FCP_FMG_AD-7.4 is a legacy examination, not a current FCP award
FCP_FMG_AD-7.4 identifies an earlier Fortinet FortiManager Administrator examination. The code can help readers find historical product study material, but it does not identify a current certification path in October 2026. Fortinet retired its FCF, FCA, FCP, FCSS and FCX credential labels on July 15, 2026 and introduced an eight-level NSE program. The official NSE program announcement documents the transition.
Fortinet’s current exam-release list names NSE 6 – FortiManager 7.6 Administrator as released on July 15, 2026, replacing the preceding NSE 5 FortiManager 7.6 examination. The issuer’s exam mapping associates qualifying earlier FortiManager Administrator passes with NSE 6 in Secure Networking. Eligibility depends on the individual’s credential and pass history; the mapping is not permission to assert that an old FCP_FMG_AD-7.4 question bank remains valid, or that every former candidate receives a new badge.
FortiManager 7.4 concepts such as ADOMs, policy packages, revision control and device management can still be instructive. Commands, menus, firmware support and exam objectives can change between releases. Use this article as a practical operations guide with clearly labeled historical context, not as a promise of exam success, current voucher availability or protected exam-question access.
Understand the difference between managed and running configuration
FortiManager centralizes administration of supported FortiGate and other Fortinet devices. It stores device configuration representations, reusable objects and policy packages, while the devices retain their own running configurations. A rule visible in the manager is not necessarily installed on every firewall. The correct question is what has been changed, approved, installed and verified on the intended target.
In an authorized lab, register two test devices and record their management connections, firmware versions and the relevant ADOM. Make a benign object change, preview the installation difference, then verify which device actually received it. Check both a permitted and a prohibited application flow after installation. This tests outcomes, rather than trusting a success banner as the sole evidence of correctness.
The difference between FortiManager policy packages and device settings matters because a centralized firewall policy does not automatically repair unrelated routing, VPN, NAT or service-level faults.
Design administrative domains around accountability
Administrative domains (ADOMs) group devices and management resources into controlled scopes. They can separate operating teams, tenants or product-version groups. An ADOM is a management structure, not a data-plane network security boundary. Its design must reflect who can see, edit and install configurations, which shared objects are needed and how different firmware versions are managed.
For a fictional organization with two independent divisions, identify the devices and support engineers each division owns. Test a deliberately limited operator account and verify it cannot modify the other division’s protected configuration. Establish which emergency changes require cross-team approval. Avoid treating a convenient ADOM name as proof that access controls were tested.
See the published explanation of ADOMs and multi-tenancy when deciding whether organizational separation actually needs different managed policy scopes.
Maintain reusable policy objects without expanding risk
Policy packages and shared objects promote consistent configurations, but consistency magnifies an error when the object is used broadly. A mistaken address group can affect several rules and devices. Before editing a shared object, identify where it is referenced, who owns the change and which traffic can be impacted. A narrow test package is safer than modifying a global object without a dependency review.
Document application requirements and firewall behavior separately. Confirm source and destination networks, relevant services, address translation, expected route and logging. A successful connectivity test should be paired with a negative test showing unwanted access remains blocked. Fixing an application by temporarily allowing all traffic does not constitute an acceptable permanent resolution.
Control edits with workspace locks and workflow
Concurrent changes can cause version conflicts and confusing installations. Fortinet’s FortiManager workspace guidance describes modes that require locking ADOMs, policy packages or devices before editing. The precise locking and approval workflow depends on the configured mode and software version. Locks protect concurrent editing, but do not replace peer review or authorization.
Practice obtaining a lock for a harmless change in a test ADOM. Inspect the pending difference and release the lock through the supported process. Do not routinely disconnect a colleague to steal a lock. When workflow approval is enabled, track the difference between authoring, submitting, approving and installing a change.
The site’s article on FortiManager workspace mode and locking expands this specific operational scenario.
Prepare installation, verification and rollback together
An installation plan should specify target devices, policy differences, permitted maintenance windows, dependencies, approvers and a known-good revision. Preview changes before installation and retain the relevant history for recovery. Afterward, verify both the control plane and the actual application traffic. A device showing an online status can still carry an incorrect security policy.
Use a staged rollout when one object or policy may affect several branches. Choose a representative test device first, validate expected and denied flows, and establish a stopping rule for errors. Avoid blind retries when an installation response is ambiguous. Confirm the device’s current version and manager database state before deciding whether to repeat, repair or roll back the change.
Troubleshoot device enrollment and drift with evidence
If a firewall becomes disconnected from FortiManager, determine whether the issue is management reachability, device registration, an authorization or trust failure, unsupported software, or a local change. The firewall may continue forwarding traffic while management connectivity is down; this does not mean the central manager is synchronized or ready to push policy. Preserve status, timestamps and log evidence before making changes.
A locally edited device may differ from the manager’s expected configuration. Reconcile the difference by identifying the owner and purpose of each change rather than forcing an overwrite. An emergency device fix may be legitimate. Document how the intended manager state should be updated and verify that restored alignment does not remove required security protections.
Distinguish management availability from firewall failover
FortiManager resilience concerns access to the management platform and preservation of its operational data. It is not identical to FortiGate cluster failover or branch traffic continuity. Define the management recovery target, dependency on storage and network connectivity, and evidence required to resume controlled installations after an outage.
In a disposable test environment, rehearse a planned loss of manager access, restore service and inspect whether policy versions and permissions remain correct. Record what was verified and what could not be tested without a production-like cluster. Do not equate a restarted process with complete operational recovery.
Study NSE 6 with version-specific practical work
Review the current Fortinet NSE 6 FortiManager exam description before selecting training. Map device management, ADOM design, policy lifecycle, object reuse, workspace controls, diagnostics and rollback to reproducible tasks. Label older 7.4 material as historical whenever it describes retired certification rules or older interface behavior.
A useful portfolio contains an ADOM responsibility diagram, an approved installation difference, evidence of expected and denied traffic, a change record and tested rollback steps. These demonstrate technical understanding without claiming that a discontinued exam code guarantees a qualification, promotion or passing score.