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 8

Question 70

A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. Verify: In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change.
  2. Implement: 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. Verify: In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change.
  3. Implement: Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. Verify: 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.
  4. Implement: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Verify: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. Confirm it through this test: In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change. An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.

B.

The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. The test would be relevant: In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change. But the offered implementation—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.—addresses “Complete initial FortiManager system networking and administrator hardening”. The action needed here is: Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan.

C.

The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. The action is applicable: Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. But its proposed test—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.—addresses “Complete initial FortiManager system networking and administrator hardening”. This requirement is confirmed instead by: In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change.

D.

The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. This action/test pair addresses “Preserve FortiManager configuration with a tested backup and restore method”. Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. The case instead calls for: Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan.

Question 71

A managed service provider is adding a contractor to administer one customer ADOM while prohibiting policy access to all other clients. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan.
  2. Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.
  3. Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.
  4. Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

Answer & Explanations

Correct answer: D

A.

Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. This addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”, where the governing principle is: An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. The stated case instead calls for: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

B.

Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. This addresses “Explain central management versus FortiGate enforcement responsibilities”, where the governing principle is: FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable. The stated case instead calls for: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

C.

Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. This addresses “Preserve FortiManager configuration with a tested backup and restore method”, where the governing principle is: Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. The stated case instead calls for: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

D.

Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. Verify the result with this test: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

Question 72

A managed service provider is adding a contractor to administer one customer ADOM while prohibiting policy access to all other clients. The engineer proposes the following change: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Which mechanism explains why it works?

  1. An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
  2. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.
  3. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.
  4. FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

Answer & Explanations

Correct answer: C

A.

An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. That explains “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the mechanism behind the described change. The relevant principle is: A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

B.

Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. That explains “Preserve FortiManager configuration with a tested backup and restore method”, not the mechanism behind the described change. The relevant principle is: A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

C.

A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. The corresponding implementation is: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

D.

FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable. That explains “Explain central management versus FortiGate enforcement responsibilities”, not the mechanism behind the described change. The relevant principle is: A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

Question 73

A managed service provider is adding a contractor to administer one customer ADOM while prohibiting policy access to all other clients. After implementing this change—Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.—which test most directly validates its intended outcome?

  1. In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change.
  2. Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.
  3. Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.
  4. Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

Answer & Explanations

Correct answer: D

A.

In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change. That would help test “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the outcome required in this scenario. The relevant acceptance check is: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

B.

Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. That would help test “Explain central management versus FortiGate enforcement responsibilities”, not the outcome required in this scenario. The relevant acceptance check is: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

C.

Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. That would help test “Preserve FortiManager configuration with a tested backup and restore method”, not the outcome required in this scenario. The relevant acceptance check is: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

D.

Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. This check is decisive because a successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

Question 74

A managed service provider is adding a contractor to administer one customer ADOM while prohibiting policy access to all other clients. Which proposed shortcut most directly risks unauthorized cross-tenant policy changes after conflating centralized authentication with least-privilege FortiManager authorization and should therefore be rejected?

  1. Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.
  2. Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.
  3. Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.
  4. Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path.

Answer & Explanations

Correct answer: C

A.

Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online. That shortcut risks loss of actual traffic filtering caused by confusing central configuration control with an enforcement gateway. Here the specific shortcut is: Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.

B.

Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations. That shortcut risks unrecoverable centralized policy and object history when a damaged management appliance lacks a valid tested backup. Here the specific shortcut is: Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.

C.

Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords. The foreseeable failure is unauthorized cross-tenant policy changes after conflating centralized authentication with least-privilege FortiManager authorization. The safer response is: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

D.

Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path. That shortcut risks stale management state and failed updates after treating offline staging capabilities as evidence of live connectivity. Here the specific shortcut is: Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.

Question 75

A managed service provider is adding a contractor to administer one customer ADOM while prohibiting policy access to all other clients. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Verify: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.
  2. Implement: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Verify: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.
  3. Implement: Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. Verify: In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change.
  4. Implement: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Verify: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

Answer & Explanations

Correct answer: B

A.

The action is applicable: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. But its proposed test—Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.—addresses “Preserve FortiManager configuration with a tested backup and restore method”. This requirement is confirmed instead by: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

B.

Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Confirm it through this test: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

C.

This action/test pair addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”. Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change. The case instead calls for: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

D.

The test would be relevant: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. But the offered implementation—Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.—addresses “Preserve FortiManager configuration with a tested backup and restore method”. The action needed here is: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

Question 76

A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.
  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 FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan.
  4. Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. Verify the result with this test: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

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: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

C.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. This addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”, where the governing principle is: An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. The stated case instead calls for: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

D.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. This addresses “Preserve FortiManager configuration with a tested backup and restore method”, where the governing principle is: Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. The stated case instead calls for: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

Question 77

A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. The engineer proposes the following change: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Which mechanism explains why it works?

  1. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.
  2. An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
  3. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.
  4. 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.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. That explains “Preserve FortiManager configuration with a tested backup and restore method”, not the mechanism behind the described change. The relevant principle is: A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

B.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. That explains “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the mechanism behind the described change. The relevant principle is: A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

C.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. The corresponding implementation is: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

D.

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: A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

Question 78

A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. After implementing this change—Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.—which test most directly validates its intended outcome?

  1. Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.
  2. 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.
  3. In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change.
  4. Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. That would help test “Preserve FortiManager configuration with a tested backup and restore method”, not the outcome required in this scenario. The relevant acceptance check is: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

B.

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: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

C.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change. That would help test “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the outcome required in this scenario. The relevant acceptance check is: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

D.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. This check is decisive because a successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

Question 79

A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Which proposed shortcut most directly risks unauthorized cross-tenant policy changes after conflating centralized authentication with least-privilege FortiManager authorization and should therefore be rejected?

  1. Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.
  2. Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path.
  3. Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.
  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: A

A.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords. The foreseeable failure is unauthorized cross-tenant policy changes after conflating centralized authentication with least-privilege FortiManager authorization. The safer response is: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

B.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path. That shortcut risks stale management state and failed updates after treating offline staging capabilities as evidence of live connectivity. Here the specific shortcut is: Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.

C.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations. That shortcut risks unrecoverable centralized policy and object history when a damaged management appliance lacks a valid tested backup. Here the specific shortcut is: Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.

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: Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.

Question 80

A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. Verify: In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change.
  2. Implement: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Verify: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.
  3. Implement: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Verify: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.
  4. Implement: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Verify: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. This action/test pair addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”. Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change. The case instead calls for: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

B.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Confirm it through this test: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

C.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. The test would be relevant: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. But the offered implementation—Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.—addresses “Preserve FortiManager configuration with a tested backup and restore method”. The action needed here is: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.

D.

The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. The action is applicable: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. But its proposed test—Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.—addresses “Preserve FortiManager configuration with a tested backup and restore method”. This requirement is confirmed instead by: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

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