During a scheduled failover test for the library catalog, cutover is delayed because DNS TTLs keep clients pointed at the old site. What does this outcome mainly illustrate?
Select an answer to reveal the explanation.
Short Explanation
The failover drill did its job—it showed that sticky DNS TTLs were slowing the cutover. Better to learn that on a calm Tuesday than during a real outage. Testing recovery is how you find the hidden speed bumps.
Full Explanation
Failover and recovery tests validate that designed resilience works within required timeframes and expose configuration issues such as long DNS TTLs that delay client cutover. Brochure claims and tabletop-only exercises cannot reveal those technical blockers. Ignoring DNS timing leaves a latent failure mode until a live incident. Incorporating failover testing into resilience practice improves confidence that recovery architecture meets operational needs.