To begin sending logs to Strata Logging Service while continuing to forward them to Panorama log collectors, the necessary configuration is to enable Cloud Logging. This option is configured in the Cloud Logging section under Device # Setup # Management in the appropriate templates. Once enabled, this ensures that logs are directed both to the Strata Logging Service (cloud) and to the Panorama log collectors.

Basic Concept: Some interface features are tied to Layer 3 operation because they require an IP address and routed interface behavior. Layer 2 interfaces switch traffic and do not host those IP-based services.
Why A is Correct: DDNS is correct because Dynamic DNS binds to an IP-addressed Layer 3 interface, while link attributes, LLDP, or NetFlow-type monitoring are not the same Layer 3-only DDNS function.
Why B is Wrong: Link Duplex is related to management or logging, but it does not provide the required Panorama operation, rule hierarchy behavior, or dual-log forwarding outcome.
Why C is Wrong: NetFlow is related to management or logging, but it does not provide the required Panorama operation, rule hierarchy behavior, or dual-log forwarding outcome.
Why D is Wrong: LLDP is related to management or logging, but it does not provide the required Panorama operation, rule hierarchy behavior, or dual-log forwarding outcome.

In the Palo Alto Networks PAN-OS architecture, aZone Protection Profileprovides the first line of defense against infrastructure-level attacks. It is applied to an entire zone to protect the firewall's resources and the internal network from malicious or malformed traffic before that traffic is even processed by the Security Policy engine.
The specific protections described-detecting malformed IP headers (incorrect header lengths) and invalid TCP flag combinations (such as SYN and FIN set simultaneously, which is logically impossible in standard TCP communications)-fall under thePacket-Based Attack Protectionsection of the profile. This section is further divided into several tabs, includingIP Drop,TCP Drop, andICMP Drop.
* IP Drop:This is where the firewall is configured to discard packets with malformed headers, invalid lengths, or security risks like IP spoofing and fragments.
* TCP Drop:This section handles the "SYN-FIN" check. Setting both flags is a classic technique used by attackers to bypass legacy stateful firewalls or to fingerprint operating systems. By enabling these protections, the NGFW drops these non-compliant packets at the ingress stage.
UnlikeFlood Protection(which mitigates DoS/DDoS attacks by limiting packet rates) orReconnaissance Protection(which detects port scans and host sweeps),Packet-Based Attack Protectionfocuses on the structural integrity and protocol compliance of individual packets entering the interface.

Before a firewall administrator can define policy rules based on users and groups, the Group Mapping settings must be configured. These settings enable the firewall to map users to their respective Active Directory (AD) groups. This mapping allows the firewall to use user and group information to create policy rules based on group membership.

Local firewall rules are evaluated after Panorama pre-rules (those applied before the firewall's local policies) and before Panorama post-rules (those applied after the firewall's local policies).
This ensures that the local firewall rules do not override the central Panorama policy and are only applied in the appropriate order within the policy evaluation sequence.