AWS Certified Advanced Networking Specialty Practice Exam

Disable ads (and more) with a membership for a one time $4.99 payment

Question: 1 / 150

When configuring a route to on-premises infrastructure, what is true about overlapping CIDR ranges?

This will always result in routing failures.

The more specific route takes precedence.

When configuring routes to integrate on-premises infrastructure with your cloud network, understanding how overlapping CIDR ranges are prioritized is vital. In this case, if there are overlapping CIDR ranges, the more specific route indeed takes precedence.

This means that if two routes exist, one being a broader CIDR (larger range of IPs) and the other being a more specific CIDR (smaller range of IPs), the routing table will utilize the more specific route for decision-making. This behavior is due to the way route selection works in networking, where specificity helps in determining the exact path for packets based on the longest prefix match.

In scenarios where multiple routes could potentially direct traffic, the specific route enables finer control over the traffic destination, potentially solving issues associated with address space overlaps. This is particularly useful in hybrid configurations or multi-tenancy situations where different systems or customers might overlap in their address designs.

Choosing an option that states that overlapping CIDR ranges will always result in routing failures overlooks the nuanced behavior of routing tables and their capacity to resolve ambiguity through specificity. Instead, it is crucial to comprehend and apply the precedence rules effectively to ensure a smooth integration of on-premises infrastructure with cloud environments.

The original CIDR always takes precedence.

Routing can be successful without any overlapping CIDR ranges.

Next

Report this question