Q98 — AWS SAA-C03 Ch.11

Question 98 of 100 | ← Chapter 11

Q798. A company has an AWS Direct Connect connection from its corporate data center to its VPC in the us-east- 1 Region. The company recently acquired a corporation that has several VPCs and a Direct Connect connection between its on-premises data center and the eu-west-2 Region. The CIDR blocks for the VPCs of the company and the corporation do not overlap. The company requires connectivity between two Regions and the data centers. The company needs a solution that is scalable while reducing operational overhead.What should a solutions architect do to meet these requirements?

• A. Set up inter-Region VPC peering between the VPC in us-east-1 and the VPCs in eu-west-2.
• B. Create private virtual interfaces from the Direct Connect connection in us-east-1 to the VPCs in eu-west- 2.
• C. Establish VPN appliances in a fully meshed VPN network hosted by Amazon EC2. Use AWS VPN CloudHub to send and receive data between the data centers and each VPC.
• D. Connect the existing Direct Connect connection to a Direct Connect gateway. Route traffic from the virtual private gateways of the VPCs in each Region to the Direct Connect gateway. ✓

Correct Answer: D. Connect the existing Direct Connect connection to a Direct Connect gateway. Route traffic from the virtual private gateways of the VPCs in each Region to the Direct Connect gateway.

Explanation

To meet the requirement of establishing connectivity between two AWS Regions and the data centers of both the company and the recently acquired corporation, while ensuring scalability and reducing operational overhead, the recommended solution is:D. Connect the existing Direct Connect connection to a Direct Connect gateway. Route traffic from the virtual private gateways of the VPCs in each Region to the Direct Connect gateway.By connecting the existing Direct Connect connection to a Direct Connect gateway, you can establish connectivity between the company's VPC in the us-east-1 Region and the VPCs in the eu-west-2 Region. The Direct Connect gateway acts as a hub, allowing traffic to flow between the VPCs in different Regions and the on-premises data centers.Here's why the other options are not the best fit for the given requirements:A. Setting up inter-Region VPC peering: While inter-Region VPC peering allows connectivity between VPCs in different Regions, it does not directly address the requirement of connecting the data centers and reducing operational overhead.B. Creating private virtual interfaces from the Direct Connect connection: This option only establishes connectivity between the Direct Connect connection in the us-east-1 Region and the VPCs in the eu-west-2 Region. It does not address the requirement of connecting the data centers or provide a scalable solution.C. Establishing VPN appliances in a fully meshed VPN network: While this option allows for connectivity between the data centers and the VPCs, it introduces additional complexity and operational overhead by requiring the deployment and management of VPN appliances in an EC2-based VPN network.Therefore, the recommended solution that meets the requirements of establishing connectivity between two AWS Regions and the data centers while ensuring scalability and reducing operational overhead is:D. Connect the existing Direct Connect connection to a Direct Connect gateway. Route traffic from the virtual private gateways of the VPCs in each Region to the Direct Connect gateway.