Examkin

Soru

Zorluk: OrtaInfrastructure Migration with AWS Application Migration Service (MGN)

A manufacturing company is migrating its legacy shop-floor execution system consisting of four physical servers from an on-premises factory network to AWS. The migration team has established a hybrid network path using an AWS Direct Connect connection terminated at an AWS Transit Gateway. They have successfully installed the AWS Application Migration Service (MGN) replication agent on the source servers. However, the migration console shows that data replication is stalled and the agents cannot establish communication with the replication servers in the staging area VPC. Which of the following actions should the solutions architect take to resolve this replication communication issue?

  1. Allow inbound traffic on TCP port 1500 in the staging area security group, and ensure the on-premises firewalls permit outbound traffic over TCP port 1500 to the staging area subnet.Cevap
  2. B
    Allow inbound traffic on TCP port 443 in the staging area security group, and configure a public NAT Gateway in the staging area subnet to route replication traffic.
  3. C
    Reconfigure the Direct Connect connection to bypass the Transit Gateway by attaching a Direct Connect gateway directly to the staging area VPC, as Transit Gateway routing does not support transitive replication traffic.
  4. D
    Create a Route 53 Private Hosted Zone for the replication service endpoint and associate it with the staging area VPC and the on-premises DNS resolvers.

Cevap

Allow inbound traffic on TCP port 1500 in the staging area security group, and ensure the on-premises firewalls permit outbound traffic over TCP port 1500 to the staging area subnet.
The correct option correctly identifies that AWS MGN relies on TCP port 1500 for sending replication data from the agent on the source server to the replication servers in the staging area VPC. Ensuring both the on-premises firewall allows outbound traffic and the staging area security group allows inbound traffic on TCP port 1500 resolves the replication timeout.

Adım Adım Çözüm

1
Analyze the replication architecture of AWS MGN.
Identify that the control plane uses HTTPS (TCP port 443) to communicate with the MGN service APIs, while the actual replication stream uses TCP port 1500 to send data directly to the replication servers (EC2 instances) launched in the staging area VPC.
This helps distinguish between control plane access and data plane replication paths.
2
Evaluate the current failure symptom in the scenario.
Since the agent installation was successful, control plane connectivity (TCP port 443) is working. The issue lies within the data plane stream between the on-premises source servers and the staging area replication servers.
Correctly identifying the stalled data replication point points directly to TCP port 1500.
3
Configure the network security rules.
Permit outbound TCP 1500 from the on-premises firewall and inbound TCP 1500 in the security group associated with the replication servers in the AWS staging area.
This establishes the necessary connection path for block-level replication traffic.

Anahtar Kavram

AWS Application Migration Service (MGN) network port requirements for data replication
Bu soruyu puanla

Konular

Infrastructure Migration with AWS Application Migration Service (MGN)

Bu konudan daha fazla soru