Question 120
At Evergreen Services, an infrastructure review by the network assurance team is evaluating contractor and staff applications across a regional professional-services firm after an audit of cloud access (FT-E-01-02). The review finds that a branch policy is corrected locally but the next FortiManager install overwrites it from a stale template. Any correction must respect this operating requirement: contractors receive only explicitly authorized private resources. Which result is the strongest evidence that the corrective approach succeeded?
Explanation
Correct Answer
This is the most direct validation of the stated failure: In a controlled a regional professional-services firm acceptance test, The installed FortiGate configuration retains the approved setting after a second policy push; the outcome is recorded under Evergreen Services's rollout (FT-E-01-02). It tests the result of the proposed action, correct the authoritative managed template and install using a reviewed change workflow, rather than a separate feature or an unrelated path metric. The relevant principle is that Central management is authoritative over the managed device configuration.
Incorrect Answers
The source case reports that a branch policy is corrected locally but the next FortiManager install overwrites it from a stale template. The proposed evidence concerns: Visibility and configuration authority depend on establishing the right management relationship. The current question instead requires an outcome tied to: Central management is authoritative over the managed device configuration. The direct observation is “The installed FortiGate configuration retains the approved setting after a second policy push; record the specific tenant and user identities”.
The source case reports that a branch policy is corrected locally but the next FortiManager install overwrites it from a stale template. “The unexpected change is linked to a specific install event revision and actor; reproduce it with documented network endpoints” tests the distinct technical dependency: Versioned central management supplies change lineage beyond the running device state. This test could pass while the stated failure remains. The direct verification here is “The installed FortiGate configuration retains the approved setting after a second policy push; record the specific tenant and user identities” because central management is authoritative over the managed device configuration.
The source case reports that a branch policy is corrected locally but the next FortiManager install overwrites it from a stale template. That observation would support a control associated with: Troubleshooting should correlate flow selection and observed performance rather than guess. It does not prove the specific correction worked. Confirm “The installed FortiGate configuration retains the approved setting after a second policy push; record the specific tenant and user identities” against: Central management is authoritative over the managed device configuration.