A logistics corporation is designing a hybrid network connectivity solution for its multi-account AWS environment. The infrastructure consists of spoke VPCs evenly distributed across the `us-east-1` and `eu-west-1` regions. The company must connect this infrastructure to two on-premises data centers: a primary site in Frankfurt and a secondary site in Munich. The design must use two AWS Direct Connect connections—one terminating in Frankfurt and another in Munich—to achieve high availability and active-standby failover. The architecture must minimize BGP routing complexity and administrative overhead, prevent inter-VPC traffic from crossing regions unless explicitly configured, and scale to accommodate new spoke VPCs without manual BGP updates. Which TWO network configurations should a solutions architect implement to meet these requirements?
- Deploy an AWS Transit Gateway in `us-east-1` and another in `eu-west-1`, then associate both Transit Gateways with a single global AWS Direct Connect Gateway.Cevap
- On the Direct Connect Gateway association for each Transit Gateway, configure the allowed prefixes to advertise only the specific IP CIDR blocks of the VPCs located within that Transit Gateway's respective region.Cevap
- CEstablish a Transit Gateway peering connection between the two regions, and configure the route tables to dynamically route on-premises destined traffic through the peered Transit Gateway if the local Direct Connect connection fails.
- DCreate a separate AWS Direct Connect Gateway in each region, and peer the two Direct Connect Gateways to enable cross-region transitive routing between the data centers and the spoke VPCs.
- EUtilize AWS Resource Access Manager to share the Direct Connect private virtual interfaces (VIFs) across all AWS accounts, and configure BGP sessions directly from the on-premises routers to each spoke VPC Virtual Private Gateway.