An enterprise is designing a highly available hybrid network architecture for its multi-account AWS environment across two regions: (primary) and (secondary). The network architecture consists of an AWS Transit Gateway in each region, connected via a Transit Gateway peering attachment. The on-premises network has two data centers: one in New York and one in Chicago.
The New York data center connects to the Transit Gateway via a 10 Gbps AWS Direct Connect connection using a Transit VIF terminated on a central Direct Connect Gateway. The Chicago data center connects to the Transit Gateway in the same manner. To ensure disaster recovery capability, the enterprise deploys redundant IPsec VPN connections from both data centers to the Transit Gateways in their respective local regions.
The company's routing policy has the following constraints:
- Under normal operating conditions, all traffic between the VPCs in and the New York data center must use the local Direct Connect path.
- If the Direct Connect connection in fails, traffic between and the New York data center must immediately fail over to the local IPsec VPN connection. It must NOT route through the peered Transit Gateway in to avoid high inter-region data transfer charges and latency.
- Only if both the local Direct Connect and the local IPsec VPN connections in fail should traffic fail over transitively through the Transit Gateway peering connection to use the hybrid paths in .
Which TWO configurations must the Solutions Architect implement to satisfy these routing requirements?
- On the on-premises routers, advertise specific subnets (such as /24 prefixes) via BGP over both the local Direct Connect Transit VIFs and the local IPsec VPN tunnels, and configure a static route for the summary corporate network range (such as a /16 prefix) pointing to the Transit Gateway peering attachment in each region's Transit Gateway route table.Cevap
- Configure the customer gateway routers to assign the highest BGP Local Preference to routes for the local AWS region's VPC CIDR received over the local Direct Connect path, a medium Local Preference to routes received over the local IPsec VPN, and the lowest Local Preference to routes received via the remote region's Direct Connect and VPN paths.Cevap
- CEnable dynamic BGP route propagation across the Transit Gateway peering attachment, and configure BGP Local Preference attributes within the Transit Gateway route tables to prioritize the Direct Connect path over the local IPsec VPN path.
- DDeploy a single, non-redundant NAT Gateway in a shared services VPC in us-east-1 to route all outbound corporate traffic, and configure the on-premises routers to prioritize the IPsec VPN tunnels by advertising more specific subnets over the VPN than over the Direct Connect Transit VIFs.
- ECreate a single Route 53 Private Hosted Zone (PHZ) in the network account, associate it with the Transit Gateway peering attachment, and rely on the peered Transit Gateways to automatically route DNS queries and VPC-to-VPC traffic without associating the PHZ with the VPCs in the spoke accounts.