A pharmaceutical company is executing a lift-and-shift migration of its on-premises Manufacturing Execution System (MES) to AWS using AWS Application Migration Service (MGN). The on-premises servers are located in a secure subnet with outbound traffic filtered through a local firewall. Connectivity to AWS is established via a Site-to-Site VPN terminated on an AWS Transit Gateway in a centralized Network Services account. The target staging area resides in a dedicated Staging VPC in a separate Migration account, which is attached to the same Transit Gateway. After successful installation of the MGN replication agent on the source servers, the replication status in the AWS Migration Hub console remains 'Stalled' with zero bytes transferred. Which configuration changes must the Solutions Architect implement to establish replication connectivity and allow replication data to flow to the staging area? (Select TWO.)
- Configure the security group of the Replication Servers in the Staging VPC to allow inbound traffic on TCP port from the on-premises source subnet CIDR block.Cevap
- Update the Transit Gateway route tables and the Staging VPC route tables to ensure bidirectional routing is established between the Staging VPC subnet and the on-premises subnet.Cevap
- CAssociate the Route 53 Private Hosted Zone (PHZ) created for the MGN VPC endpoints with the Staging VPC, and configure an on-premises DNS conditional forwarder to resolve MGN endpoints via a VPC peering connection.
- DDeploy a single NAT Gateway in the public subnet of the Staging VPC, and configure the Staging VPC route tables to route all outbound replication server traffic through the NAT Gateway to reach the on-premises network.
- EAttach a Direct Connect Gateway directly to the Staging VPC, and establish a virtual interface (VIF) to bypass the Transit Gateway to enable transitive routing between the VPN and the Direct Connect Gateway.