A company uses the us-east-1 Region and the ap-south-1 Region for its business units (BUs). The BUS are named BU-1 and BU-Z. For each BU, there are two VPCs in us-east-1 and one VPC in ap-south-1…

Question

Options

• AConfigure an AWS Cloud WAN network that operates in the required Regions. Attach all BU
• BConfigure a transit gateway in each Region. Configure peering between the transit gateways.
• CConfigure an AWS Cloud WAN network that operates in the required Regions. Attach all BU
• DConfigure an AWS Cloud WAN network that operates in the required Regions. Create AWS

• A
  4% (1)
• B
  8% (2)
• C
  16% (4)
• D
  72% (18)

Explanation

Explanation

Option D is correct because AWS Cloud WAN provides a centrally managed global network with network segments that enforce isolation between BUs - traffic within a segment (BU) is permitted, while cross-segment communication is blocked by default, making it the most operationally efficient solution that scales easily as new BUs and Regions are added.

Why the distractors fall short:

• Option A & C appear to be incomplete or improperly described versions of a Cloud WAN solution - likely missing the critical configuration of separate network segments per BU, which is the key mechanism that enforces workload isolation between business units.
• Option B (transit gateways per Region with peering) requires manual management of route tables and peering connections for every new Region or BU added, creating significant operational overhead that worsens as the company scales.

Memory Tip

Think of Cloud WAN segments = swimlanes: each BU gets its own lane on the highway - traffic flows freely within a lane but cannot cross into another. When you see requirements for multi-Region isolation + future scalability, Cloud WAN with segments is almost always the answer over transit gateway meshes, which become complex to manage at scale.

No community discussion yet for this question.