A county clinic scheduling application runs on VMs that must be rehosted to AWS with continuous replication and a planned cutover window. Which application transfer mechanism should architects select?
Select an answer to reveal the explanation.
Short Explanation
Rehosting clinic VMs is a moving truck with a synchronized inventory, not a photo album of screenshots. MGN keeps the machines replicating and gives you a real cutover window for lift-and-shift.
Full Explanation
A county clinic scheduling application on VMs that must be rehosted to AWS with continuous replication and a planned cutover window should use AWS Application Migration Service (MGN) for lift-and-shift rehost. MGN continuously replicates disks and supports controlled cutover windows suited to clinical operations that cannot accept uncontrolled downtime for patient appointments. Amazon Kinesis Data Streams as the primary VM disk replication engine fails concept: Kinesis is a streaming data service, not block-level VM replication for rehost of clinic systems. AWS Snowcone devices carrying only the application installer MSI fail to replicate running VM state for continuous rehost of clinic schedules. Manual AMI builds from screenshots of each on-premises console fail automation, consistency, and continuous replication needs for healthcare cutovers. Exam caveat: MGN is the AWS rehost replication and cutover service for VM lift-and-shift. Operational check: install MGN agents, validate continuous replication lag against RPO targets, rehearse cutover in a nonprod window, schedule clinical cutover with rollback criteria, and monitor post-cutover clinic scheduling SLOs with the health department.