Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 49
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?
Answer & Explanations
Correct answer: 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. 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.
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.
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.
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.
Question 481
A financial institution must demonstrate that FortiManager policy authors cannot approve their own high-risk production changes. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
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: 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.
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. This addresses “Choose ADOM or policy package lock scope appropriate to the change”, where the governing 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. The stated case instead calls for: 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.
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. 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. Verify the result with this 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.
Use FortiManager policy checks and relevant object validations to inspect shadowed, inconsistent or invalid rules and referenced interfaces, then resolve significant issues before installing to production targets. This addresses “Run FortiManager policy check before approving a package installation”, where the governing principle is: A syntactically saved rule may never match because a broader earlier rule captures traffic; checking effective policy logic prevents false assumptions that a newly written rule changes enforcement. The stated case instead calls for: 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.
Question 482
A financial institution must demonstrate that FortiManager policy authors cannot approve their own high-risk production changes. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: 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. That explains “Choose ADOM or policy package lock scope appropriate to the change”, not the mechanism behind the described change. The relevant 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.
A syntactically saved rule may never match because a broader earlier rule captures traffic; checking effective policy logic prevents false assumptions that a newly written rule changes enforcement. That explains “Run FortiManager policy check before approving a package installation”, not the mechanism behind the described change. The relevant 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.
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: 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.
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 corresponding implementation is: 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.
Question 483
A financial institution must demonstrate that FortiManager policy authors cannot approve their own high-risk production changes. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
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. This check is decisive because 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.
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. That would help test “Choose ADOM or policy package lock scope appropriate to the change”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Add a narrowly scoped deny beneath a broad allow in a lab package, use the available policy analysis and simulated traffic to reveal the shadowed behavior, then revise approved rule order. That would help test “Run FortiManager policy check before approving a package installation”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
Question 484
A financial institution must demonstrate that FortiManager policy authors cannot approve their own high-risk production changes. Which proposed shortcut most directly risks unauthorized production rule installation after FortiManager workflow separation of duties is bypassed and should therefore be rejected?
Answer & Explanations
Correct answer: B
Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications. That shortcut risks accidental edit conflicts or avoidable maintenance delays after choosing no lock or overly broad lock scope. Here the specific shortcut is: Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy.
Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy. The foreseeable failure is unauthorized production rule installation after FortiManager workflow separation of duties is bypassed. The safer response is: 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.
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: Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy.
Save a new deny rule at the end of a policy list and assume it always overrides an earlier matching allow because its description says High Priority. That shortcut risks unintended permitted access after an ineffective shadowed security rule is installed without verification. Here the specific shortcut is: Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy.
Question 485
A financial institution must demonstrate that FortiManager policy authors cannot approve their own high-risk production changes. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
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. Confirm it through this 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. 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 action is applicable: 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. But its proposed 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.—addresses “Enable FortiManager workspace mode for concurrent policy editing”. This requirement is confirmed instead by: 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.
The test would be relevant: 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. But the offered implementation—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.—addresses “Enable FortiManager workspace mode for concurrent policy editing”. The action needed here is: 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 action/test pair addresses “Choose ADOM or policy package lock scope appropriate to the 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. 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. The case instead calls for: 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.
Question 486
A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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. This addresses “Choose ADOM or policy package lock scope appropriate to the change”, where the governing 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. The stated case instead calls for: 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.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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. 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. Verify the result with this 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.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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: 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.
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. This addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, where the governing principle is: An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. The stated case instead calls for: 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.
Question 487
A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. That explains “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the mechanism behind the described change. The relevant 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 question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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. That explains “Choose ADOM or policy package lock scope appropriate to the change”, not the mechanism behind the described change. The relevant 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 question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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 corresponding implementation is: 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.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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: 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.
Question 488
A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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. That would help test “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: 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.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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. That would help test “Choose ADOM or policy package lock scope appropriate to the change”, not the outcome required in this scenario. The relevant acceptance check is: 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.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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: 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.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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. This check is decisive because 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.
Question 489
A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. Which proposed shortcut most directly risks unauthorized production rule installation after FortiManager workflow separation of duties is bypassed and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy. The foreseeable failure is unauthorized production rule installation after FortiManager workflow separation of duties is bypassed. The safer response is: 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.
Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed. That shortcut risks incorrect change records after management database restoration is confused with actual firewall enforcement rollback. Here the specific shortcut is: Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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: Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications. That shortcut risks accidental edit conflicts or avoidable maintenance delays after choosing no lock or overly broad lock scope. Here the specific shortcut is: Give rule authors direct unrestricted installation privileges while claiming their self-signed change ticket provides the independent approval required by policy.
Question 490
A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. The test would be relevant: 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. But the offered implementation—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.—addresses “Enable FortiManager workspace mode for concurrent policy editing”. The action needed here is: 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.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. 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. Confirm it through this 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. 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 question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. The action is applicable: 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. But its proposed 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.—addresses “Enable FortiManager workspace mode for concurrent policy editing”. This requirement is confirmed instead by: 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.
The question is set in this situation: A hospital firewall team is configuring workflow permissions so an on-call editor can prepare an emergency rule while a separate reviewer approves installation. This action/test pair addresses “Choose ADOM or policy package lock scope appropriate to the 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. 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. The case instead calls for: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 47 - 10 Questions (Last Reviewed 05-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 48 - 10 Questions (Last Reviewed 04-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 49 - 10 Questions (Last Reviewed 03-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 50 - 10 Questions (Last Reviewed 02-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 51 - 10 Questions (Last Reviewed 01-Oct-2026)