You are tasked with moving a legacy application from a virtual machine running inside your
datacenter to an Amazon VPC. Unfortunately, this app requires access to a number of onpremises services and no one who configured the app still works for your company. Even worse,
there’s no documentation for it. What will allow the application running inside the VPC to reach
back and access its internal dependencies without being reconfigured? Choose 3 answers
A.
A VM Import of the current virtual machine
B.
An Internet Gateway to allow a VPN connection
C.
Entries in Amazon Route 53 that allow the Instance to resolve its dependencies’ IP addresses
D.
An IP address space that does not conflict with the one on-premises
E.
An Elastic IP address on the VPC instance
F.
An AWS Direct Connect link between the VPC and the network housing the internal services
Answer : A, D & F
A. VM Import of the current virtual machine (VM Import to copy the VM to AWS as there is no documentation it can’t be configured from scratch)
B. An Internet Gateway to allow a VPN connection. (Virtual and Customer gateway is needed)
C. Entries in Amazon Route 53 that allow the Instance to resolve its dependencies’ IP addresses (Route 53 is not required)
D. An IP address space that does not conflict with the one on-premises (IP address cannot conflict)
E. An Elastic IP address on the VPC instance (Don’t need a EIP as private subnets can also interact with on-premises network)
F. An AWS Direct Connect link between the VPC and the network housing the internal services (VPN or a DX for communication)