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 48

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.

Question 471

A bank's operations team wants two different security engineers to edit unrelated FortiManager policies in the same ADOM during a controlled window. 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. Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.
  4. Use FortiManager's policy installation preview and validation to inspect intended commands, target devices and object/interface resolution, then obtain approval before deploying a package.

Answer & Explanations

Correct answer: C

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. This addresses “Enable FortiManager workspace mode for concurrent policy editing”, where the governing principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. The stated case instead calls for: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

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: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

C.

Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode. Verify the result with this test: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

D.

Use FortiManager's policy installation preview and validation to inspect intended commands, target devices and object/interface resolution, then obtain approval before deploying a package. This addresses “Preview a FortiManager Install Wizard plan before changing a FortiGate”, where the governing principle is: The central package editor expresses desired state; the Install Wizard translates it into target-specific configuration and may reveal missing mappings or unexpected changes that are not visible from the package name. The stated case instead calls for: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

Question 472

A bank's operations team wants two different security engineers to edit unrelated FortiManager policies in the same ADOM during a controlled window. The engineer proposes the following change: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. Which mechanism explains why it works?

  1. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.
  2. The central package editor expresses desired state; the Install Wizard translates it into target-specific configuration and may reveal missing mappings or unexpected changes that are not visible from the package name.
  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. A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

Answer & Explanations

Correct answer: D

A.

Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. That explains “Enable FortiManager workspace mode for concurrent policy editing”, not the mechanism behind the described change. The relevant principle is: A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

B.

The central package editor expresses desired state; the Install Wizard translates it into target-specific configuration and may reveal missing mappings or unexpected changes that are not visible from the package name. That explains “Preview a FortiManager Install Wizard plan before changing a FortiGate”, not the mechanism behind the described change. The relevant principle is: A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

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: A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

D.

A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode. The corresponding implementation is: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

Question 473

A bank's operations team wants two different security engineers to edit unrelated FortiManager policies in the same ADOM during a controlled window. After implementing this change—Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.—which test most directly validates its intended outcome?

  1. 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. Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.
  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. Preview a staging package with a dynamic object for two FortiGate targets, compare each generated change, install to one test device and confirm its actual policy counters.

Answer & Explanations

Correct answer: B

A.

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. That would help test “Enable FortiManager workspace mode for concurrent policy editing”, not the outcome required in this scenario. The relevant acceptance check is: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

B.

Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported. This check is decisive because a broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

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: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

D.

Preview a staging package with a dynamic object for two FortiGate targets, compare each generated change, install to one test device and confirm its actual policy counters. That would help test “Preview a FortiManager Install Wizard plan before changing a FortiGate”, not the outcome required in this scenario. The relevant acceptance check is: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

Question 474

A bank's operations team wants two different security engineers to edit unrelated FortiManager policies in the same ADOM during a controlled window. Which proposed shortcut most directly risks accidental edit conflicts or avoidable maintenance delays after choosing no lock or overly broad lock scope and should therefore be rejected?

  1. Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.
  2. Delete every workspace session after one user disconnects and assume all authorized unpublished rule modifications will be preserved automatically.
  3. Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications.
  4. 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.

Answer & Explanations

Correct answer: C

A.

Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes. That shortcut risks network exposure or traffic disruption after deploying unchecked generated policy differences. Here the specific shortcut is: Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications.

B.

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: Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications.

C.

Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications. The foreseeable failure is accidental edit conflicts or avoidable maintenance delays after choosing no lock or overly broad lock scope. The safer response is: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

D.

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. That shortcut risks lost or overwritten firewall policy edits when concurrent administrators lack controlled workspace locking. Here the specific shortcut is: Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications.

Question 475

A bank's operations team wants two different security engineers to edit unrelated FortiManager policies in the same ADOM during a controlled window. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. Verify: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.
  2. Implement: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. 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: 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: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.
  4. 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.

Answer & Explanations

Correct answer: A

A.

Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. Confirm it through this test: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported. A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

B.

The action is applicable: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. But its proposed test—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.—addresses “Release abandoned workspace locks without silently discarding valid changes”. This requirement is confirmed instead by: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

C.

The test would be relevant: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported. But the offered implementation—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.—addresses “Release abandoned workspace locks without silently discarding valid changes”. The action needed here is: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

D.

This action/test pair addresses “Enable FortiManager workspace mode for concurrent policy editing”. 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. 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. The case instead calls for: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

Question 476

An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
  3. 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.
  4. Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. 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: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

B.

Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. This addresses “Choose a FortiManager policy package for a shared branch access standard”, where the governing principle is: Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy. The stated case instead calls for: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

C.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. 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. This addresses “Enable FortiManager workspace mode for concurrent policy editing”, where the governing principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. The stated case instead calls for: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

D.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode. Verify the result with this test: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

Question 477

An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. The engineer proposes the following change: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. Which mechanism explains why it works?

  1. 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.
  2. A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.
  3. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.
  4. Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. 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: A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

B.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode. The corresponding implementation is: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

C.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. That explains “Enable FortiManager workspace mode for concurrent policy editing”, not the mechanism behind the described change. The relevant principle is: A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

D.

Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy. That explains “Choose a FortiManager policy package for a shared branch access standard”, not the mechanism behind the described change. The relevant principle is: A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

Question 478

An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. After implementing this change—Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.—which test most directly validates its intended outcome?

  1. Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.
  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. Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported. This check is decisive because a broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

B.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. 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. That would help test “Enable FortiManager workspace mode for concurrent policy editing”, not the outcome required in this scenario. The relevant acceptance check is: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

C.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. 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: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

D.

Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged. That would help test “Choose a FortiManager policy package for a shared branch access standard”, not the outcome required in this scenario. The relevant acceptance check is: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

Question 479

An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. Which proposed shortcut most directly risks accidental edit conflicts or avoidable maintenance delays after choosing no lock or overly broad lock scope 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. Delete every workspace session after one user disconnects and assume all authorized unpublished rule modifications will be preserved automatically.
  3. Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications.
  4. Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. 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. That shortcut risks lost or overwritten firewall policy edits when concurrent administrators lack controlled workspace locking. Here the specific shortcut is: Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications.

B.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. 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: Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications.

C.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications. The foreseeable failure is accidental edit conflicts or avoidable maintenance delays after choosing no lock or overly broad lock scope. The safer response is: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

D.

Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard. That shortcut risks unexpected branch exposure or missing controls after confusing central policy authoring with installation target coverage. Here the specific shortcut is: Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications.

Question 480

An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. 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.
  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: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.
  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: 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. Implement: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. Verify: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. The action is applicable: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. But its proposed test—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.—addresses “Release abandoned workspace locks without silently discarding valid changes”. This requirement is confirmed instead by: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.

B.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. The test would be relevant: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported. But the offered implementation—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.—addresses “Release abandoned workspace locks without silently discarding valid changes”. The action needed here is: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

C.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. This action/test pair addresses “Enable FortiManager workspace mode for concurrent policy editing”. 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. 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. The case instead calls for: Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.

D.

The question is set in this situation: An MSP is deciding whether to lock a full customer ADOM or one package for a small emergency change without blocking independent planned work. Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. Confirm it through this test: Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported. A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.

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