The configuration Concurrent ADOM Access: Allow explicitly permits a single administrator account to access and therefore lock multiple ADOMs simultaneously. This makes option D correct.

ADOM locking is tied to an administrator's session. If the session terminates ungracefully (e.g., browser crash, network loss), the lock is not released. The ADOM remains locked to prevent data inconsistency until the administrator's idle session times out or another administrator with override permissions manually unlocks it. This makes option B correct.

A. Unlocking an ADOM will submit configuration changes automatically to the approval administrator.

This describes a feature of Workspace Mode, which is explicitly Disabled in the exhibit. In Normal mode, there is no submission or approval workflow.

C. Unlocking an ADOM will install configuration changes automatically on managed devices.

Unlocking an ADOM and installing a configuration are two distinct and separate administrative actions. Unlocking only makes the ADOM available for other administrators to edit.

1. FortiManager Administration Guide 7.4.1

Page 101

"System Settings pane":

Under the ADOM section

the guide describes the Concurrent ADOM Access setting: "Select to allow administrators to access multiple ADOMs at the same time." This directly validates option D.

The guide also describes Workspace Mode

confirming its features are not active when disabled

which invalidates option A.

2. FortiManager Administration Guide 7.4.1

Page 98

"ADOMs":

This section explains the ADOM locking mechanism: "When an administrator is making configuration changes in an ADOM

the ADOM is locked to prevent other administrators from making changes at the same time." It further explains that locks are tied to sessions. If a session ends abnormally

the lock persists until the session idle timeout

validating the behavior described in option B.

3. FortiManager Administration Guide 7.4.1

Page 323

"Install policies and objects":

This section details the installation process as a separate

deliberate step initiated by an administrator using the Install Wizard. This confirms that unlocking an ADOM (a configuration management action) does not trigger an installation

invalidating option C.