Question 350
At Bluehaven Telecom, an infrastructure review by the carrier access engineering group is evaluating customer support tool reachability across a metropolitan customer service network after the last approved policy installation (FT-E-02-01). The review finds that a regional operator can assign new branch identities and silently push organization-wide access policy changes. Any correction must respect this operating requirement: service management data cannot cross tenant boundaries. Which architectural or operational principle best explains the appropriate correction?
Explanation
Correct Answer
The relevant design principle is: Administrative separation of duties reduces accidental high-impact configuration changes. In this customer support tool reachability decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that a regional operator can assign new branch identities and silently push organization-wide access policy changes; the intended approach is to create distinct FortiManager administrative roles and approval scopes for provisioning and policy installation. The distinguishing confirmation is that A provisioning-only test operator cannot approve or install a global security change.
Incorrect Answers
The source case reports that a regional operator can assign new branch identities and silently push organization-wide access policy changes. The alternative states a real but different technical principle: Multi-tenant management boundaries are separate from the customer traffic plane; do not infer authorization solely from connectivity. The facts in this question are explained by: Administrative separation of duties reduces accidental high-impact configuration changes; distinguish desired policy from effective enforcement.
The source case reports that a regional operator can assign new branch identities and silently push organization-wide access policy changes. That principle controls the offered alternative: Visibility and configuration authority depend on establishing the right management relationship; avoid assuming a healthy session proves all services work. It is not the causal distinction established here: Administrative separation of duties reduces accidental high-impact configuration changes; distinguish desired policy from effective enforcement.
The source case reports that a regional operator can assign new branch identities and silently push organization-wide access policy changes. The alternative states a real but different technical principle: IPsec failures can occur before routing or application policy is relevant; do not infer authorization solely from connectivity. The facts in this question are explained by: Administrative separation of duties reduces accidental high-impact configuration changes; distinguish desired policy from effective enforcement.