Question 60
At Westmoor Finance, an infrastructure review by the SD-WAN architecture team is evaluating cross-border collaboration across a multinational advisory firm WAN following an underlay circuit upgrade (FT-B-07-02). The review finds that an engineer adds a static default route but policy-routed flows still follow an unexpected overlay. Any correction must respect this operating requirement: client data respects approved regional egress and retention. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Audit policy routes before changing default-route metrics; make it a repeatable part of Westmoor Finance's change assurance (FT-B-07-02). It sustains the corrective action, inspect policy routing and normal route lookup order for the specific session, and must preserve the requirement that client data respects approved regional egress and retention.
Incorrect Answers
The source case reports that an engineer adds a static default route but policy-routed flows still follow an unexpected overlay. “Maintain a lab record of primary and alternate route selection; schedule a recorded review after topology changes” maintains another technical control: Maintain a lab record of primary and alternate route selection; schedule a recorded review after topology changes. It does not directly prevent this case’s specific recurrence, for which “Audit policy routes before changing default-route metrics; include explicit primary and alternate path tests” addresses: Audit policy routes before changing default-route metrics; include explicit primary and alternate path tests.
The source case reports that an engineer adds a static default route but policy-routed flows still follow an unexpected overlay. That ongoing review concerns: Verify overlay prefix advertisements after subnet changes; use a measured acceptance threshold where relevant. The governing risk here is: Audit policy routes before changing default-route metrics; include explicit primary and alternate path tests. Maintain “Audit policy routes before changing default-route metrics; include explicit primary and alternate path tests” as the case-specific check.
The source case reports that an engineer adds a static default route but policy-routed flows still follow an unexpected overlay. “Review application classification after signature updates; retain the evidence under approved change control” maintains another technical control: Review application classification after signature updates; retain the evidence under approved change control. It does not directly prevent this case’s specific recurrence, for which “Audit policy routes before changing default-route metrics; include explicit primary and alternate path tests” addresses: Audit policy routes before changing default-route metrics; include explicit primary and alternate path tests.