200-301: Cisco Certified Network AssociateDemo

Two independent static-route designs each satisfy the requirement on their own. Configuring a single default route of equal administrative distance toward each ISP gateway (0.0.0.0 0.0.0.0 toward 198.51.100.1 and toward 203.0.113.1) causes the router to install both as equal-cost paths, so CEF load-shares outbound traffic across ISP1 and ISP2, and if either next hop becomes unreachable the surviving default route alone continues to carry all traffic, giving redundancy. Splitting the entire address space into two /1 static routes toward each ISP achieves the same split-and-fail-over behavior only when it is paired with full 0.0.0.0/0 default routes to both ISPs as a less-specific backup, which is exactly what one option provides by combining the halved routes with the two full default routes. A route pair using unusually high administrative distances (255) is effectively unreachable/unused, an unpaired /1 split without any covering default route leaves half the address space with no path if its ISP fails, and a floating static default route (differing administrative distances) only fails over rather than load-balancing, so those designs do not meet both stated goals simultaneously.