Question 740
At Westmoor Finance, an infrastructure review by the SD-WAN architecture team is evaluating cross-border collaboration across a multinational advisory firm WAN after a tenant onboarding change (FT-E-04-02). The review finds that after a broad SD-WAN template change engineers cannot identify which install altered the site route policy. 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: Require change tickets to reference installed policy versions; make it a repeatable part of Westmoor Finance's change assurance (FT-E-04-02). It sustains the corrective action, use centralized installation history and administrator attribution for the target device or policy package, and must preserve the requirement that client data respects approved regional egress and retention.
Incorrect Answers
The source case reports that after a broad SD-WAN template change engineers cannot identify which install altered the site route policy. “Audit service provider admin assignments during renewals; include a negative-authorization regression case” maintains another technical control: Audit service provider admin assignments during renewals; include a negative-authorization regression case. It does not directly prevent this case’s specific recurrence, for which “Require change tickets to reference installed policy versions; include explicit primary and alternate path tests” addresses: Require change tickets to reference installed policy versions; include explicit primary and alternate path tests.
The source case reports that after a broad SD-WAN template change engineers cannot identify which install altered the site route policy. That ongoing review concerns: Audit out-of-band edits before scheduled installation jobs; use a measured acceptance threshold where relevant. The governing risk here is: Require change tickets to reference installed policy versions; include explicit primary and alternate path tests. Maintain “Require change tickets to reference installed policy versions; include explicit primary and alternate path tests” as the case-specific check.
The source case reports that after a broad SD-WAN template change engineers cannot identify which install altered the site route policy. The alternative is a useful recurring check for: Maintain consistent time sources and user identifiers across logging domains; retain the evidence under approved change control. The present failure instead depends on: Require change tickets to reference installed policy versions; include explicit primary and alternate path tests. The targeted safeguard is “Require change tickets to reference installed policy versions; include explicit primary and alternate path tests”.