A community college district needs traffic for one records server at 10.88.5.20 to take a dedicated path. Which IPv4 static matches that requirement?
Select an answer to reveal the explanation.
Short Explanation
One VIP server is a single mailbox, not the whole street. A /32 host static pins just that address to the path you want — defaults and /24s are too broad for that surgical job.
Full Explanation
When community college district traffic for one records server at 10.88.5.20 must take a dedicated path, the matching construct is an IPv4 host static: 10.88.5.20/32 (mask 255.255.255.255) with the chosen next hop. Host routes are the most specific IPv4 unicast routes; longest-prefix match ensures that only packets to that server use the dedicated uplink, while the rest of any encompassing /24 or summary continues to follow its existing network route.
A default 0.0.0.0/0 is too broad—it neither pins the server nor guarantees the dedicated path for that host alone. A /24 network route covers the entire subnet equally and cannot by itself prefer a single host over other addresses in the same LAN without an accompanying longer /32. An IPv6 ::1 loopback static is unrelated to forwarding IPv4 packets to 10.88.5.20.
Exam caveat: if both a /24 and a /32 exist, the /32 wins for that host even if the /24 has a better AD; AD is consulted only among same-prefix-length candidates from different sources. Operational check: install the /32, confirm it appears in the routing table, traceroute to 10.88.5.20 and to another host in the same subnet, and verify only the records server uses the dedicated next hop while sibling addresses still follow the broader route.