Question 20
A post-incident design review discusses the following: A core design wastes /24 subnets on each of thirty numbered router-to-router Ethernet links. Which preventive design control MOST DIRECTLY addresses this specific risk?
Explanation
Correct Answer
Document platform support for /31 and standardize point-to-point allocations in IPAM. This control targets the underlying design risk. RFC 3021 /31s can use both addresses on point-to-point links without ordinary network and broadcast host reservations. The follow-up acceptance check remains: Both router endpoints exchange routes and ping one another over a /31 while the overall address pool is conserved.
Incorrect Answers
IPv6 LAN autoconfiguration normally relies on a /64 subnet; a /48 supports many distinct /64 subnets. The repeat risk here is different: RFC 3021 /31s can use both addresses on point-to-point links without ordinary network and broadcast host reservations. A directly relevant preventive control is: Document platform support for /31 and standardize point-to-point allocations in IPAM.
Hierarchical IPv6 prefix planning supports route summarization and stable per-link /64 subnets. The repeat risk here is different: RFC 3021 /31s can use both addresses on point-to-point links without ordinary network and broadcast host reservations. A directly relevant preventive control is: Document platform support for /31 and standardize point-to-point allocations in IPAM.
Overlapping private address space prevents unambiguous ordinary IP routing between identical prefixes. The repeat risk here is different: RFC 3021 /31s can use both addresses on point-to-point links without ordinary network and broadcast host reservations. A directly relevant preventive control is: Document platform support for /31 and standardize point-to-point allocations in IPAM.