Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A cloud network engineer is analyzing Cloud NGFW firewall policy logs in Cloud Logging after enabling logging on an existing regional network firewall policy:
apply_security_profile_group): A TCP port 443 connection established before logging was enabled continues sending packets every 2 minutes, but generates no log entries. New sessions show one log entry with disposition: INTERCEPTED and apply_security_profile_fallback_action: UNSPECIFIED, even across multiple underlying connections.deny): Dropped UDP traffic logs every 5 seconds, but dropped ICMP traffic generates no logs.How should the engineer interpret these log observations?
apply_security_profile_fallback_action: UNSPECIFIED indicates interception failed and traffic bypassed inspection, while the missing ICMP logs indicate Rule 2 is shadowed by a higher-priority rule.INTERCEPTED Disposition and Shadowed Rules MeanIn Cloud NGFW, apply_security_profile_fallback_action is a metadata field included in firewall policy log entries whenever a rule uses the apply_security_profile_group action, while a shadowed rule is a rule whose attributes are completely overlapped by one or more higher- or equal-priority rules.
apply_security_profile_fallback_action: UNSPECIFIED: When Cloud NGFW successfully intercepts a session and redirects it to a firewall endpoint for deep packet inspection, it sets disposition to INTERCEPTED and apply_security_profile_fallback_action to UNSPECIFIED. This combination confirms healthy interception rather than a bypass or failure.TCP and UDP connections and never logs ICMP.disposition: INTERCEPTED paired with action: APPLY_SECURITY_PROFILE_GROUP explicitly confirms traffic redirection to the security profile group.deny rule for ICMP (protocol=1) will produce zero firewall policy log entries.Rule 2 produced zero logs for both UDP and ICMP because a higher-priority rule at priority 5 already matched the exact same IP ranges and protocols, and Rule 1 reported an unexpected allow or deny fallback disposition instead of INTERCEPTED due to an unreachable firewall endpoint.
allow and deny rules.Google Cloud VPC and Cloud NGFW firewalls are stateful, meaning once an outbound or inbound connection is permitted, reply traffic is automatically allowed via connection tracking without re-evaluating firewall rules or generating additional log entries. Firewall policy rules logging can be enabled on allow, deny, and apply_security_profile_group rules.
apply_security_profile_group: Firewall policy rules logging is fully supported on rules configured with apply_security_profile_group. In fact, Cloud NGFW policies are the only logs capable of recording the INTERCEPTED disposition and the APPLY_SECURITY_PROFILE_GROUP action, using session-based logic rather than standard connection-based logging.allow, deny, and apply_security_profile_group rules, though implied default rules (implied deny ingress and implied allow egress) do not support logging.apply_security_profile_group generates a single high-level session interception log, detailed Layer 7 logs (such as threat or URL filtering logs) are generated separately per inspected connection.The engineer had enabled logging before the TCP port 443 handshake occurred, observed the initial outbound ALLOW log entry, and wondered why inbound return packets from the server did not trigger a second log entry on an ingress rule.
Configuration propagation delay refers to the brief synchronization window after creating or updating a firewall rule during which log records may lack complete rule metadata. Connection logging rate limits cap the number of connections logged per unit of time based on a VM's machine type (in regular VPC networks) to protect compute performance.
INTERCEPTED log entry across multiple underlying connections on an apply_security_profile_group rule is intentional session-based logging behavior, not rate-limit dropping.apply_security_profile_group intentionally emit one high-level log entry for the initial session rather than one per connection, and Cloud NGFW notes it does not capture logs of all sessions.TCP and UDP are supported.Logs appeared for new TCP and UDP connections immediately after a rule edit but were missing rule_details fields, and a VM experiencing thousands of distinct new 5-tuple connections per second showed dropped telemetry while staying well within TCP/UDP protocols.
apply_security_profile_group uses session-based logging with INTERCEPTED disposition, and firewall policy rules logging only records TCP and UDP.Cloud NGFW firewall policy rules logging records connection records for Layer 4 traffic and session-level interception events for Layer 7 deep packet inspection rules. Understanding how connection state timers, advanced inspection actions, and protocol filters interact is essential for accurately validating security policy enforcement.
INTERCEPTED entry with UNSPECIFIED fallback: When a rule uses the apply_security_profile_group action, logging shifts from connection-based to session-based logic. Cloud NGFW writes a single high-level log entry confirming the initial session was intercepted (disposition: INTERCEPTED) and redirected to the firewall endpoint, automatically populating apply_security_profile_fallback_action as UNSPECIFIED. Granular Layer 7 threat or URL filtering logs are emitted separately per inspected connection.deny rules with logging enabled, each dropped packet matching a unique 5-tuple logs as a failed attempt and repeats every 5 seconds while traffic persists. However, firewall policy rules logging only supports TCP and UDP protocols, so dropped ICMP packets never generate firewall rule log entries.TCP and UDP streams must remain idle for at least 10 minutes (or receive a TCP RST) before subsequent packets trigger logging.apply_security_profile_group logs the initial session interception rather than every underlying connection within that session.TCP and UDP connections are captured by firewall policy rules logging; other protocols require VPC Flow Logs or Out-of-band integration.TCP or UDP packets for the same 5-tuple are throttled to one log entry every 5 seconds.Recognizing these native Cloud NGFW telemetry mechanics prevents false-positive misconfiguration alarms. The engineer can confirm that Rule 1 is actively intercepting traffic and Rule 2 is enforcing denies as designed, while using VPC Flow Logs if visibility into ICMP drops or continuous long-lived streams is required.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated