An enterprise is migrating its legacy on-premises ERP application consisting of 15 virtual machines to AWS using AWS Application Migration Service (MGN). The hybrid connectivity between the on-premises data center and AWS is established via a 1 Gbps AWS Direct Connect connection that terminates at an AWS Transit Gateway in a centralized Network Services VPC. The Transit Gateway distributes traffic to a dedicated Staging VPC where the MGN replication servers are provisioned. After installing the AWS Replication Agent on the on-premises source servers, the migration team observes that the data replication status remains stuck at 'Initiating' and the agent log files show connection timeouts when attempting to reach the replication servers. Which of the following actions should a Solutions Architect take to resolve this issue and allow data replication to proceed?
- Configure the on-premises firewall to permit outbound traffic on TCP port 1500 to the staging area subnet CIDR block, and verify that the security group associated with the replication servers in the Staging VPC allows inbound traffic on TCP port 1500 from the on-premises IP address range.Cevap
- BCreate an Amazon Route 53 private hosted zone for the MGN replication endpoints, associate it with both the Staging VPC and the Network Services VPC, and configure the on-premises firewall to allow outbound HTTPS traffic on TCP port 443.
- CModify the Transit Gateway route tables to bypass the Network Services VPC and route the replication traffic through a Direct Connect Gateway associated directly with the Staging VPC, as Transit Gateway does not support transitive routing between Direct Connect and a Staging VPC.
- DDeploy redundant NAT Gateways across multiple Availability Zones in the Staging VPC, and update the route tables of the replication server subnets to route default outbound traffic (0.0.0.0/0) through these NAT Gateways to the internet.