Courseiva
Network DesignhardMultiple ChoiceObjective-mapped

ANS-C01 Network Design Practice Question

A company has a VPC with a CIDR of 10.0.0.0/16 and needs to peer with another VPC with CIDR 10.0.0.0/16. They plan to use a transit gateway to connect the VPCs. What is the correct approach to handle the overlapping CIDR ranges?

⚠ Common exam trap

AWS often tests the misconception that a transit gateway can perform NAT or otherwise magically handle overlapping CIDRs, but in reality, AWS transit gateways are pure Layer-3 routers that require unique destination prefixes for correct forwarding.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Create a new VPC with a non-overlapping CIDR and migrate resources from one of the existing VPCs.

Transit gateways do not perform NAT or resolve overlapping CIDR conflicts between attached VPCs. When two VPCs have identical CIDR blocks (10.0.0.0/16), the transit gateway cannot route traffic correctly because it cannot distinguish between the two networks. The only viable solution is to create a new VPC with a non-overlapping CIDR and migrate resources from one of the existing VPCs, eliminating the conflict at the network layer.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Create a new VPC with a non-overlapping CIDR and migrate resources from one of the existing VPCs.

    Why this is correct

    This resolves the overlap by eliminating it.

  • Create a VPC peering connection and use a smaller subnet CIDR for traffic filtering.

    Why it's wrong here

    VPC peering does not allow overlapping CIDRs.

  • Use a transit gateway with network address translation (NAT) to translate one VPC CIDR to a non-overlapping range.

    Why it's wrong here

    Transit gateway does not do NAT.

  • Configure the transit gateway with equal-cost multipath (ECMP) to load balance traffic between the overlapping CIDRs.

    Why it's wrong here

    ECMP does not resolve overlap.

Visual reference

Inside (Private) PC-A 10.0.0.1 PC-B 10.0.0.2 NAT Router Outside (Public) 203.0.113.1 Inside Global Server PAT: many private IPs share one public IP via unique port numbers

About these practice questions

One of 1,621 original ANS-C01 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

4 more ways this is tested on ANS-C01

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A company has a VPC with a CIDR of 10.0.0.0/16 and needs to connect to another VPC with CIDR 10.0.0.0/16 via VPC Peering. They encounter an error because of overlapping CIDRs. Which TWO actions can resolve this issue?

medium
  • A.Use a subnet-level peering connection
  • B.Create a new VPC with a non-overlapping CIDR and peer with that
  • C.Modify the CIDR of one VPC to a non-overlapping range
  • D.Use AWS Transit Gateway with separate route tables
  • E.Use a NAT Gateway to translate IPs

Why B: Creating a new VPC with a non-overlapping CIDR and establishing a VPC peering connection resolves the conflict. VPC peering requires that the CIDR blocks of the two VPCs do not overlap, as overlapping ranges prevent proper route table entries and cause routing ambiguity. By using a non-overlapping CIDR, you enable direct connectivity between the VPCs without IP address conflicts.

Variation 2. A company has a VPC with a CIDR of 10.0.0.0/16 and wants to connect to another VPC with CIDR 10.0.0.0/16 in a different account. The VPCs are in the same region. Which THREE steps are necessary to establish connectivity? (Choose THREE.)

hard
  • A.Change the CIDR block of one VPC to a non-overlapping range.
  • B.Create VPC endpoints in each VPC for the other VPC's services.
  • C.Set up a VPN connection between the VPCs.
  • D.Create a VPC peering connection request from one account and accept it in the other.
  • E.Update route tables in both VPCs to add routes for the peered VPC CIDR.

Why A: VPC peering requires non-overlapping CIDR blocks. Since both VPCs use 10.0.0.0/16, they have identical address spaces, which makes routing ambiguous and prevents the peering connection from being established. AWS enforces this rule to ensure that route tables can uniquely direct traffic between the peered VPCs without conflicts.

Variation 3. A company has a VPC with a CIDR of 10.0.0.0/16. They need to peer with another VPC that has a CIDR of 10.0.0.0/24. What will happen?

hard
  • A.The peering connection will be established, but only the first VPC's CIDR will be used.
  • B.The peering connection will be established, but routes with overlapping CIDRs will not be added automatically.
  • C.The peering connection will fail because the CIDRs overlap.
  • D.The peering connection will be established, and the overlapping CIDRs will be ignored.

Why C: AWS VPC peering requires that the CIDR blocks of the two VPCs do not overlap. When both VPCs use the same IP range (10.0.0.0/16 and 10.0.0.0/24), the peering connection request will fail because overlapping CIDRs create routing ambiguity and are not supported by the VPC peering service. This is a hard limit enforced at the time of peering creation, not during route table configuration.

Variation 4. A company has a VPC with a CIDR of 10.0.0.0/16 and needs to peer with another VPC that has CIDR 10.0.0.0/16. What is the issue and how can it be resolved?

easy
  • A.The VPCs can be peered if you enable DNS resolution.
  • B.The VPCs have overlapping CIDRs, so they cannot be directly peered. You must re-IP one VPC or use a NAT solution.
  • C.Use a Transit Gateway to connect the VPCs, which supports overlapping CIDRs.
  • D.Use a Direct Connect Gateway to connect the VPCs, which ignores CIDR overlap.

Why B: VPC peering requires non-overlapping CIDR blocks because the route tables in each VPC must have distinct destination prefixes to route traffic correctly. When both VPCs use 10.0.0.0/16, the routes are identical, causing ambiguity and preventing the peering connection from being established. The only resolution is to change the CIDR of one VPC or use a NAT-based solution to translate addresses.

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This ANS-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ANS-C01 exam.