ANS-C01 Question 158
Select 2You are designing a connectivity strategy for an organization with multiple AWS accounts, spanning two AWS Regions. Each account has multiple VPCs, and the organization requires low-latency, high-bandwidth communication between VPCs within the same account, across accounts, and across Regions. Additionally, the solution must minimize management overhead and use AWS-managed services where possible. Which combination of solutions should you implement?
- A
Use AWS Transit Gateway to interconnect VPCs within each Region and establish peering between the Transit Gateways in different Regions.
- B
Use VPC Peering to establish connectivity between all VPCs in both Regions.
- C
Use AWS Direct Connect to establish private connections between the Regions.
- D
Use AWS Transit Gateway to interconnect VPCs within each account and then use AWS PrivateLink for inter-Region communication.
- E
Use AWS Transit Gateway to interconnect VPCs within each Region and enable inter-Region peering between the Transit Gateways.
Show answer and explanation
Correct answers: A, E
Explanation
To design a scalable, low-latency, high-bandwidth connectivity architecture across multiple AWS accounts and Regions, AWS Transit Gateway is the primary service to use. It simplifies the management of connections within a Region and supports inter-Region peering for cross-Region connectivity. This approach minimizes management overhead and leverages AWS-managed services, aligning with the requirements of the scenario.
- A. Correct.
Correct. AWS Transit Gateway is designed for managing connectivity at scale within a Region. Transit Gateway inter-Region peering is a recommended solution for connecting VPCs across Regions with low-latency, high-bandwidth capabilities.
- B. Incorrect.
Incorrect. VPC Peering can achieve connectivity between VPCs, but managing peering connections at scale across multiple accounts and Regions leads to significant management overhead. This does not align with the requirement to minimize management overhead.
- C. Incorrect.
Incorrect. AWS Direct Connect is used for hybrid connectivity between on-premises networks and AWS, not for inter-VPC or inter-Region connectivity within AWS.
- D. Incorrect.
Incorrect. AWS PrivateLink is primarily designed for exposing services securely to other VPCs and accounts, not for general inter-Region connectivity between VPCs.
- E. Correct.
Correct. AWS Transit Gateway interconnects VPCs within a Region efficiently and supports inter-Region peering, which is a scalable and AWS-managed solution for multi-Region connectivity.