Your organization uses FortiManager to manage 50 FortiGates across multiple locations. You have recently enabled workspace mode on your main ADOM to…

Workspace mode in FortiManager provides concurrency control and administrative locking to prevent simultaneous configuration changes that could corrupt the database or create conflicts. When an administrator locks an ADOM, FortiManager grants exclusive write access to that administrator, putting all other administrators into a read-only state for that specific ADOM. This ensures database integrity and prevents race conditions during major configuration changes. Until the holding administrator saves, commits, or unlocks the ADOM session, other administrators cannot make modifications. This mechanism explicitly explains why Administrator B is blocked from making changes while Administrator A holds the exclusive ADOM lock.

B: ADOM locking restricts write access to a single administrator for the entire ADOM, rather than allowing simultaneous editing by multiple administrators.

C: ADOM locking applies at the entire ADOM level in this mode, not at a per-policy granular level.

D: ADOM locking must be explicitly performed by administrators when entering read/write mode, rather than being unmanageable and automatic.

- Fortinet

FortiManager 7.2.0 Administration Guide

Section: "Workspace mode and ADOM locking"

pp. 185–190.

- Fortinet

FortiManager 7.4.0 Administration Guide

Section: "Concurrent administration and session locks"

pp. 192–197.