Your organization uses FortiManager to manage 50 FortiGates across multiple locations. You have recently enabled workspace mode on your main ADOM to allow multiple administrators to work concurrently on policy changes. However, you notice that when Administrator A locks the ADOM to make critical changes, Administrator B is blocked from accessing any configuration until the lock is released.
What is the intended purpose of ADOM locking in workspace mode, and which statement accurately describes the behavior?
Show Answer
Hide Answer
Correct Answer:
A
When workspace mode is enabled on an ADOM, administrators can use ADOM locking to prevent concurrent access during critical operations. When an ADOM is locked, only the administrator who holds the lock can make changes; all other administrators are blocked from editing until the lock is released. This ensures database integrity during important configuration modifications.
Why other options are incorrect:
- Option 2: While workspace mode does allow concurrent editing within an ADOM, locking at the ADOM level is a coarser mechanism that blocks all access, not just conflicting policies. Per-policy locking requires per-policy lock controls.
- Option 3: Per-policy locking is a separate feature from ADOM locking. ADOM locking is an ADOM-wide mechanism. Per-policy locks allow fine-grained control at the individual policy level.
- Option 4: ADOM locking in workspace mode is manual and under administrator control. Workspace mode enables the capability for concurrent editing, but locking is an optional action administrators take when needed.
