Configure Workspace Mode NSE6-FORTIMANAGER-ADMINISTRATOR Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   What is the primary implication of concurrent ADOM access in FortiManager when workspace mode is disabled?

   • AChanges are saved to a temporary area and must be explicitly merged by an administrator.
   • BChanges made by one administrator are automatically propagated to all other logged-in administrators.
   • CAdministrators must take turns accessing the ADOM to avoid being locked out.
   • DThe last administrator to save changes can overwrite the changes made by others.
   Reveal Solution Discussion Select an answer first
2. 12foundation · medium

   In FortiManager, how does enabling workspace mode primarily support a change management process?

   • AIt requires administrators to lock an ADOM before making changes and to install those changes for them to take effect, enabling controlled review and deployment.
   • BIt automatically rolls back any configuration change that is not approved by a second administrator.
   • CIt automatically saves a snapshot of the configuration before every change and requires a manager to approve the snapshot before it becomes active.
   • DIt prevents all administrators from making changes unless a separate change-management server grants approval in real time.
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   An administrator locks an ADOM in advanced workspace mode to implement a new security policy. Another administrator attempts to edit an object in the same ADOM. What will the second administrator experience?

   • AThey receive a message that the ADOM is locked and can only view the configuration
   • BThey can edit the object but changes are not saved until the lock is released
   • CThey are logged out of FortiManager automatically
   • DThey can request lock ownership and take over the lock
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   A FortiManager administrator is evaluating workspace modes for a new ADOM. The team has a mix of experienced and junior administrators. The goal is to prevent accidental changes while still allowing junior administrators to make approved changes without requiring a super administrator for every modification. Which workspace mode and configuration would best achieve this?

   • ANormal mode with global locking and role-based access control granting edit permissions to junior administrators
   • BNormal mode with per-ADOM locking and role-based access control granting edit permissions to junior administrators
   • CDisabled mode with role-based access control granting edit permissions to junior administrators
   • DAdvanced mode with per-ADOM locking and role-based access control granting edit permissions to junior administrators
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   An administrator is troubleshooting an issue where an ADOM cannot be locked because it appears to be locked by a user account that was deleted from FortiManager. The lock is not visible in the GUI, and the administrator cannot unlock it. What is the most effective way to resolve this?

   • ARecreate the deleted user account and then unlock the ADOM
   • BUse the CLI to clear the lock with the 'execute adom unlock' command and the deleted user's name
   • CRestart the FortiManager service to clear all locks
   • DContact Fortinet support to manually clear the lock
   Reveal Solution Discussion Select an answer first