Question 130
At Bayline Logistics, an infrastructure review by the branch operations engineers is evaluating warehouse application transport across a multiwarehouse distribution fabric while testing an alternate WAN provider (FT-B-18-02). The review finds that one hub outage leaves remaining tunnels established but branch prefixes unreachable. Any correction must respect this operating requirement: warehouse scanning must remain available during carrier loss. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Include hub-loss cases in scheduled private access exercises; make it a repeatable part of Bayline Logistics's change assurance (FT-B-18-02). It sustains the corrective action, verify alternate hub IPsec and BGP adjacency plus route convergence behavior, and must preserve the requirement that warehouse scanning must remain available during carrier loss.
Incorrect Answers
The source case reports that one hub outage leaves remaining tunnels established but branch prefixes unreachable. The alternative is a useful recurring check for: Monitor asymmetric path changes during failover drills; use a measured acceptance threshold where relevant. The present failure instead depends on: Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant. The targeted safeguard is “Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant”.
The source case reports that one hub outage leaves remaining tunnels established but branch prefixes unreachable. “Track loopback advertisements and reachability before migrating overlays; confirm this in the next branch rollout checklist” maintains another technical control: Track loopback advertisements and reachability before migrating overlays; confirm this in the next branch rollout checklist. It does not directly prevent this case’s specific recurrence, for which “Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant” addresses: Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant.
The source case reports that one hub outage leaves remaining tunnels established but branch prefixes unreachable. That ongoing review concerns: Check rule hits and shadowing in each SD-WAN policy review; include a negative-authorization regression case. The governing risk here is: Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant. Maintain “Include hub-loss cases in scheduled private access exercises; use a measured acceptance threshold where relevant” as the case-specific check.