Home / cybersecurity / Palo Alto Networks Certified Next-Generation Firewall Engineer (NGFW Engineer) / Cheat Sheet
Palo Alto Networks Certified Next-Generation Firewall Engineer (NGFW Engineer)

NGFW Engineer Cheat Sheet

NGFW Engineer Tests Picking the Exact PAN-OS Object — Not Any Feature That Works

This role-based exam, which followed the retired PCNSE, targets engineers who deploy and automate PAN-OS firewalls. Several options are always real features, so match the precise requirement to the precise object.

Check Your Readiness →
Among the harder certs
Avg: Not published by Palo Alto Networks
Pass: 750 / 1000
Most candidates understand Palo Alto Networks Certified Next-Generation Firewall Engineer (NGFW Engineer) concepts — and still fail. This exam tests how you apply knowledge under pressure.

NGFW Engineer Datasheet Domains (November 2025)

Three official domains (40/40/20) are split here by objective group. Items include multiple choice, matching and ordering plus unscored pretest questions. Distractors are real PAN-OS objects built for a neighbouring purpose. Item count and duration are not officially published.

  1. 01
    PAN-OS Networking: interfaces, zones, HA (part of 40%) — virtual wire vs. L2/L3/tap, zone defaults, HA links, path monitoring, preemption
  2. 02
    PAN-OS Networking: routing and tunnels (part of 40%) — distances, Advanced Routing Engine, GlobalProtect portal vs. gateway, IPSec proxy IDs, GRE
  3. 03
    Device Settings: access, VSYS, logging, updates (part of 40%) — auth sequences, admin roles, external zones, log forwarding, upgrade order
  4. 04
    Device Settings: certificates, identity, proxy (part of 40%) — forward trust/untrust, certificate profiles, User-ID and Cloud Identity Engine, web proxy
  5. 05
    Integration and Automation (20%) — VM-Series bootstrap, CN-Series, Cloud NGFW, APIs, Terraform vs. Ansible, Panorama, ACC and reports

Wrong instinct vs correct approach

A company with only Microsoft Entra ID must match users by Entra groups on several firewalls
✕ Wrong instinct

Configure LDAP group mapping against a domain controller

✓ Correct approach

There are no domain controllers to query, so use the Cloud Identity Engine, which syncs Entra ID directory data and shares user and group context with the firewalls. Also enable User-ID on the source zones.

Fifty branch firewalls need identical DNS and NTP but unique hostnames and management IPs
✕ Wrong instinct

Configure each firewall locally or build fifty templates

✓ Correct approach

Put shared DNS and NTP in one template inside a template stack, and supply per-device hostname and management IP through template variables or device-specific overrides. Commit on Panorama, then push to devices.

A third-party policy-based VPN peer brings up phase 1, but phase 2 never establishes
✕ Wrong instinct

Change the DH group in the IKE crypto profile

✓ Correct approach

Policy-based peers negotiate phase 2 per local and remote subnet pair, so configure proxy IDs matching the peer's crypto access lists. Phase 1 already works, so IKE gateway crypto is not the issue.

Security must enforce a block rule on all branches that local admins cannot override
✕ Wrong instinct

Add the block rule as a Panorama post-rule

✓ Correct approach

Post-rules evaluate after local rules, so a local allow could match first. Enforced controls go in pre-rules, which are evaluated before local rules and cannot be edited on the firewall.

Know these cold

  • ▸ Tap only sees copies and cannot block; virtual wire inserts inline with no IP or MAC
  • ▸ HA1 config and state, HA2 session sync, HA3 packet forwarding in active/active only
  • ▸ Default distances — tatic 10, eBGP 20, OSPF internal 30, iBGP 200
  • ▸ Intrazone traffic allowed by default; interzone denied unless a rule allows it
  • ▸ Data interfaces need an interface management profile to answer ping, SSH or HTTPS
  • ▸ Authentication sequence gives fallback; one authentication profile never falls back
  • ▸ Service profile presents a certificate; certificate profile validates one presented to the firewall
  • ▸ Upgrade content before PAN-OS, Panorama before firewalls, HA peers one at a time
  • ▸ Inter-VSYS traffic uses external zones and needs Security policy in both virtual systems
  • ▸ Split tunneling is a GlobalProtect gateway setting; the portal distributes app config and gateways

Can you answer these without checking your notes?

In this scenario: "A company with only Microsoft Entra ID must match users by Entra groups on several firewalls" — what should you do first?
There are no domain controllers to query, so use the Cloud Identity Engine, which syncs Entra ID directory data and shares user and group context with the firewalls. Also enable User-ID on the source zones.
In this scenario: "Fifty branch firewalls need identical DNS and NTP but unique hostnames and management IPs" — what should you do first?
Put shared DNS and NTP in one template inside a template stack, and supply per-device hostname and management IP through template variables or device-specific overrides. Commit on Panorama, then push to devices.
In this scenario: "A third-party policy-based VPN peer brings up phase 1, but phase 2 never establishes" — what should you do first?
Policy-based peers negotiate phase 2 per local and remote subnet pair, so configure proxy IDs matching the peer's crypto access lists. Phase 1 already works, so IKE gateway crypto is not the issue.

Common Exam Mistakes — What candidates get wrong

Putting a Security rule in a Panorama template

Templates and template stacks hold network and device settings only; policies and objects live in device groups, which inherit downward from Shared. In a template stack the higher template wins conflicts, and every Panorama change needs commit then push.

Using link monitoring when the upstream ISP router is what failed

Link monitoring watches only the firewall's own interfaces, which stay up behind a switch. Path monitoring pings destination IPs beyond the link. Preemption, for failback to the higher-priority peer, must be enabled on both peers.

Swapping forward trust and forward untrust decryption certificates

Forward trust signs certificates for sites with valid certificates and should be an enterprise subordinate CA endpoints trust. Forward untrust signs for sites with invalid certificates and must stay untrusted so users still see warnings.

Expecting a log forwarding profile to send system and config logs

A log forwarding profile attaches to Security rules and forwards traffic and threat logs. System, configuration and other device logs are forwarded from Device log settings. Collector group log redundancy halves usable storage.

Raising the Diffie-Hellman group to make IPSec quantum-resistant

Classical DH and ECDH remain vulnerable to harvest-now, decrypt-later attacks. The PAN-OS answer is a post-quantum pre-shared key or hybrid ML-KEM key exchange, both requiring IKEv2 rather than IKEv1.

Resources to help you pass Palo Alto Networks NGFW Engineer on your first attempt

NGFW Engineer hinges on choosing the one PAN-OS object that fits. Check your accuracy.