MLS-C01 · Question #148
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…
The correct answer is A. A VM Import of the current virtual machine D. An IP address space that does not conflict with the one on-premises F. An AWS Direct Connect link between the VPC and the network housing the internal services. To migrate a legacy application from an on-premises VM to an Amazon VPC without reconfiguration, it's essential to import the VM as-is and establish seamless private network connectivity back to on-premises services.
Question
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
Options
- AA VM Import of the current virtual machine
- BAn Internet Gateway to allow a VPN connection
- CEntries in Amazon Route 53 that allow the Instance to resolve its dependencies' IP addresses
- DAn IP address space that does not conflict with the one on-premises
- EAn Elastic IP address on the VPC instance
- FAn AWS Direct Connect link between the VPC and the network housing the internal services
How the community answered
(37 responses)- A78% (29)
- B3% (1)
- C14% (5)
- E5% (2)
Why each option
To migrate a legacy application from an on-premises VM to an Amazon VPC without reconfiguration, it's essential to import the VM as-is and establish seamless private network connectivity back to on-premises services.
Importing the current virtual machine using AWS VM Import/Export allows the legacy application, its operating system, and all configurations to be moved to an EC2 instance in AWS without modification, directly addressing the 'without being reconfigured' requirement.
An Internet Gateway primarily allows public internet access and does not, by itself, establish a private VPN connection to an on-premises network for internal dependency access.
While crucial for DNS-based access, creating entries in Amazon Route 53 primarily addresses name resolution and assumes underlying network connectivity is already established; it is secondary to the foundational network connection and non-conflicting IP space.
Establishing an IP address space for the VPC that does not conflict with the on-premises network's IP space is fundamental for enabling proper routing and communication between the VPC instance and the on-premises dependencies.
An Elastic IP address provides a static public IP for an EC2 instance, which is used for external internet-facing communication, not for private access back to on-premises internal services.
An AWS Direct Connect link provides a dedicated private network connection between the Amazon VPC and the on-premises network, ensuring secure, high-bandwidth, and low-latency access for the migrated application to its internal dependencies.
Concept tested: Hybrid cloud connectivity and VM migration
Source: https://docs.aws.amazon.com/vm-import/latest/userguide/what-is-vmimport.html
Topics
Community Discussion
No community discussion yet for this question.