Practice Exams:

Fortinet FCP_FMG_AD-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiManager 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FMG_AD-7.6 Premium ETE File


  • Premium File 62 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FMG_AD-7.6 Practice Test 13

Question 120

An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Verify: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.
  2. Implement: Set each ADOM to a supported FortiOS compatibility version for its managed devices and plan the official ADOM upgrade or migration path before introducing gateways on newer firmware. Verify: Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status.
  3. Implement: Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure. Verify: Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status.
  4. Implement: Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure. Verify: Compare a staged FortiGate's FortiOS version with the ADOM target version, verify management and object editor compatibility, and rehearse a supported one-click ADOM upgrade in the lab.

Answer & Explanations

Correct answer: C

A.

This action/test pair addresses “Coordinate ADOM administrative privileges and multi-administrator sessions”. Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. The case instead calls for: Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure.

B.

The test would be relevant: Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status. But the offered implementation—Set each ADOM to a supported FortiOS compatibility version for its managed devices and plan the official ADOM upgrade or migration path before introducing gateways on newer firmware.—addresses “Keep ADOM firmware version compatibility aligned with managed FortiGate releases”. The action needed here is: Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure.

C.

The question is set in this situation: An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure. Confirm it through this test: Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status. An ADOM move changes the management database and package context for a device; dragging a device label between groups is not equivalent to reconciling its interface mappings, imported rules and target ADOM compatibility.

D.

The action is applicable: Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure. But its proposed test—Compare a staged FortiGate's FortiOS version with the ADOM target version, verify management and object editor compatibility, and rehearse a supported one-click ADOM upgrade in the lab.—addresses “Keep ADOM firmware version compatibility aligned with managed FortiGate releases”. This requirement is confirmed instead by: Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status.

Question 121

A large insurer is dividing management duties between a global security team and regional analysts who must not alter production firewall packages. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Configure supported administrative domains that match independent customers or security jurisdictions, assign managed devices and administrators to correct ADOMs, and verify object and policy isolation.
  2. Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow.
  3. Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.
  4. Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates.

Answer & Explanations

Correct answer: C

A.

Configure supported administrative domains that match independent customers or security jurisdictions, assign managed devices and administrators to correct ADOMs, and verify object and policy isolation. This addresses “Divide a multi-customer FortiManager environment into appropriate ADOMs”, where the governing principle is: ADOMs partition FortiManager's management scope and databases; a descriptive device group by itself does not create isolation between customers or prevent an administrator from editing shared policy objects. The stated case instead calls for: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

B.

Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow. This addresses “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, where the governing principle is: ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed. The stated case instead calls for: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

C.

Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions. Verify the result with this test: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

D.

Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates. This addresses “Complete initial FortiManager system networking and administrator hardening”, where the governing principle is: FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. The stated case instead calls for: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

Question 122

A large insurer is dividing management duties between a global security team and regional analysts who must not alter production firewall packages. The engineer proposes the following change: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Which mechanism explains why it works?

  1. Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.
  2. ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed.
  3. FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation.
  4. ADOMs partition FortiManager's management scope and databases; a descriptive device group by itself does not create isolation between customers or prevent an administrator from editing shared policy objects.

Answer & Explanations

Correct answer: A

A.

Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions. The corresponding implementation is: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

B.

ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed. That explains “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, not the mechanism behind the described change. The relevant principle is: Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

C.

FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. That explains “Complete initial FortiManager system networking and administrator hardening”, not the mechanism behind the described change. The relevant principle is: Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

D.

ADOMs partition FortiManager's management scope and databases; a descriptive device group by itself does not create isolation between customers or prevent an administrator from editing shared policy objects. That explains “Divide a multi-customer FortiManager environment into appropriate ADOMs”, not the mechanism behind the described change. The relevant principle is: Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

Question 123

A large insurer is dividing management duties between a global security team and regional analysts who must not alter production firewall packages. After implementing this change—Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.—which test most directly validates its intended outcome?

  1. From an authorized management subnet connect to the new FortiManager, verify its route, clock and name resolution, deny an unapproved management source, and confirm no default shared administrator credential remains.
  2. Create two lab ADOMs with separate administrators and policy packages, verify a device and object from the first are unavailable for modification from the second, and document global policy exceptions.
  3. Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode.
  4. Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

Answer & Explanations

Correct answer: D

A.

From an authorized management subnet connect to the new FortiManager, verify its route, clock and name resolution, deny an unapproved management source, and confirm no default shared administrator credential remains. That would help test “Complete initial FortiManager system networking and administrator hardening”, not the outcome required in this scenario. The relevant acceptance check is: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

B.

Create two lab ADOMs with separate administrators and policy packages, verify a device and object from the first are unavailable for modification from the second, and document global policy exceptions. That would help test “Divide a multi-customer FortiManager environment into appropriate ADOMs”, not the outcome required in this scenario. The relevant acceptance check is: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

C.

Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode. That would help test “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, not the outcome required in this scenario. The relevant acceptance check is: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

D.

Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. This check is decisive because parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

Question 124

A large insurer is dividing management duties between a global security team and regional analysts who must not alter production firewall packages. Which proposed shortcut most directly risks untraceable privileged policy changes and multi-tenant exposure caused by shared FortiManager administrator credentials and should therefore be rejected?

  1. Expose a factory-default FortiManager management interface directly to the internet and begin registering branch gateways before setting a restricted administrator account or working route.
  2. Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes.
  3. Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority.
  4. Turn on a mode that omits required central policy management and assume FortiManager will still author and install the organization's shared firewall rule base exactly as before.

Answer & Explanations

Correct answer: B

A.

Expose a factory-default FortiManager management interface directly to the internet and begin registering branch gateways before setting a restricted administrator account or working route. That shortcut risks central management compromise or failed device onboarding from unprotected factory defaults and incomplete network bootstrap. Here the specific shortcut is: Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes.

B.

Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes. The foreseeable failure is untraceable privileged policy changes and multi-tenant exposure caused by shared FortiManager administrator credentials. The safer response is: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

C.

Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority. That shortcut risks cross-customer policy exposure after using device organization labels as a substitute for ADOM isolation. Here the specific shortcut is: Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes.

D.

Turn on a mode that omits required central policy management and assume FortiManager will still author and install the organization's shared firewall rule base exactly as before. That shortcut risks missing centralized policy functionality after selecting an ADOM management mode inconsistent with operational requirements. Here the specific shortcut is: Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes.

Question 125

A large insurer is dividing management duties between a global security team and regional analysts who must not alter production firewall packages. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow. Verify: Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode.
  2. Implement: Configure supported administrative domains that match independent customers or security jurisdictions, assign managed devices and administrators to correct ADOMs, and verify object and policy isolation. Verify: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.
  3. Implement: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Verify: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.
  4. Implement: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Verify: Create two lab ADOMs with separate administrators and policy packages, verify a device and object from the first are unavailable for modification from the second, and document global policy exceptions.

Answer & Explanations

Correct answer: C

A.

This action/test pair addresses “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”. Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow. Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode. The case instead calls for: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

B.

The test would be relevant: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. But the offered implementation—Configure supported administrative domains that match independent customers or security jurisdictions, assign managed devices and administrators to correct ADOMs, and verify object and policy isolation.—addresses “Divide a multi-customer FortiManager environment into appropriate ADOMs”. The action needed here is: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

C.

Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Confirm it through this test: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

D.

The action is applicable: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. But its proposed test—Create two lab ADOMs with separate administrators and policy packages, verify a device and object from the first are unavailable for modification from the second, and document global policy exceptions.—addresses “Divide a multi-customer FortiManager environment into appropriate ADOMs”. This requirement is confirmed instead by: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

Question 126

A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.
  2. Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure.
  3. Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning.
  4. Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

Answer & Explanations

Correct answer: D

A.

Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. This addresses “Restore FortiManager ADOM content after a controlled management change”, where the governing principle is: ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state. The stated case instead calls for: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

B.

Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure. This addresses “Move a registered FortiGate between ADOMs through a supported workflow”, where the governing principle is: An ADOM move changes the management database and package context for a device; dragging a device label between groups is not equivalent to reconciling its interface mappings, imported rules and target ADOM compatibility. The stated case instead calls for: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

C.

Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning. This addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, where the governing principle is: Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. The stated case instead calls for: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

D.

The question is set in this situation: A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions. Verify the result with this test: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

Question 127

A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. The engineer proposes the following change: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Which mechanism explains why it works?

  1. Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.
  2. Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received.
  3. ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.
  4. An ADOM move changes the management database and package context for a device; dragging a device label between groups is not equivalent to reconciling its interface mappings, imported rules and target ADOM compatibility.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions. The corresponding implementation is: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

B.

Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. That explains “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the mechanism behind the described change. The relevant principle is: Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

C.

ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state. That explains “Restore FortiManager ADOM content after a controlled management change”, not the mechanism behind the described change. The relevant principle is: Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

D.

An ADOM move changes the management database and package context for a device; dragging a device label between groups is not equivalent to reconciling its interface mappings, imported rules and target ADOM compatibility. That explains “Move a registered FortiGate between ADOMs through a supported workflow”, not the mechanism behind the described change. The relevant principle is: Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

Question 128

A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. After implementing this change—Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.—which test most directly validates its intended outcome?

  1. Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status.
  2. Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.
  3. Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy.
  4. Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

Answer & Explanations

Correct answer: B

A.

Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status. That would help test “Move a registered FortiGate between ADOMs through a supported workflow”, not the outcome required in this scenario. The relevant acceptance check is: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

B.

The question is set in this situation: A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. This check is decisive because parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

C.

Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy. That would help test “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the outcome required in this scenario. The relevant acceptance check is: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

D.

Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages. That would help test “Restore FortiManager ADOM content after a controlled management change”, not the outcome required in this scenario. The relevant acceptance check is: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

Question 129

A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Which proposed shortcut most directly risks untraceable privileged policy changes and multi-tenant exposure caused by shared FortiManager administrator credentials and should therefore be rejected?

  1. Rename a branch firewall to match the destination customer and assume it automatically moves with its policies into a new ADOM without migration or version checks.
  2. Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate.
  3. Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes.
  4. Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.

Answer & Explanations

Correct answer: C

A.

Rename a branch firewall to match the destination customer and assume it automatically moves with its policies into a new ADOM without migration or version checks. That shortcut risks orphaned device or incorrect policy ownership after treating an ADOM move as a cosmetic rename. Here the specific shortcut is: Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes.

B.

Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate. That shortcut risks irreversible central policy history loss after failing to preserve management database and ADOM revisions. Here the specific shortcut is: Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes.

C.

The question is set in this situation: A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes. The foreseeable failure is untraceable privileged policy changes and multi-tenant exposure caused by shared FortiManager administrator credentials. The safer response is: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

D.

Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation. That shortcut risks missing security visibility after assuming central configuration automatically delivers usable analytics and log retention. Here the specific shortcut is: Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes.

Question 130

A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Verify: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.
  2. Implement: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Verify: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.
  3. Implement: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Verify: Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status.
  4. Implement: Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure. Verify: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Confirm it through this test: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

B.

This action/test pair addresses “Restore FortiManager ADOM content after a controlled management change”. Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages. The case instead calls for: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

C.

The action is applicable: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. But its proposed test—Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status.—addresses “Move a registered FortiGate between ADOMs through a supported workflow”. This requirement is confirmed instead by: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

D.

The test would be relevant: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. But the offered implementation—Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure.—addresses “Move a registered FortiGate between ADOMs through a supported workflow”. The action needed here is: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests