Current status (October 2026): Fortinet’s archived examination listing for FortiManager 7.4 Administrator gives October 15, 2025 as the last availability date for the exact 35-question, 70-minute FCP-era edition. FCP certifications were retired on July 15, 2026. Fortinet’s NSE transition guidance maps qualifying FortiManager Administrator results to NSE 6 Secure Networking under separate credential rules. A historical exam’s delivery end date is not the same event as the later certification-program transition.
FortiManager credentials after July 2026
The FCP_FMG_AD-7.4 designation refers to a legacy Fortinet Certified Professional-era exam, not to a newly awarded FCP credential. Fortinet retired the FCP family on July 15, 2026. An eligible FortiManager Administrator exam pass can map to NSE 6 in Secure Networking under the issuer’s transition policy, with separate rules for active former credentials and recent exam passes.
Fortinet’s NSE 6 FortiManager 7.6 Administrator description identifies a different, currently offered examination covering ADOM administration, device onboarding, policy packages and troubleshooting. The published 7.6 format is 70 minutes with 30–40 questions and addresses FortiManager 7.6.1 and FortiOS 7.6. This newer sitting does not extend the archived FCP_FMG_AD-7.4 delivery window beyond October 15, 2025. Match any proposed booking or practice material to the currently listed exam code, edition and language rather than assuming exam versions are interchangeable.
What FortiManager does
FortiManager centralizes management of FortiGate configurations, reusable policy objects and authorized deployment changes. A poorly targeted policy package can affect multiple devices, so installers should review the exact policy difference and device targets before committing. FortiAnalyzer has a different operational emphasis: collecting logs, supporting event investigation and producing reports rather than installing policy packages. Administrators should distinguish these complementary roles instead of treating management and analytics tools as interchangeable.
A useful starting exercise adds a test FortiGate to a managed inventory, checks connectivity and authorization, and compares the observed configuration against the expected device state. Keep production devices out of a learning exercise unless explicitly authorized.
Administrative domains and delegated access
ADOMs allow managed devices and policy objects to be organized into separate administrative contexts. Their use depends on an organization’s size, licensing and operating model. A secure design aligns ADOM visibility and administrator roles with actual responsibilities, rather than giving all users unrestricted control.
Record the account performing a change, the ADOM it can access and the target devices. Verify that a delegated user cannot accidentally install policy to another team’s devices. Role boundaries should be tested as carefully as the firewall rules themselves.
If several teams share FortiManager, test role boundaries with two named lab administrators. One should be permitted to review or edit the intended ADOM and another should be denied a cross-domain action. Also verify whether change approval or workspace locking is enabled in that deployment. This is a more useful demonstration of least privilege than merely listing available role names.
Policy objects, packages and device mapping
A policy package represents a set of firewall policies intended for one or more managed FortiGate devices. Shared objects must map appropriately to the target device. Fortinet’s documentation warns that referenced objects will be installed and some nonreferenced objects may also be installed or removed, depending on the package and import choices.
Do not install a shared policy simply because it passes a syntax check. Compare its source and destination interfaces, address objects, security profiles and intended devices. Examine per-device mappings and ensure the package does not unintentionally broaden access or remove objects another application needs.
Before reusing an object in several policy packages, confirm its semantic meaning and device mapping. A service name can look uniform while source and destination address groups differ by ADOM or environment. A policy installed to a firewall that lacks the expected object definition can fail or behave unexpectedly. Compare the package configuration with the actual target device mapping and keep the intended network flow documented beside the change ticket.
Change review and installation workflow
Fortinet’s FortiManager best practices recommend reviewing Install Preview before policy installation, particularly when applying a package for the first time. A prudent workflow captures the current state, prepares the intended difference, requests approval, reviews the preview and installs only to the specified authorized targets.
If the preview contains unexpected deletions, translations or interface changes, stop and reconcile the object mapping before continuing. Record the result, check traffic on the managed FortiGate and preserve a rollback plan. A successful wizard completion is not proof that every dependent service still functions.
Install Preview is a decision aid, not a substitute for testing. Inspect the commands that would be added, changed or removed and look for unrelated interface, routing or administrator changes. Confirm the selected device set, package and installation mode. A reviewer should be able to explain why each proposed change follows from the approved request, and the deployment window should include an explicit rollback route if a critical application loses connectivity.
After installation, validate both the FortiManager job result and the forwarding/security behavior on representative FortiGate devices. Check that the expected policy is present, confirm a permitted and denied traffic sample, and capture configuration-revision identifiers. A successful central-management task does not by itself prove that traffic on every branch firewall still follows the required rules.
Revision history and troubleshooting
Configuration revision tools can assist with comparing changes and investigating drift. Build a lab example that deliberately changes a test address object, compares revisions and then restores the approved value. Use logs and device state to verify the restoration rather than assuming the revision label proves the running configuration.
When a push fails, distinguish an authorization issue, an ADOM mismatch, a missing object mapping, an offline device and a configuration conflict. The appropriate response is targeted diagnosis, not repeated installation attempts to every managed device.
A useful troubleshooting case begins with a known-good revision and a deliberate test change to a noncritical object. Compare the resulting package revision and installed device configuration, then revert only the intended change. Record which revision was active on FortiManager and which was active on the managed firewall; these can diverge when installation is incomplete or another authorized administrator changes the device directly.
A concrete policy-deployment review
Consider a test organization with two FortiGates using different internal interfaces. A shared policy package includes an address object that requires a device-specific mapping. Before installation, confirm both mappings, preview the resulting changes for each device and check whether unrelated objects might be affected. If either preview contains an unexpected deletion, stop and repair the mapping rather than deploying to both devices.
After an approved install, validate the resulting FortiGate policies and observe allowed and denied test traffic. Record which revision was installed and how to return to the previous working state. This scenario teaches change control, object mapping and troubleshooting without claiming that the policy wizard has tested the application automatically.
Prepare against active NSE 6 objectives
Read the active NSE 6 Secure Networking and FortiManager exam descriptions before selecting materials. Map each task to a hands-on exercise covering device management, ADOMs, policy packages, install preview, revision control and operational troubleshooting. The relevant FortiManager release must match the issuer objectives and documentation used in the lab.
Third-party practice questions can be used to test understanding but should not be presented as official exam registration, guaranteed success or proof of live examination content. The professional value of FortiManager skill comes from auditable configuration control and safe operations, not a promise that passing a retired FCP-branded exam leads to leadership or a specific salary.