A company is migrating to AWS and intends to use multiple VPCs across multiple AWS Regions. A network engineer needs to establish connectivity between the eu-west-1 and eu-central-1 Regions to the company headquarters and branch office, respectively.

The network engineer created a production VPC, Prod A, with a CIDR block of 10.0.0.0/16 in an account in eu-west-1, and another production VPC, Prod B, with a CIDR block of 10.1.0.0/16 in a different account in eu-central-1.

The network engineer performed the following steps to establish connectivity:

Created a transit gateway in each Region

Shared and accepted the transit gateways with the production accounts in both Regions

Configured a peering attachment between the transit gateways

Attached both VPCs to their respective Region's transit gateway

Created transit gateway route tables and associated the attachments with the route tables

Configured static routes in both transit gateway route tables to direct traffic to the remote VPC in the other Region

Enabled route propagation on the VPC route tables in each Region

After completing the configuration, the network engineer attempted to connect from Prod A to Prod B but was unsuccessful.

What steps should the network engineer take to ensure the required connectivity is achieved?

Exam-Like

Modify the IP address of the peering attachment to a wider range.

Delete the static routes that were in the transit gateway route table to send traffic to the remote VPC and enable route propagation instead.

Create a new route destined to 10.0.0.0/8 in both production VPC route tables with the Region transit gateway as the target.

Modify the transit gateway route tables from the production accounts to propagate routes dynamically between the production VPCs.

AWS Certified Advanced Networking - Specialty