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 on-premises 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.
An AWS Direct Connect link between the VPC and the network housing the internal services.
B.
An Internet Gateway to allow a VPN connection.
C.
An Elastic IP address on the VPC instance
D.
An IP address space that does not conflict with the one on-premises
E.
Entries in Amazon Route 53 that allow the Instance to resolve its dependencies’ IP addresses
F.
A VM Import of the current virtual machine
ADF
1
0
D is not c- Application is MOVING. ACF are correct.
1
0
@AmazingGirl, it cannot be C, Why do you need public Ip address? specially when it has been even mentioned in question that it need be available on internet. However it needs connect back to on-premise apps.
I think It should be: AEF
0
0
I think it should be ADE.
-correct-
A- This will facilitate the connection to on-prem.
D- The IPs can’t overlap.
E- This one is left, since 3 wrong answers has been found. Not enough detail if this is correct or not. If this application used IPs, this wouldn’t be needed.
-wrong-
B- It doesn’t need an IGW for a VPN connection.
C- it doesn’t need a public IP.
F- The question is about communicating from VPC to on-prem. Not about moving it to VPC.
0
0
the first sentence of the question is “You are tasked with moving a legacy application from a virtual machine running Inside your datacenter to an
Amazon VPC”, F is the first step to solve the question.
VM Import/Export enables customers to import Virtual Machine(VM) images in order to create Amazon EC2 instance.
0
0
I am having some doubts on option E . route 53 can work on within VPC for private DNS. I hope route 53 service can not resolve on premise private IP address even if you create record set also.
0
0
I like ADE as well. Legacy app usually means its not virtualized rulling out VM import.
0
0
it clearly states ‘moving a legacy application from a virtual machine’
0
0
I like ADF. How will you migrate application to cloud without VM? No documentation about software and configuration of server is available. So F is mandatory
0
0
ADF
0
0
i select ACD
0
0
ADF
A. An AWS Direct Connect link between the VPC and the network housing the internal services. — correct, you could use this to have the instance you migrated into the VPC communicate back to the legacy on-prem servers. (You could also use a VPN instead of a circuit if you wanted)
B. An Internet Gateway to allow a VPN connection. — incorrect, you don’t need an IGW to build a VPN back to your on-prem data center
C. An Elastic IP address on the VPC instance. — incorrect, there is nothing in the question to indicate anything needs to communicate over the Internet, it could all be internal traffic only.
D. An IP address space that does not conflict with the one on-premises. — correct, you would totally need to make sure there were no private IP conflicts between your VPC CIDR and your internal on-prem networks if you wanted the instance in the VPC to talk to the legacy on-prem servers.
E. Entries in Amazon Route 53 that allow the Instance to resolve its dependencies’ IP addresses. –incorrect… You could have your instance use hard-coded private IP addresses to communicate to the on-prem servers, thus removing DNS from the equation entirely. If you did choose to use DNS to resolve them (which is probably better than hard-coded private IP addresses), you still wouldn’t wouldn’t want to do a zone transfer and configure those DNS entries in Route53. You’d just point your VPC instance to your on-prem DNS server, or alternatively set up a bind instance in your VPC with a forwarder to your on-prem DNS server.
F. A VM Import of the current virtual machine. — correct, you would definitely want to leverage this in order to easily migrate the VM from on-prem to AWS.
3
0
Thank you!
0
0
ADF
0
0
A, D and F are the right answers.
0
0
Go with ADF
0
0
F wont be the correct answer, as question being asked “What will allow the application running inside the VPC to reach back and access its internal dependencies without being reconfigured?
”
F is definitely require a lot of reconfiguration work.
I will go for ADE. Agreed with Someone$33
0
0
Without being reconfigured is a crucial word
A is clearly correct
D is also a must
F serves to be only plausible if you do not want to reconfigure the VM
BEC are irrelevant you do not need them at all.
0
0
ADF
0
0
ADF
F is for moving legacy VM to AWS
0
0