A gaming studio is migrating its legacy multiplayer game servers from an on-premises data center to AWS using AWS Application Migration Service (MGN). The replication network path must be private, utilizing an existing AWS Direct Connect connection with a private virtual interface (VIF) attached to an AWS Transit Gateway that connects to the migration VPC. During the initial testing phase, the AWS MGN Replication Agent is installed on the source servers, but the replication status remains stuck at 'Initiating' and no data is being copied to the staging area in AWS. A network engineer verifies that the source servers can resolve the necessary domain names and can reach the VPC endpoints in AWS, but the replication data blocks are not being received. Which of the following configuration changes will resolve this replication issue?
- Update the security group of the staging area replication servers to permit incoming connections on TCP port 1500 from the on-premises IP address range, and configure the local firewall to permit outgoing traffic on the same port.Cevap
- BReconfigure the Transit Gateway route table to establish a Direct Connect Gateway connection that bypasses the Transit Gateway routing, allowing direct peering between the on-premises data center and the staging VPC.
- CLink the Amazon Route 53 Private Hosted Zone created for the AWS MGN interface VPC endpoints to the staging VPC and authorize cross-account access for the on-premises DNS resolver.
- DRoute all outbound traffic from the staging subnets through a single NAT Gateway located in a public subnet of the staging VPC to reach the AWS MGN service endpoints.