Question 20
At Pinecrest University, an infrastructure review by the campus network security team is evaluating staff research access across a multicampus network after an audit of cloud access (FT-A-03-01). The review finds that a managed provider plans a common configuration package that mixes two customers' branch address spaces. Any correction must respect this operating requirement: research network identities must not inherit student public access. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Audit provider role boundaries before each large template rollout; make it a repeatable part of Pinecrest University's change assurance (FT-A-03-01). It sustains the corrective action, partition tenant-specific templates and administrative scopes while sharing only approved common baselines, and must preserve the requirement that research network identities must not inherit student public access.
Incorrect Answers
The source case reports that a managed provider plans a common configuration package that mixes two customers' branch address spaces. “Validate underlay reachability before changing overlay routing; repeat checks when the client or PoP version changes” maintains another technical control: Validate underlay reachability before changing overlay routing; repeat checks when the client or PoP version changes. It does not directly prevent this case’s specific recurrence, for which “Audit provider role boundaries before each large template rollout; use a measured acceptance threshold where relevant” addresses: Audit provider role boundaries before each large template rollout; use a measured acceptance threshold where relevant.
The source case reports that a managed provider plans a common configuration package that mixes two customers' branch address spaces. That ongoing review concerns: Maintain regional route-policy baselines with explicit failover acceptance tests; retain the evidence under approved change control. The governing risk here is: Audit provider role boundaries before each large template rollout; use a measured acceptance threshold where relevant. Maintain “Audit provider role boundaries before each large template rollout; use a measured acceptance threshold where relevant” as the case-specific check.
The source case reports that a managed provider plans a common configuration package that mixes two customers' branch address spaces. The alternative is a useful recurring check for: Include policy-zone audits alongside SD-WAN rollout checks; document the result for the next audit cycle. The present failure instead depends on: Audit provider role boundaries before each large template rollout; use a measured acceptance threshold where relevant. The targeted safeguard is “Audit provider role boundaries before each large template rollout; use a measured acceptance threshold where relevant”.