Examkin

Question

Difficulty: MediumInfrastructure Migration with AWS Application Migration Service (MGN)

An automotive manufacturing company is migrating its legacy telemetry processing servers (88 virtual machines running on-premises hypervisors) to AWS using AWS Application Migration Service (MGN). The migration must use a dedicated AWS Direct Connect connection connected via a transit virtual interface (VIF) to an AWS Transit Gateway. The target staging area VPC has no direct internet access, and all data replication traffic must be kept entirely private. The migration team has installed the replication agent on the source virtual machines, but the agent fails to establish a connection with the replication servers in the staging area VPC. Which of the following configuration steps must be performed to establish private replication connectivity and resolve the issue? (Select TWO.)

  1. Configure the on-premises firewall and the MGN staging area security groups to allow outbound TCP port 15001500 traffic from the source servers to the replication servers in the staging area subnet.Answer
  2. Configure the AWS Application Migration Service replication template to use private IP addresses for data routing and ensure the Transit Gateway routes traffic between the Direct Connect connection and the staging area VPC.Answer
  3. C
    Associate the Route 53 Private Hosted Zone created for the MGN control plane endpoints with the Transit Gateway to allow the replication agent to resolve the endpoints.
  4. D
    Deploy a single NAT Gateway in the staging area subnet and configure the route tables to route all TCP port 15001500 replication traffic through it to the on-premises environment.
  5. E
    Configure the Direct Connect Gateway to enable direct transitive routing between the staging VPC and the inspection VPC without passing traffic through the Transit Gateway.

Answer

To establish private replication connectivity, you must configure the on-premises firewall and staging area security groups to allow TCP port 15001500 traffic, and configure the MGN replication template to use private IP addresses while ensuring the Transit Gateway routes traffic over the Direct Connect connection.
The correct configuration requires opening TCP port 15001500 for replication traffic and modifying the replication template to use private IP addresses. AWS Application Migration Service replicates data using the MGN replication agent over TCP port 15001500. If this port is blocked on the source firewall or staging security groups, connectivity fails. Additionally, to ensure replication traffic flows privately over Direct Connect and Transit Gateway, the replication template must be configured to use private IP addresses.

Step-by-Step Solution

1
Verify the network port requirements for AWS Application Migration Service replication.
Determine that TCP port 15001500 must be open outbound from the source servers to the replication servers in the staging area VPC.
MGN replicates data at the block level over TCP port 15001500.
2
Configure routing and IP addressing settings in the MGN replication template.
Set the replication template to route data replication traffic over private networks using private IP addresses.
This forces replication traffic over the Direct Connect connection rather than trying to use public endpoints.
3
Verify routing transitiveness through the Transit Gateway.
Ensure the Transit Gateway routing tables associate and propagate paths between the on-premises gateway and the staging area VPC.
The Transit Gateway acts as the hub for routing private traffic over the Direct Connect connection.

Key Concept

Data replication in AWS Application Migration Service (MGN) requires TCP port 15001500 to be open between the source agent and the staging area replication servers, and private routing must be enabled in the replication template to utilize Direct Connect or VPN connections.
Rate this question

Topics

Infrastructure Migration with AWS Application Migration Service (MGN)

More questions from this topic