An energy utility company is migrating critical grid-monitoring servers from an on-premises data center to AWS using AWS Application Migration Service (MGN). The replication traffic must travel privately over a AWS Direct Connect connection via an AWS Transit Gateway. The target environment is a dedicated Migration VPC. The Solutions Architect has established interface VPC endpoints for the MGN control plane in a Shared Services VPC, which is shared with the Migration VPC via Route 53 Private Hosted Zone associations. After installing the AWS Replication Agent on the source servers, the console indicates that the agents can communicate with the control plane, but the replication status remains stalled at progress. Which combination of actions will resolve the replication stall and resume data transfer?
- Ensure that the on-premises firewall permits outbound traffic on TCP Port to the staging area subnet in the Migration VPC, and verify that the route table associated with the staging area subnet contains a route pointing to the Transit Gateway for the on-premises network CIDR.Cevap
- BRe-create the Route 53 Private Hosted Zone for the AWS Application Migration Service endpoints inside the Migration VPC, and ensure that the zone is manually associated with the Shared Services VPC.
- CDeploy a highly available pair of NAT Gateways in the staging area subnet, and update the staging subnet's route table to route replication traffic over the public internet to the AWS Application Migration Service public endpoints.
- DConfigure a Direct Connect gateway to handle transitive routing directly between the Migration VPC and the on-premises data center, bypassing the Transit Gateway configuration.