Get Aug-2026 Dumps to Pass your FCP_FMG_AD-7.6 Exam with 100% Real Questions and Answers
Updated Exam FCP_FMG_AD-7.6 Dumps with New Questions
Fortinet FCP_FMG_AD-7.6 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 3 |
|
| Topic 4 |
|
NEW QUESTION # 11
Refer to the exhibit. What are two results from the configuration shown in the exhibit? (Choose two.)
- A. The administrator must have access to the ADOM to approve changes.
- B. The same administrator can lock more than one ADOM at the same time.
- C. The administrator can lock policy blocks and FortiManager global ADOM.
- D. Ungraceful closed sessions will keep the ADOM in a locked state until the administrator session times out.
Answer: B,D
Explanation:
If an administrator locks an ADOM (checks it out) and then closes their session ungracefully (e.g., browser crash, network disconnect) without explicitly checking the configuration back in, the ADOM remains in a locked state. FortiManager relies on the configured session timeout to automatically release the lock. This prevents other administrators from editing the configuration until the lock expires.
The lock is applied on a per-ADOM basis. A single administrator can log into FortiManager and check out (lock) multiple different ADOMs simultaneously, provided those ADOMs are not currently locked by another administrator.
NEW QUESTION # 12
An administrator upgrades FortiManager with workspace mode per ADOM enabled to the latest version but notices that the ADOM versions did not change.
Why were the ADOMs not upgraded?
- A. The administrator did not run the database integrity check before performing the upgrade.
- B. FortiManager does not automatically upgrade ADOMs after a firmware upgrade.
- C. A user had all ADOMs locked before the upgrade, which stopped them from being upgraded.
- D. A FortiManager process task is stuck and blocking the ADOM upgrade, so the administrator must fix it.
Answer: B
Explanation:
The correct answer is B . The FortiManager 7.6 Administrator Study Guide gives the exact extract: "Also note when you upgrade the FortiManager firmware version the existing ADOMs are not automatically upgraded." This directly explains why the administrator saw the FortiManager upgrade complete while the ADOM versions remained unchanged.
The same section also explains that ADOM upgrades are a separate action: "You can upgrade an ADOM in System Settings > ADOMs" and "Can upgrade to one version higher at a time." In addition, the guide recommends: "upgrade all devices first, and then upgrade the ADOM." So the issue is not workspace mode, locked ADOMs, or a stuck task. The ADOMs simply require their own manual upgrade step after the FortiManager firmware upgrade.
NEW QUESTION # 13
Refer to the exhibit. How does FortiManager get antivirus and IPS updates?
- A. It connects to the public FortiGuard servers listed in the configuration.
- B. It gets updates from the server with IP address 10.0.1.50.
- C. It uses all URLs in the list that contain the fds host name.
- D. It connects to all servers marked as FortiGuard Distribution Network through Internet (FDNI) sources.
Answer: B
Explanation:
The output shows that Server Override Mode is set to Strict, and the server at index 0 (IP
10.0.1.50, port 8890) is marked with an asterisk *, indicating it is the active FortiGuard server.
Since it was configured via CLI and is at the top of the list, FortiManager will exclusively use this server for antivirus and IPS updates.
NEW QUESTION # 14
An administrator assigned the Training global policy package to the Branches policy package in ADOM1. Later, the administrator created a new policy package named Remotes on ADOM1.
What should the administrator do to sync the Training global policy package with the Remotes policy package in ADOM1?
- A. Manually add and assign the Remotes policy package to the Training global policy package
- B. Use the automatically install policies to ADOM devices method to sync from the Training global policy package to the Remotes policy package
- C. Assign the Training global policy package to the Remotes policy package
- D. Unassign the Training policy package and reassign it to all policy packages within ADOM1
Answer: C
Explanation:
In FortiManager, global policy packages are not automatically assigned to new policy packages created in an ADOM. To apply a global policy (like "Training") to a new policy package (like
"Remotes"), the administrator must manually assign the global policy to that policy package.
Therefore, the correct step is to assign the Training global policy package to the Remotes policy package.
NEW QUESTION # 15
Which is recommended when you are managing a high volume of logs in your network?
- A. Add and manage FortiAnalyzer from FortiManager.
- B. Store logs on FortiManager and use FortiView.
- C. Enable advanced ADOM mode on FortiManager.
- D. Forward logs from FortiAnalyzer to FortiManager daily.
Answer: A
Explanation:
Adding and managing FortiAnalyzer from FortiManager is recommended for handling a high volume of logs, as FortiAnalyzer is designed specifically for centralized log management, analysis, and reporting, which offloads this workload from FortiManager.
NEW QUESTION # 16
An administrator notices that CLI scripts are failing on some FortiGate devices because they use different FortiOS versions.
Which two actions should the administrator take to fix the failing CLI scripts? Choose two answers.
- A. Create separate ADOMs for each FortiOS version.
- B. Create version-specific CLI script groups and assign them to the appropriate devices.
- C. Disable CLI scripts for devices using older firmware.
- D. Modify the CLI scripts to include conditional commands based on FortiOS version.
Answer: A,B
Explanation:
The most strongly supported answer is A . The study guide explicitly states: "In the case of having multiple FortiOS firmware versions on the same ADOM, it is recommended to use separate ADOMs instead." It also says: "When you organize managed FortiGate devices, it is highly recommended that you group them based on their FortiOS firmware version. This is because valid command syntax varies by firmware version, which affects script compatibility." D is the other practical fix supported by FortiManager workflow. The study guide states that FortiManager can run scripts on multiple managed devices at once , and device groups let you run scripts on multiple devices instead of a single device . Combined with the firmware-version compatibility rule above, the correct operational approach is to keep version-specific scripts and apply them only to the matching device sets. B and C are not supported by the uploaded study guide as the recommended fix.
=========
NEW QUESTION # 17
Refer to the exhibit. What are two results from the configuration shown in the exhibit? (Choose two.)
- A. Multiple administrators can lock and work on separate AOMs at the same time.
- B. The same administrator can lock more than one ADOM at the same time.
- C. Concurrent read-write access to an ADOM is disabled.
- D. All changes must be approved before they can be installed on a device.
Answer: A,B
Explanation:
The CLI command set workspace-mode normal configures FortiManager to use normal workspace mode, which allows:
- A single administrator to lock multiple ADOMs simultaneously, since there's no restriction on per-user ADOM access in this mode.
- Multiple administrators to work concurrently on different ADOMs, each locking their own ADOM as needed.
NEW QUESTION # 18
Refer to the exhibit. What will happen if the script is run using the Device Database option?
(Choose two.)
- A. The Device Settings Status will be tagged as Modified.
- B. The script history will show successful installation of the script on the remote FortiGate.
- C. The successful execution of a script on the Device Database will create a new revision history.
- D. You must install these changes using the Install Wizard to a managed device.
Answer: A,D
Explanation:
Once scripts are run on the device database, you can then install the changes on a managed device using the installation wizard.
Since the script changed the device settings in FortiManager, the Config Status shows "Modified" and needs to be installed with Installation Wizard.
NEW QUESTION # 19
Which two conditions trigger FortiManager to create a new revision history? (Choose two.)
- A. When a provisioning template is assigned to a managed device on the device-level database
- B. When FortiManager is auto-updated with configuration changes made directly on a managed device
- C. When changes to the device-level database are made on FortiManager
- D. When FortiManager installs device-level changes on a managed device
Answer: B,D
Explanation:
Conditions for Revision History and Troubleshooting
FortiManager creates a revision history when:
1- FortiGate is added to FortiManager
2- Device changes are installed
3- FortiGate configuration is retrieved from FortiManager
4- A local change on FortiGate causes an automatic update
Scripts run directly on remote devices also cause automatic updates and create a revision history
5- You revert to a previous revision and install the changes
How to check managed FortiGate configuration issues:
1- View and download FortiGate configuration revision
Compare differences between revisions
2- View who made the changes
3- View what has been installed on the managed device
NEW QUESTION # 20
What are two outcomes of ADOM revisions? (Choose two.)
- A. ADOM revisions can save the current state of all policy packages and objects for an ADOM.
- B. ADOM revisions can save the current state of the entire ADOM.
- C. ADOM revisions do not increase the size of configuration backups.
- D. ADOM revisions appear in the Install Policy & Package Settings section of the install wizard.
Answer: A,C
Explanation:
Note that an ADOM revision is a snapshot of the entire ADOM and not the changes specific to this policy package.
Warning: Keep in mind that ADOM revisions can significantly increase the size of the configuration backup.
NEW QUESTION # 21
Refer to the exhibit. Which statement about the environment shown in the exhibit is correct?
- A. No FortiGuard packages have been synchronized between the cluster members yet.
- B. You must restart the secondary unit if you promote it to become the primary.
- C. FortiAnalyzer features are not enabled on this FortiManager device.
- D. A failover will take place after five minutes without receiving heartbeat packets.
Answer: C
Explanation:
lf FortiAnalyzer features are enabled, you cannot add FortiAnalyzer to FortiManager. You will also not be able to configure FortiManager high availability (HA).
NEW QUESTION # 22
What allows FortiManager to run CLI scripts on FortiGate devices without prompting for SSH authentication each time?
- A. The script using the Remote FortiGate Directly (via CLI) option.
- B. The script on the FortiManager device database.
- C. FortiGate devices using the legacy login method.
- D. The secure management tunnel between FortiManager and FortiGate devices.
Answer: D
Explanation:
FortiManager uses a secure management tunnel (TCP port 541) to communicate with managed FortiGate devices. This tunnel allows FortiManager to run CLI scripts, push configuration changes, and retrieve information without prompting for SSH authentication each time, as trust is already established through device authorization and certificate exchange.
NEW QUESTION # 23
Refer to the exhibit.
Which statement about the environment shown in the exhibit is true? Choose one answer
- A. FortiAnalyzer features are not enabled on this FortiManager device.
- B. A failover will take place after five minutes without receiving heartbeat packets.
- C. No FortiGuard packages have been synchronized between the cluster members.
- D. You must restart the secondary device if you promote it to primary.
Answer: A
Explanation:
The exhibit shows a FortiManager HA cluster with one primary and one secondary member. The FortiManager 7.6 Administrator Study Guide clearly states that if FortiAnalyzer features are enabled, you cannot configure FortiManager HA , so in an HA environment like the one shown, FortiAnalyzer features are not enabled . That makes D the correct answer.
A is incorrect because the study guide explicitly says you do not need to reboot a device when promoting it from secondary to primary.
C is incorrect because the failover mode shown is Manual , not VRRP automatic failover , so failover does not occur automatically based on heartbeat loss.
B is not the best answer here because FortiGuard packages are downloaded separately rather than synchronized as HA data, but the exhibit's key provable conclusion is the HA restriction on FortiAnalyzer features.
=========
NEW QUESTION # 24
A FortiManager administrator has moved a FortiGate device to a new ADOM, but they cannot see the policy or object configurations for that FortiGate.
What should the administrator do to see the policy or object configurations?
- A. Import the policy package manually using the Import Configuration wizard.
- B. Use ADOM sync to restore the missing configurations.
- C. Reset the device and add it to the new ADOM again.
- D. Use ADOM shared objects to restore all missing data.
Answer: A
Explanation:
When a FortiGate device is moved from its original ADOM (Source ADOM) to a new ADOM (Target ADOM), only the Device Database (the device's running configuration) moves with it.
The Policy Package and the Policy/Object configurations are not automatically transferred because they are considered part of the Source ADOM's specific policy logic.
NEW QUESTION # 25
Push updates are failing on a FortiGate device located behind a network address translation (NAT) device?
Which two settings should the administrator check to correct this problem? (Choose two.)
- A. Make sure the virtual IP address and the correct ports are configured on the NAT device.
- B. Make sure the NAT device IP address and the correct ports are configured on FortiManager.
- C. Make sure the Bind to IP address option on the FortiGuard service interface is set to the virtual IP address from the NAT device.
- D. Make sure FortiGuard updates and web service are enabled on the FortiGuard service interface.
Answer: A,B
Explanation:
What if FortiManager is behind a NAT device?
If FortiManager is behind a NAT device, sending its IP address for push updates causes push updates to fail because this is a non-routable IP address from the FDN. You must configure the following:
* On FortiManager, configure the NAT device IP address and port used for push updates.
* On the NAT device, configure the virtual IP and port that forwards to FortiManager.device.
NEW QUESTION # 26
You are moving managed FortiGate devices from one ADOM to a new ADOM.
Which statement correctly describes the expected result?
- A. Any unused objects from a previous ADOM are moved to the new ADOM automatically.
- B. The shared device settings will be installed automatically.
- C. The shared policy package will not be moved to the new ADOM automatically.
- D. Policy packages will be imported into the new ADOM automatically.
Answer: C
Explanation:
When you move devices from one ADOM to another ADOM, shared policy packages and objects do not move to the new ADOM. You will need to import policy packages from managed devices.
NEW QUESTION # 27
......
100% Pass Guarantee for FCP_FMG_AD-7.6 Exam Dumps with Actual Exam Questions: https://pass4sure.practicetorrent.com/FCP_FMG_AD-7.6-practice-exam-torrent.html