FCP FortiManager 7.4 study materials
FCP FortiManager 7.4 study resources

FCP FortiManager 7.4 study plan

FCP FortiManager 7.4 · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

System Setup and Administration

  • Diagram the FortiManager deployment topologies (standalone, HA, and fabric) and label the management protocols and ports used between FortiManager, FortiGate, and FortiAnalyzer.

  • Install FortiManager in a lab VM, complete the initial setup wizard, and record each configuration choice with the reason it was selected.

  • Configure administrative accounts, RADIUS or LDAP authentication, and role-based profiles; then verify access with test logins for each role.

  • Enable and interpret the FortiManager event log and task monitor to confirm that system-level changes are recorded and traceable.

Your checkpoint

A one-page deployment diagram plus a configuration log documenting every setup choice, with screenshots of successful admin logins for at least two roles.

Week 2

System Setup and Administration

  • Configure workspace mode and ADOMs, then demonstrate how to lock, unlock, and commit changes without conflicting with a second admin session.

  • Set up backup and restore procedures, including scheduled backups to an external server, and perform a full restore in the lab.

  • Apply firmware upgrade best practices by reviewing release notes, checking the upgrade path, and executing an upgrade on the lab FortiManager.

  • Troubleshoot a simulated admin login failure by inspecting authentication logs and connectivity to the external authentication server.

Your checkpoint

A written runbook section covering workspace mode, ADOM creation, backup/restore, and firmware upgrade steps, validated by a successful lab restore and upgrade.

Week 3

Device Manager

  • Add a FortiGate to FortiManager using the correct discovery method, authorize the device, and verify the serial number and HA status appear correctly.

  • Create and assign a provisioning template to the managed FortiGate, then push the configuration and confirm the change on the device.

  • Build a device-level backup schedule and compare a pre-change and post-change configuration revision in the revision history.

  • Configure a device group and demonstrate how group-level settings propagate to member devices.

Your checkpoint

A device onboarding checklist and a revision-history comparison showing at least two configuration revisions for one managed FortiGate.

Week 4

Device Manager

  • Use the install wizard to push interface and routing changes to a managed FortiGate, then verify the results in the FortiGate CLI.

  • Diagnose and resolve a failed install by reading the install preview, task monitor, and device logs.

  • Configure metadata variables on a managed device and reference them in a provisioning template.

  • Perform a device-level script execution and confirm the output in the task monitor.

Your checkpoint

A troubleshooting report for one failed install, including root cause, resolution steps, and evidence from the task monitor.

Week 5

Policy and Objects

  • Create firewall address and service objects in the ADOM object database and reference them in a policy package.

  • Build a policy package with at least three policies, including NAT and security profiles, and install it to a managed FortiGate.

  • Configure policy block and object revision tracking, then compare two policy package revisions.

  • Use the policy check and install preview to identify conflicts or missing objects before installation.

Your checkpoint

A policy package export showing at least three policies with referenced objects, plus a revision comparison report.

Week 6

Policy and Objects

  • Create a dynamic object and use it in a policy, then verify how the object resolves on the managed device.

  • Configure global and local policy packages in a multi-ADOM scenario and explain the precedence rules.

  • Set up policy and object consistency checks, then resolve any inconsistencies reported by FortiManager.

  • Demonstrate object usage lookup to identify which policies reference a given address object before deleting it.

Your checkpoint

A written explanation of global versus local policy behavior with lab evidence, plus a resolved inconsistency report.

Week 7

Advanced Configuration and Troubleshooting

  • Configure and test the FortiManager fabric integration with FortiAnalyzer and FortiGate, including log forwarding and security fabric settings.

  • Set up a JSON API or scripting workflow to create an address object and verify the result through the GUI and API.

  • Configure HA between two FortiManager instances in the lab and test failover by stopping the primary node.

  • Review and tune administrative settings such as session timeout, password policy, and trusted hosts.

Your checkpoint

An HA failover test record with timestamps and a working API script that creates and verifies an object.

Week 8

System Setup and Administration & Device Manager & Policy and Objects & Advanced Configuration and Troubleshooting

  • Complete a timed practice assessment covering all four domains and score at least 80 percent.

  • Review every missed question by mapping it to the relevant domain and writing a short corrective note.

  • Re-run the lab scenarios for device onboarding, policy install, and HA failover without referring to notes.

  • Build a one-page quick-reference sheet of commands, ports, and troubleshooting steps for final review.

Your checkpoint

A scored practice assessment report with corrective notes and a completed one-page quick-reference sheet.

Milestones

Week 2: Successfully restore a FortiManager backup and complete a firmware upgrade in the lab without data loss.

Week 4: Onboard a FortiGate, push a provisioning template, and resolve one failed install using task monitor evidence.

Week 6: Install a policy package with at least three policies and resolve all reported object or policy inconsistencies.

Week 8: Score at least 80 percent on a timed four-domain practice assessment and complete all lab re-runs without notes.