ANS-C01 · Question #264
A company has configured an AWS Cloud WAN core network with edge locations in the us-east- 1 Region and the us-west-1 Region. Each edge location has two segments: development and staging. The…
The correct answer is D. Update the core network policy to add a static route for each segment. Configure a route to direct. To enable communication between VPCs attached to different AWS Cloud WAN segments, the core network policy must be updated to define explicit static routes that allow traffic flow between those segments.
Question
A company has configured an AWS Cloud WAN core network with edge locations in the us-east- 1 Region and the us-west-1 Region. Each edge location has two segments: development and staging. The segments use the default core network policy. The company has attached VPCs to the core network. A development VPC is attached to the development segment in us-east-1 and is configured to use the 10.0.0.0/16 CIDR block. A staging VPC is attached to the staging segment in us-west-1 and is configured to use the 10.5.0.0/16 CIDR block. The company has updated the route tables for both VPCs with a route that directs any traffic for 0.0.0.0/0 to the core network. The company's network team needs to establish communication between the two VPCs by using the AWS Cloud WAN core network. The network team is not receiving a response during tests of communication between the VPCs. The network team has verified that security groups and network ACLs are not blocking the traffic. What should the network team do to establish this communication?
Options
- AUpdate both VPC route tables to have a new static route. Configure a route on the development
- BUpdate the segment filter to allow traffic on the development and staging segments.
- CSet the isolate-attachments parameter to False for the development and staging segments.
- DUpdate the core network policy to add a static route for each segment. Configure a route to direct
How the community answered
(46 responses)- A7% (3)
- B28% (13)
- C15% (7)
- D50% (23)
Why each option
To enable communication between VPCs attached to different AWS Cloud WAN segments, the core network policy must be updated to define explicit static routes that allow traffic flow between those segments.
Updating VPC route tables configures traffic to be sent *to* the core network, but it does not define how the Cloud WAN core network itself routes traffic *between* its internal segments.
There is no standard 'segment filter' mechanism in AWS Cloud WAN for enabling inter-segment routing; routing between segments is controlled by explicit configuration within the core network policy.
The `isolate-attachments` parameter controls whether attachments *within the same segment* can communicate with each other, not whether attachments in *different* segments can communicate.
AWS Cloud WAN segments are isolated by default, and to enable communication between VPCs attached to different segments (e.g., development and staging), the core network policy must be modified to define static routes that direct traffic between their respective CIDR blocks.
Concept tested: AWS Cloud WAN inter-segment routing policy
Source: https://docs.aws.amazon.com/cloudwan/latest/ug/segments.html
Community Discussion
No community discussion yet for this question.