AWS Certified Solutions Architect Professional SAP-C02 Practice Question
Your company runs 200 Windows Server 2016 virtual machines on-premises in a VMware vSphere cluster. A dedicated 1-Gbps AWS Direct Connect private virtual interface already connects the on-premises network to a VPC in us-east-1.
The migration team will use AWS Application Migration Service (MGN). The migration must meet the following requirements:
- Keep production downtime during the final cutover below 10 minutes per server.
- Send all replication traffic through the Direct Connect link, not over the public internet.
- After each cutover, automatically install the Amazon CloudWatch agent on the new Amazon EC2 instance and join the instance to the company's AWS Managed Microsoft AD domain.
- Minimize additional infrastructure and administrative effort.
Which approach in AWS Application Migration Service will meet all of these requirements?
Deploy AWS DataSync agents on-premises to copy each VM's disks to Amazon S3 through Direct Connect, use VM Import/Export to create AMIs, and launch EC2 instances with user-data scripts that install the CloudWatch agent and join the domain at first boot.
Keep the default replication settings so MGN replicates over the public internet. After each cutover, run an AWS Systems Manager automation document that installs the CloudWatch agent and joins the instance to AWS Managed AD. Manually update the instance security group.
Order AWS Snowball Edge devices, export the virtual machines, create AMIs from the returned snapshots, launch the EC2 instances, and manually install the CloudWatch agent and join each instance to AWS Managed AD after launch.
Install the AWS Replication Agent on every source VM. In the MGN replication settings template, choose Use private IP for data replication (which sends TCP 1500 traffic across the Direct Connect link) and retain the default MGN security group. For each source server, enable the predefined post-launch actions Install a CloudWatch Agent and Join Directory Service domain. Perform a test launch, then run a cutover launch and finalize after validation.