A media streaming enterprise is migrating its legacy content transcoding and metadata proc… — AWS Certified Solutions Architect - Professional

A media streaming enterprise is migrating its legacy content transcoding and metadata processing cluster consisting of $30$ on-premises servers to AWS. The staging area VPC in AWS is connected to the on-premises environment using an AWS Direct Connect connection with a Transit Gateway. During the replication phase, the migration team observes that the AWS Application Migration Service (MGN) replication agent is installed on the on-premises servers, but the replication status remains stuck at 'Initiating' with a communication error. Additionally, in the target VPC, replica test instances launched in the private subnets are unable to download necessary packages from the internet during post-launch scripting, leading to failed test phases. Which two actions should the solutions architect take to resolve these issues and ensure a successful migration? (Select TWO.)

Allow outbound traffic from the on-premises servers to the staging area subnets over TCP port $1500$ , and configure the staging area security groups to allow inbound traffic on TCP port $1500$ .Answer
Deploy redundant NAT Gateways across multiple Availability Zones in the target VPC's public subnets, and configure the target private subnets' route tables to route outbound internet traffic ( $0.0.0.0/0$ ) to the respective NAT Gateway in their zone.Answer
C
Configure the staging area replication servers to initiate inbound connections to the on-premises servers over TCP port $443$ to pull the replicated data blocks.
D
Deploy a single NAT Gateway in one public subnet of the target VPC, and configure the route tables of all target private subnets across all Availability Zones to route outbound internet traffic ( $0.0.0.0/0$ ) through this single NAT Gateway.
E
Associate the Route $53$ Private Hosted Zone used for the update repository with the on-premises network interfaces directly to allow local resolution of target package repositories.
F
Configure Transit Gateway routing to bypass the target VPC route tables and route replication traffic directly to the target VPC's private subnets using a Direct Connect gateway without a Transit Gateway attachment.

Answer

The solutions architect should allow outbound traffic from on-premises to the staging area subnets over TCP port

1500

(with corresponding inbound security group rules) and deploy redundant NAT Gateways across public subnets in the target VPC, configuring target private subnets to route outbound traffic through their respective regional NAT Gateway.

The AWS Application Migration Service (MGN) agent requires TCP port

1500

to send data replication blocks from on-premises servers to the staging area replication servers. In addition, post-launch testing of migrated instances in private subnets requires internet access to fetch packages, which is best achieved in a highly available manner using redundant NAT Gateways across public subnets.

Step-by-Step Solution

Update local firewalls and AWS Security Groups associated with the staging area replication instances to permit replication traffic.

Established TCP port

1500

connectivity between the on-premises source servers and the replication instances.

This allows the replication agent to push data blocks securely to AWS and resolves the 'Initiating' status hang.

Deploy highly available NAT Gateways across all public subnets in the target VPC and route private subnet outbound traffic to them.

Highly available outbound internet connectivity is established for target instances in private subnets.

This enables post-launch script execution on target instances to fetch external update packages without creating a single point of failure.

Key Concept

AWS MGN network requirements (port 1500) and highly available target VPC routing for post-launch execution.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic