Question 530
At Falcon Security MSP, an infrastructure review by the provider services group is evaluating customer tenant connectivity across a managed multitenant edge platform during a regional modernization (FT-A-08-02). The review finds that a bulk device import assigns the wrong site names and WAN ports to several new branch gateways. Any correction must respect this operating requirement: one customer cannot see or change another customer network. Which ongoing control most directly reduces the chance of this issue returning?
Explanation
Correct Answer
This preventive control directly targets recurrence: Use pre-import lint and post-deployment spot checks for each cohort; make it a repeatable part of Falcon Security MSP's change assurance (FT-A-08-02). It sustains the corrective action, repair the CSV inventory mapping and validate a small staged import before wider provisioning, and must preserve the requirement that one customer cannot see or change another customer network.
Incorrect Answers
The source case reports that a bulk device import assigns the wrong site names and WAN ports to several new branch gateways. The alternative is a useful recurring check for: Exercise both directions of hub failover each change window; use a measured acceptance threshold where relevant. The present failure instead depends on: Use pre-import lint and post-deployment spot checks for each cohort; use a measured acceptance threshold where relevant. The targeted safeguard is “Use pre-import lint and post-deployment spot checks for each cohort; use a measured acceptance threshold where relevant”.
The source case reports that a bulk device import assigns the wrong site names and WAN ports to several new branch gateways. “Verify member-zone-policy relationships after circuit changes; repeat checks when the client or PoP version changes” maintains another technical control: Verify member-zone-policy relationships after circuit changes; repeat checks when the client or PoP version changes. It does not directly prevent this case’s specific recurrence, for which “Use pre-import lint and post-deployment spot checks for each cohort; use a measured acceptance threshold where relevant” addresses: Use pre-import lint and post-deployment spot checks for each cohort; use a measured acceptance threshold where relevant.
The source case reports that a bulk device import assigns the wrong site names and WAN ports to several new branch gateways. That ongoing review concerns: Retain timestamped SLA and member-state events for incident review; document the result for the next audit cycle. The governing risk here is: Use pre-import lint and post-deployment spot checks for each cohort; use a measured acceptance threshold where relevant. Maintain “Use pre-import lint and post-deployment spot checks for each cohort; use a measured acceptance threshold where relevant” as the case-specific check.