# Free NSE6_FMG_AD-7.6 practice questions

> 10 free NSE6_FMG_AD-7.6 practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/fortinet-fcp-fmg-ad-7-6/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/fortinet-fcp-fmg-ad-7-6/

### Question 1 of 10

Two administrators often edit the same ADOM at the same time and overwrite each other's changes. The company wants an administrator to lock the ADOM, make changes, save and then unlock, without any approval step. Which setting meets this requirement?

- A. Workspace mode set to disable
- B. Workspace mode set to normal (workspace)
- C. ADOM device mode set to advanced for the ADOM
- D. Workspace mode set to workflow

**Answer:** B

**Explanation:** Workspace (normal) mode requires administrators to lock an ADOM, package or device before editing and to save before unlocking, which prevents concurrent overwrites without approvals. Workflow mode adds sessions that must be submitted and approved, which the company does not want. Disabling workspace mode allows simultaneous editing, which is the current problem. Advanced device mode concerns VDOM-to-ADOM assignment, not locking.

### Question 2 of 10

An MSSP manages FortiGate devices for three customers on one FortiManager. Each customer's administrators must see only their own devices, policy packages and objects. What should the MSSP enable and configure?

- A. Create one policy package folder per customer and give each administrator the Package_User profile for that folder
- B. Enable workflow mode and create an approval group per customer so that each change is reviewed by that customer
- C. Enable ADOMs and create one ADOM per customer, then assign each customer's administrators to their own ADOM
- D. Keep ADOMs disabled and create one device group per customer, then restrict the administrators to that device group

**Answer:** C

**Explanation:** Administrative domains (ADOMs) partition devices, policy packages and objects so administrators assigned to an ADOM only see that ADOM's data. Device groups are an organisational aid and do not isolate the ADOM-wide object database. Workflow mode controls approval of changes, not visibility. Package folders and the Package_User profile still expose the shared ADOM object database to every customer.

### Question 3 of 10

Twenty FortiGate devices will be shipped directly to new stores. The administrator wants their configuration staged on FortiManager in advance so it is pushed automatically when each unit first connects. Which approach should be used?

- A. Add each unit as a model device by serial number, with templates and a policy package assigned in advance
- B. Wait until each unit connects, then use the Discover option and import its factory-default policy package
- C. Create one ADOM per store and pre-load a configuration backup into each ADOM's revision history
- D. Add each unit with the Discover option using a placeholder IP address that is changed after it is installed

**Answer:** A

**Explanation:** Model devices are pre-provisioned by serial number with templates and a policy package; when the real FortiGate connects, FortiManager links it to the model and installs the staged configuration. Waiting and importing a factory default skips the pre-staging requirement. Discovery requires a reachable device and real credentials, so a placeholder IP does not work. Revision history cannot hold a configuration for a device that has never been registered, and per-store ADOMs add needless overhead.

### Question 4 of 10

A branch FortiGate behind an ISP NAT router has no inbound port forwarding. The administrator wants it managed by the head-office FortiManager, which has a public IP address. Which registration method works?

- A. Use the Add Device wizard with the Discover option, the FortiGate's private IP address and its administrator credentials
- B. Run a CLI script on FortiManager that targets the branch FortiGate directly to create the FGFM tunnel
- C. Use the Add Device wizard with the Discover option and the ISP router's public IP address and admin credentials
- D. Configure central management on the FortiGate to point at the FortiManager, then authorize the unregistered device on FortiManager

**Answer:** D

**Explanation:** Because nothing forwards inbound traffic to the branch FortiGate, the FortiGate must initiate the FGFM connection outbound; it then appears as an unauthorized device that the administrator authorizes. Discovering the private address fails because it is not routable from head office, and discovering the router's public address fails without a port forward. Scripts that run on a remote FortiGate need an existing FGFM tunnel, so they cannot create the first one.

### Question 5 of 10

A security team maintains a set of eight standard outbound policies that must appear in several different policy packages and be maintained once. Which FortiManager feature is designed for this?

- A. A dynamic address group containing each package's addresses
- B. A policy block inserted into every policy package that needs them
- C. A per-policy install target applied to the eight policies in one package
- D. A metadata variable holding the eight policy IDs for each package

**Answer:** B

**Explanation:** Policy blocks group reusable policies that can be inserted into multiple packages and maintained in one place. An address group only groups addresses, not policies. Metadata variables hold per-device values, not policy sets. Per-policy install targets limit where policies install within one package rather than sharing them across packages.

### Question 6 of 10

An install of a shared policy package fails on one FortiGate with an error that an interface used in a policy has no mapping for that device. What is the most likely cause?

- A. The FortiGate's FGFM tunnel is down, so FortiManager cannot read its interface list
- B. A normalized interface used in the package has no per-device mapping for that FortiGate
- C. The policy package was installed to too many devices at once and timed out
- D. The ADOM version is newer than the FortiOS version running on that FortiGate

**Answer:** B

**Explanation:** Policies in a shared package reference normalized interfaces, and each target device needs a mapping from the normalized interface to one of its real interfaces; a missing mapping stops the install for that device. A down tunnel produces connectivity errors, not missing-mapping errors. Concurrent installs do not cause mapping errors, and version mismatches block management with a different message.

### Question 7 of 10

After the import of 15 FortiGates into one ADOM, the object list contains many objects that no policy references. The administrator wants to clean up the ADOM database safely. Which tool should be used first?

- A. The policy consistency check on each policy package
- B. The Find Duplicate Objects tool in Policy & Objects
- C. The Find Unused Objects tool in Policy & Objects
- D. An ADOM revision rollback to the pre-import snapshot

**Answer:** C

**Explanation:** Find Unused Objects lists objects with no references so they can be reviewed and removed safely. Find Duplicate Objects identifies objects with identical values, a different clean-up task. The policy check looks for shadowed, overlapping and duplicate policies rather than unreferenced objects. Rolling back the ADOM revision would discard the imported policies along with the unused objects.

### Question 8 of 10

A company wants identical header policies, such as a block of known-bad countries, at the top of the policy packages in all its ADOMs, managed from one place. What should be used?

- A. An ADOM revision copied from one ADOM to every other ADOM
- B. A CLI script run against the policy package and ADOM database of every ADOM on a schedule
- C. A system template assigned to every FortiGate in each ADOM
- D. A Global Database policy package with header policies assigned to the ADOM packages

**Answer:** D

**Explanation:** The Global Database ADOM provides global policy packages whose header and footer policies are assigned to ADOM packages, and global objects follow the assignment. A script per ADOM would work once but is not centrally managed afterwards. System templates provision device settings such as DNS and NTP, not firewall policies. ADOM revisions restore one ADOM and cannot be copied between ADOMs.

### Question 9 of 10

A FortiGate was changed locally through its own GUI by an on-site technician. FortiManager had pending changes for the same device at that time. What is the most likely configuration status shown in Device Manager?

- A. Out of sync, because both the FortiGate and the device database changed independently
- B. Auto-updated, because the local change always overwrites the pending FortiManager changes
- C. Never installed, because the device database is reset when a local change is detected
- D. Synchronized, because FortiManager automatically merges both sets of changes

**Answer:** A

**Explanation:** When both the FortiGate and the FortiManager device database have changes, FortiManager cannot simply auto-update and reports an out-of-sync state that the administrator must resolve. FortiManager never merges both change sets automatically. An automatic update happens only when FortiManager has no pending changes. The device database is not reset by a local change, so the never-installed status does not apply.

### Question 10 of 10

An install to a FortiGate fails, and the administrator wants to see exactly which CLI command the FortiGate rejected. Where is this information found?

- A. In the policy consistency check report generated for the installed policy package
- B. In the install log for that device, opened from the task monitor or the install wizard
- C. In the FortiManager event log filtered for administrator login and logout events
- D. In the FortiGate's revision history diff between the last two revisions on FortiManager

**Answer:** B

**Explanation:** The install log records the commands sent and the FortiGate's response, including the specific command that failed. A revision diff shows configuration differences, not which command was rejected during a failed install. Login and logout events do not record install errors. The policy check analyses rule logic before installation and does not capture device responses.

Ready for a timed run? Take the free 15-question NSE6_FMG_AD-7.6 mini exam: https://devopscodelab.com/app/exams/fortinet-fcp-fmg-ad-7-6/mini/

DevOpsCode Lab is not affiliated with Fortinet. NSE6_FMG_AD-7.6 and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
