Deploy the AMS agentless appliance to vCenter and move the Windows share to FSx
A company is migrating its data center to the AWS Cloud and needs to complete the migration as quickly as possible. The company has many applications that are running on hundreds of VMware VMs in the data center. Each VM is configured with a shared Windows folder that contains common shared files. The file share is larger than 100 GB in size. The company’s compliance team requires a change request to be fled and approved for every software installation and modification to each VM. The company has an AWS Direct Connect connection with 10 GB of bandwidth between AWS and the data center. Which set of steps should the company take to complete the migration in the LEAST amount of time?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The compliance requirement rules out installing an agent on each VM, so discovery and replication must come from the agentless appliance deployed to vCenter, and the Windows share needs a native SMB target, which makes FSx for Windows File Server the correct destination rather than EFS.
A company must migrate hundreds of VMware VMs as quickly as possible, each VM using a shared Windows folder larger than 100 GB, and a compliance team requires an approved change request for every software installation or modification on each VM. A 10 GB Direct Connect link connects the data centre to AWS.
Using VM Import/Export. That path requires building an image per VM and then managing those images, which does not use the discovery and continuous replication that Application Migration Service provides, so it is not the fastest route for hundreds of VMs.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The compliance constraint is the deciding factor, because it forbids installing software on any VM, and that rules out any agent-based discovery or replication approach. The AWS Application Migration Service agentless appliance is deployed once into VMware vCenter, where it discovers the existing VMs and replicates them continuously, so hundreds of VMs migrate without touching a single guest and without waiting on per-VM change requests. For the shared Windows folder, FSx for Windows File Server provides native SMB semantics so the existing Windows workloads keep working unchanged after the file share is remapped, which is not something an EFS mount would deliver for a Windows shared folder. Reviewing the discovered portfolio completes the picture, and the whole approach uses the existing Direct Connect bandwidth rather than physically shipping data.Why the Other Options Are Wrong
A: Using VM Import/Export means creating an image for each VM and then managing those images separately, which is a slower, more manual process for hundreds of VMs than continuous replication from the agentless appliance, and it does not provide the portfolio view the option describes through Application Migration Service. It also copies the Windows share to EFS, which is not an SMB-native destination for Windows workloads. B: Deploying the Application Discovery Service agentless appliance to vCenter and reviewing the portfolio in Migration Hub performs discovery only, so nothing is actually migrated and the file share is not moved at all, which fails the requirement to complete the migration. D: Installing both the Application Discovery Service Agent and the Application Migration Service Agent on each VMware hypervisor requires software installation and modification on the hosts, which the compliance team's change process would have to approve for every host, and it is slower than the agentless approach the requirement is designed to force.Community Comment Notes
The community voted 100 to 0 for C, and the top-voted comments identified the key distinction, that the Application Migration Service agentless appliance is the correct choice because it is deployed into the VMware environment via vCenter and eliminates the need for per-VM agents. Other commenters noted that FSx for Windows File Server is the right target for a Windows shared folder, and one dissented in favour of B on the grounds of speed alone while not addressing the fact that B does not migrate anything.Official Reference
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →