exam questions

Exam AWS Certified Solutions Architect - Professional All Questions

View all questions & answers for the AWS Certified Solutions Architect - Professional exam

Exam AWS Certified Solutions Architect - Professional topic 1 question 35 discussion

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 three.)

  • 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
Show Suggested Answer Hide Answer
Suggested Answer: ADE 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Warrenn
Highly Voted 3 years, 7 months ago
ADE The question asks what will allow the application running inside the VPC to reach back and access its internal dependencies without being reconfigured. Not how to migrate it. To properly resolve internal dependency address you need Route53 https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver-getting-started.html
upvoted 22 times
EricZhang
3 years, 6 months ago
You need to configure Resolver that forward the DNS query to on-prem DNS servers. I think E means adding A/CNAME/Alias records into Route 53.
upvoted 4 times
Smart
3 years, 6 months ago
Agreed. Option F is simply not relevant to the question asked. Option E is more appropriate. In this case, we setup a R53 Private Hosted Zone. More appropriately, also setup R53 Resolver. Answer is ADE.
upvoted 2 times
kakashi
3 years, 6 months ago
Although I agree that Route53 could be used E does not clearly explain what needs to be done. D is important because is a VM with no documentation so you might not be able to recreate it from scratch and the best way is to import the VM into AWS.
upvoted 1 times
...
...
...
tan9
3 years, 7 months ago
ADF. The question is "MOVING a legacy application from a virtual machine running inside your datacenter to an Amazon VPC," hence (E) VM Import is the necessary step to do. Besides, (D) Route 53 Private DNS will only work for DNS names rather than IP addresses.
upvoted 13 times
sashenka
3 years, 5 months ago
AD[E]. So if the application is referencing internal/on-prem domains one would need to forward those to the on-prem DNS via R53. The facts we're given is there is "no documentation" about the app. For example the app could be trying to connect to an on-prem database or file server via a FQDN which is a best practice rather than reference IP's. So in this scenario how would you suggest it function if one does not leverage R53? Take another look at what we are being asked for... it is communication dependencies and not migration methodology.
upvoted 3 times
hobokabobo
2 years, 3 months ago
Um, first sentence: "You are tasked with moving a legacy application from a virtual machine running inside your datacenter to an Amazon VPC"
upvoted 1 times
shammous
1 year, 3 months ago
That step was already done. the question is about connectivity not migration
upvoted 1 times
...
...
...
...
...
AnNguyen
Highly Voted 3 years, 6 months ago
Answer is A,D,F B: Virtual and Customer gateway is needed C: Don’t need a EIP as private subnets can also interact with on-premises network E: Route 53 is not required
upvoted 11 times
student22
5 months, 3 weeks ago
Route 53 is required if the existing legacy app is using FQDN to access resources.
upvoted 1 times
...
...
vampiret
Most Recent 3 months, 1 week ago
Selected Answer: ADF
the question mention you have no knowledge to rebuild the app, so you need import the VM as a fundamental task
upvoted 1 times
...
student22
5 months, 3 weeks ago
Selected Answer: ADE
ADE E - Route 53 is required if the existing legacy app is using FQDN to access on-prem resources.
upvoted 1 times
...
amministrazione
8 months, 2 weeks ago
A. An AWS Direct Connect link between the VPC and the network housing the internal services. D. An IP address space that does not conflict with the one on-premises F. A VM Import of the current virtual machine
upvoted 1 times
...
devilman222
1 year ago
Don't understand how its anything but ADE. A. Only way mentioned to communicate with on prem. F. Can't work without it. Without a DNS resolver, the two machines will never find each other D. This is necessary for F to work. Wrong answers. B. It doesn't need to be public C. An elastic IP solve the problem of communicating with on Prem. F. Lots of ways to do this, but you only get three which are required for it to work.
upvoted 1 times
...
kondratyevmn
1 year, 9 months ago
Why everyone is so convinced about D? I would choose C over D, because an Elastic IP address comes from Amazon's pool of IPv4 addresses, !!!OR!!! from a custom IPv4 address pool that you have brought to your AWS account. Meaning that you can keep the IP from on-premise. ACF
upvoted 1 times
...
Prasadvd
2 years, 1 month ago
Selected Answer: ADE
Question is not on how to migrate the VM. The VM is assumed to have already been migrated. Resolution of address would require outbound endpoint and Rte 53 Resolver https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html
upvoted 4 times
...
TigerInTheCloud
2 years, 4 months ago
Selected Answer: ADF
A. Possible for connection, if we do not have any other (better) way B. Wrong, the internet gateway is not for VNP. C. No, EIP is not needed. D. Yes, no IP conflict (or you need NAT) E. Good, I prefer hostnames over IPs F. Surely, for moving applications to the cloud. So choose three ADF; If choose four ADEF
upvoted 2 times
...
Cal88
2 years, 6 months ago
I don't know why a lot of comments here are talking about route 53 when its not relevant at all. If we have a direct connect connection and a server that's migrated from on premise as is (including DNS config in /etc/resolv.conf ) That server will still use on premise DNS since we already have reachability to our on premise using direct connect You use route 53 resolver to point an ec2 instance that's using your VPC DNS to on premise The question is clearly asking for a "Lift and shift" approach so I would go with ADF
upvoted 2 times
...
welcomeYM
2 years, 7 months ago
Selected Answer: ADF
ADF ADF ADF ADF ADF
upvoted 1 times
marcotglb
2 years, 4 months ago
The question is just about reachability. It is not about how the machine should be migrated. The original machine could also be migrated in other ways.
upvoted 1 times
...
...
snakecharmer2
2 years, 11 months ago
Selected Answer: ADF
F and no E - We need to import the VM because we want to move all the configruations and keys that are located on its disk with it, so it is a must for the migration. Route53 is not a must!!!
upvoted 1 times
...
aloha123
2 years, 12 months ago
Selected Answer: ADE
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html
upvoted 1 times
...
RVivek
3 years, 3 months ago
ADE or ADF ADE : If you take the question "What enables the application operating inside the VPC to communicate with and access its internal dependencies without requiring reconfiguration?" In this case we assume the VM migaration is over ADF: If you focus on the question part "You've been entrusted with the responsibility of migrating a legacy application from a virtual machine" . here we assume the application uses hardcoded IP address and do not use DNS names
upvoted 1 times
RVivek
3 years, 3 months ago
ADF after reading this https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-vpc-to-network On route 53 you configure an outboud end point and forward queries from VPC to on-pre DNS server. You need not (cannot ?) make netries on Route53
upvoted 1 times
...
...
sashenka
3 years, 5 months ago
AD[E]. We are being asked for communication dependencies and NOT migration strategy! If the application is referencing internal/on-prem domains one would need to forward those to the on-prem DNS via R53. The facts we're given is there is "no documentation" about the app. So if the app could be configured to connect to an on-prem database or file server via a FQDN which is a best practice rather than reference IP's. So in this scenario how would you suggest it function if one does not leverage R53? Take another look at what we are being asked for... it is communication dependencies and not migration method!
upvoted 1 times
Cal88
2 years, 6 months ago
That's not true We are asked to "Lift and shift" the application and make it work in AWS as it was on premise. Why would. you need route 53 when the server is already using the on premise DNS and direct connect is being used? The DNS queries will go from the server to the on premise without the need to setup anything on route 53. if you use VM import export the same server will be replicated to AWS and all of its configuration will be the same including DNS configs I would choose ADF.
upvoted 1 times
...
...
joyees1979
3 years, 5 months ago
ADE should be correct. Not F because the questionasks what will be required for the applicaton running inside the VPC (assumption that the application has already been migrated).
upvoted 1 times
...
Akhil254
3 years, 5 months ago
ADF Correct
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago