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 47

Question 460

An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer package. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Verify: Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.
  2. Implement: After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. Verify: Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.
  3. Implement: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Verify: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
  4. Implement: After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. Verify: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

Answer & Explanations

Correct answer: B

A.

The test would be relevant: Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. But the offered implementation—Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.—addresses “Capture a FortiManager ADOM revision before a shared policy reorganization”. The action needed here is: After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision.

B.

The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer package. After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. Confirm it through this test: Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected.

C.

This action/test pair addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”. Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. The case instead calls for: After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision.

D.

The action is applicable: After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. But its proposed test—Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.—addresses “Capture a FortiManager ADOM revision before a shared policy reorganization”. This requirement is confirmed instead by: Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.

Question 461

A national retailer has multiple regional teams editing one FortiManager ADOM and wants to stop simultaneous rule changes from overwriting each other. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.
  2. Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure.
  3. Configure the intended interface mapping for each target firewall so policy packages referencing normalized logical interfaces resolve to the real supported FortiGate ports at installation.
  4. Configure the supported workflow or session approval process in the chosen FortiManager workspace mode so a submitted production policy change receives designated reviewer approval before being installed.

Answer & Explanations

Correct answer: A

A.

Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. Verify the result with this test: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

B.

Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure. This addresses “Release abandoned workspace locks without silently discarding valid changes”, where the governing principle is: A stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict. The stated case instead calls for: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

C.

Configure the intended interface mapping for each target firewall so policy packages referencing normalized logical interfaces resolve to the real supported FortiGate ports at installation. This addresses “Map normalized FortiManager policy interfaces to differing FortiGate port names”, where the governing principle is: Physical interface names and zone membership differ across appliance models; central policy rules cannot be deployed safely when a logical interface mapping is absent or points to the wrong data path. The stated case instead calls for: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

D.

Configure the supported workflow or session approval process in the chosen FortiManager workspace mode so a submitted production policy change receives designated reviewer approval before being installed. This addresses “Use FortiManager workflow mode review and approval controls where required”, where the governing principle is: Workflow review separates authorship from authorization; a policy editor's ability to draft a rule does not by itself prove the change is approved for installation. The stated case instead calls for: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

Question 462

A national retailer has multiple regional teams editing one FortiManager ADOM and wants to stop simultaneous rule changes from overwriting each other. The engineer proposes the following change: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Which mechanism explains why it works?

  1. Workflow review separates authorship from authorization; a policy editor's ability to draft a rule does not by itself prove the change is approved for installation.
  2. Physical interface names and zone membership differ across appliance models; central policy rules cannot be deployed safely when a logical interface mapping is absent or points to the wrong data path.
  3. A stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict.
  4. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

Answer & Explanations

Correct answer: D

A.

Workflow review separates authorship from authorization; a policy editor's ability to draft a rule does not by itself prove the change is approved for installation. That explains “Use FortiManager workflow mode review and approval controls where required”, not the mechanism behind the described change. The relevant principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

B.

Physical interface names and zone membership differ across appliance models; central policy rules cannot be deployed safely when a logical interface mapping is absent or points to the wrong data path. That explains “Map normalized FortiManager policy interfaces to differing FortiGate port names”, not the mechanism behind the described change. The relevant principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

C.

A stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict. That explains “Release abandoned workspace locks without silently discarding valid changes”, not the mechanism behind the described change. The relevant principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

D.

Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. The corresponding implementation is: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

Question 463

A national retailer has multiple regional teams editing one FortiManager ADOM and wants to stop simultaneous rule changes from overwriting each other. After implementing this change—Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.—which test most directly validates its intended outcome?

  1. Preview one branch package targeting a FortiGate with wan1 and another with a differently named uplink, verify mapped interface values and run controlled permitted/denied traffic tests after install.
  2. Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.
  3. Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct.
  4. Create a test session containing a harmless object edit, submit it for authorized review, verify a rejected session cannot proceed and an approved one preserves its audit trail.

Answer & Explanations

Correct answer: B

A.

Preview one branch package targeting a FortiGate with wan1 and another with a differently named uplink, verify mapped interface values and run controlled permitted/denied traffic tests after install. That would help test “Map normalized FortiManager policy interfaces to differing FortiGate port names”, not the outcome required in this scenario. The relevant acceptance check is: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

B.

Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release. This check is decisive because workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

C.

Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct. That would help test “Release abandoned workspace locks without silently discarding valid changes”, not the outcome required in this scenario. The relevant acceptance check is: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

D.

Create a test session containing a harmless object edit, submit it for authorized review, verify a rejected session cannot proceed and an approved one preserves its audit trail. That would help test “Use FortiManager workflow mode review and approval controls where required”, not the outcome required in this scenario. The relevant acceptance check is: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

Question 464

A national retailer has multiple regional teams editing one FortiManager ADOM and wants to stop simultaneous rule changes from overwriting each other. Which proposed shortcut most directly risks lost or overwritten firewall policy edits when concurrent administrators lack controlled workspace locking and should therefore be rejected?

  1. Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.
  2. Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy.
  3. Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different.
  4. Delete every workspace session after one user disconnects and assume all authorized unpublished rule modifications will be preserved automatically.

Answer & Explanations

Correct answer: C

A.

Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly. That shortcut risks broken connectivity or bypassed filtering after shared policy interfaces resolve incorrectly on target FortiGates. Here the specific shortcut is: Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different.

B.

Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy. That shortcut risks unauthorized production rule installation after FortiManager workflow separation of duties is bypassed. Here the specific shortcut is: Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different.

C.

Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different. The foreseeable failure is lost or overwritten firewall policy edits when concurrent administrators lack controlled workspace locking. The safer response is: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

D.

Delete every workspace session after one user disconnects and assume all authorized unpublished rule modifications will be preserved automatically. That shortcut risks lost approved drafts or conflicting policy edits after uncontrolled workspace lock recovery. Here the specific shortcut is: Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different.

Question 465

A national retailer has multiple regional teams editing one FortiManager ADOM and wants to stop simultaneous rule changes from overwriting each other. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Verify: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.
  2. Implement: Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure. Verify: Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct.
  3. Implement: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Verify: Create a test session containing a harmless object edit, submit it for authorized review, verify a rejected session cannot proceed and an approved one preserves its audit trail.
  4. Implement: Configure the supported workflow or session approval process in the chosen FortiManager workspace mode so a submitted production policy change receives designated reviewer approval before being installed. Verify: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

Answer & Explanations

Correct answer: A

A.

Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Confirm it through this test: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

B.

This action/test pair addresses “Release abandoned workspace locks without silently discarding valid changes”. Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure. Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct. The case instead calls for: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

C.

The action is applicable: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. But its proposed test—Create a test session containing a harmless object edit, submit it for authorized review, verify a rejected session cannot proceed and an approved one preserves its audit trail.—addresses “Use FortiManager workflow mode review and approval controls where required”. This requirement is confirmed instead by: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

D.

The test would be relevant: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release. But the offered implementation—Configure the supported workflow or session approval process in the chosen FortiManager workspace mode so a submitted production policy change receives designated reviewer approval before being installed.—addresses “Use FortiManager workflow mode review and approval controls where required”. The action needed here is: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

Question 466

A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Set the intended supported installation target or per-policy scope for a FortiManager rule, review how it applies to individual managed FortiGates, and preview each target's resulting policy before committing installation.
  2. Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.
  3. Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure.
  4. Configure the supported workflow or session approval process in the chosen FortiManager workspace mode so a submitted production policy change receives designated reviewer approval before being installed.

Answer & Explanations

Correct answer: B

A.

Set the intended supported installation target or per-policy scope for a FortiManager rule, review how it applies to individual managed FortiGates, and preview each target's resulting policy before committing installation. This addresses “Verify per-policy installation targets rather than relying on package-wide assumptions”, where the governing principle is: One centrally shared package may contain rules relevant only to particular branches; leaving rule targets overly broad can create unintended permissions even when the package assignment itself is correct. The stated case instead calls for: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

B.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. Verify the result with this test: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

C.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure. This addresses “Release abandoned workspace locks without silently discarding valid changes”, where the governing principle is: A stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict. The stated case instead calls for: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

D.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Configure the supported workflow or session approval process in the chosen FortiManager workspace mode so a submitted production policy change receives designated reviewer approval before being installed. This addresses “Use FortiManager workflow mode review and approval controls where required”, where the governing principle is: Workflow review separates authorship from authorization; a policy editor's ability to draft a rule does not by itself prove the change is approved for installation. The stated case instead calls for: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

Question 467

A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. The engineer proposes the following change: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Which mechanism explains why it works?

  1. One centrally shared package may contain rules relevant only to particular branches; leaving rule targets overly broad can create unintended permissions even when the package assignment itself is correct.
  2. A stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict.
  3. Workflow review separates authorship from authorization; a policy editor's ability to draft a rule does not by itself prove the change is approved for installation.
  4. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

Answer & Explanations

Correct answer: D

A.

One centrally shared package may contain rules relevant only to particular branches; leaving rule targets overly broad can create unintended permissions even when the package assignment itself is correct. That explains “Verify per-policy installation targets rather than relying on package-wide assumptions”, not the mechanism behind the described change. The relevant principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

B.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. A stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict. That explains “Release abandoned workspace locks without silently discarding valid changes”, not the mechanism behind the described change. The relevant principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

C.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Workflow review separates authorship from authorization; a policy editor's ability to draft a rule does not by itself prove the change is approved for installation. That explains “Use FortiManager workflow mode review and approval controls where required”, not the mechanism behind the described change. The relevant principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

D.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. The corresponding implementation is: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

Question 468

A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. After implementing this change—Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.—which test most directly validates its intended outcome?

  1. In a lab assign a single branch-specific rule only to one of two package targets, compare the generated firewall configurations and confirm the other gateway does not receive the exception.
  2. Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct.
  3. Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.
  4. Create a test session containing a harmless object edit, submit it for authorized review, verify a rejected session cannot proceed and an approved one preserves its audit trail.

Answer & Explanations

Correct answer: C

A.

In a lab assign a single branch-specific rule only to one of two package targets, compare the generated firewall configurations and confirm the other gateway does not receive the exception. That would help test “Verify per-policy installation targets rather than relying on package-wide assumptions”, not the outcome required in this scenario. The relevant acceptance check is: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

B.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct. That would help test “Release abandoned workspace locks without silently discarding valid changes”, not the outcome required in this scenario. The relevant acceptance check is: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

C.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release. This check is decisive because workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

D.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Create a test session containing a harmless object edit, submit it for authorized review, verify a rejected session cannot proceed and an approved one preserves its audit trail. That would help test “Use FortiManager workflow mode review and approval controls where required”, not the outcome required in this scenario. The relevant acceptance check is: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

Question 469

A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Which proposed shortcut most directly risks lost or overwritten firewall policy edits when concurrent administrators lack controlled workspace locking and should therefore be rejected?

  1. Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different.
  2. Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy.
  3. Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.
  4. Delete every workspace session after one user disconnects and assume all authorized unpublished rule modifications will be preserved automatically.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different. The foreseeable failure is lost or overwritten firewall policy edits when concurrent administrators lack controlled workspace locking. The safer response is: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

B.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy. That shortcut risks unauthorized production rule installation after FortiManager workflow separation of duties is bypassed. Here the specific shortcut is: Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different.

C.

Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch. That shortcut risks overly broad access when a site-specific rule is deployed to every firewall in a shared package. Here the specific shortcut is: Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different.

D.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Delete every workspace session after one user disconnects and assume all authorized unpublished rule modifications will be preserved automatically. That shortcut risks lost approved drafts or conflicting policy edits after uncontrolled workspace lock recovery. Here the specific shortcut is: Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different.

Question 470

A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Configure the supported workflow or session approval process in the chosen FortiManager workspace mode so a submitted production policy change receives designated reviewer approval before being installed. Verify: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.
  2. Implement: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Verify: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.
  3. Implement: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Verify: Create a test session containing a harmless object edit, submit it for authorized review, verify a rejected session cannot proceed and an approved one preserves its audit trail.
  4. Implement: Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure. Verify: Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. The test would be relevant: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release. But the offered implementation—Configure the supported workflow or session approval process in the chosen FortiManager workspace mode so a submitted production policy change receives designated reviewer approval before being installed.—addresses “Use FortiManager workflow mode review and approval controls where required”. The action needed here is: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

B.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. Confirm it through this test: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

C.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. The action is applicable: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. But its proposed test—Create a test session containing a harmless object edit, submit it for authorized review, verify a rejected session cannot proceed and an approved one preserves its audit trail.—addresses “Use FortiManager workflow mode review and approval controls where required”. This requirement is confirmed instead by: Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.

D.

The question is set in this situation: A large hospital network is introducing workspace mode and needs an exercise proving an administrator cannot silently bypass another operator's lock. This action/test pair addresses “Release abandoned workspace locks without silently discarding valid changes”. Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure. Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct. The case instead calls for: Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.

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