156-561 · Question #69
In Amazon Web Services, what is the level of segmentation you can achieve?
The correct answer is C. Internet to VPC, VPC to VPC and Subnet to Subnet. AWS natively supports segmentation at three hierarchical layers: Internet to VPC (controlled via Internet Gateways and security groups at the boundary), VPC to VPC (via VPC Peering or Transit Gateway), and Subnet to Subnet (via Network ACLs and route tables within a VPC)…
Question
In Amazon Web Services, what is the level of segmentation you can achieve?
Options
- AVPC to VPC only
- BVPC to VPC and VM to VM (micro segmentation)
- CInternet to VPC, VPC to VPC and Subnet to Subnet
- DVM to VM (micro segmentation) and Internet to VPC
How the community answered
(27 responses)- A4% (1)
- B7% (2)
- C85% (23)
- D4% (1)
Explanation
AWS natively supports segmentation at three hierarchical layers: Internet to VPC (controlled via Internet Gateways and security groups at the boundary), VPC to VPC (via VPC Peering or Transit Gateway), and Subnet to Subnet (via Network ACLs and route tables within a VPC) - making C the complete and accurate answer.
Why the distractors fail:
- A is too narrow - it captures only one of the three segmentation levels and ignores internet-facing and intra-VPC boundaries.
- B swaps out subnet-level segmentation for "micro-segmentation," which is a term more associated with hypervisor-level SDN solutions (like VMware NSX) rather than AWS's native model.
- D combines Internet-to-VPC (correct) with VM-to-VM micro-segmentation (incorrect framing for AWS), while missing both VPC-to-VPC and Subnet-to-Subnet tiers.
Memory tip: Picture AWS segmentation as a funnel - traffic flows inward through three gates: the Internet → VPC edge, across VPC ↔ VPC peering links, then down to Subnet ↔ Subnet boundaries. If an answer skips any of those three gates or replaces "subnet" with "VM," it's wrong.
Topics
Community Discussion
No community discussion yet for this question.