Basic Concept: OCSP and CRL both check certificate revocation, but OCSP performs on-demand status checks instead of downloading full revocation lists.
Why B is Correct: OCSP is more scalable for large deployments because it returns real-time status for a certificate with lower memory and download overhead.
Why A is Wrong: OCSP allows the firewall to act as its own certificate authority (CA), and it simplifies certificate management. is associated with authentication, PKI, or TLS configuration, but it is not the object or step that enforces the certificate validation or service identity requirement being tested.
Why C is Wrong: OCSP is an older, more widely supported protocol than CRLs. ensuring compatibility with all client devices. is associated with authentication, PKI, or TLS configuration, but it is not the object or step that enforces the certificate validation or service identity requirement being tested.
Why D is Wrong: OCSP bundles all certificate statuses into a single, digitally signed file for faster downloads by the firewall. is associated with authentication, PKI, or TLS configuration, but it is not the object or step that enforces the certificate validation or service identity requirement being tested.

Basic Concept: Cloud NGFW deployment must fit the cloud routing architecture. Distributed AWS VPCs and Azure vWAN hubs call for different insertion models while still using Panorama policy.
Why C and D are Correct: Cloud NGFW endpoints in each AWS application VPC and Cloud NGFW as an Azure vWAN security partner minimize routing changes and keep policy centrally managed.
Why A is Wrong: Native cloud provider firewalls in both cloud environments and connected to Panorama for management is a cloud deployment or routing approach, but it does not match the required managed insertion model, resilience pattern, or Panorama-controlled policy design in this scenario.
Why B is Wrong: Cloud NGFW in each spoke VNet with User-Defined Routes (UDRs) to redirect traffic bypassing the vWAN hub is a cloud deployment or routing approach, but it does not match the required managed insertion model, resilience pattern, or Panorama-controlled policy design in this scenario.

Traditional firewalls rely on IP and port information.
NGFWs use Deep Packet Inspection (DPI) and behavioral analysis to identify applications regardless of port usage, enabling application-based policies.

Enabling LACP in the HA passive state allows the passive firewall to negotiate and maintain the LACP session with the switch even while it is not active, so the aggregate Ethernet interface is already up and fully formed when a failover occurs, minimizing downtime.

NetFlow export requires the interface to operate in Layer 3 mode because it depends on IP routing and flow records derived from Layer 3 traffic, which are not available on interfaces configured as Layer 2, virtual wire, or other non-Layer 3 modes.