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.
Your organization uses Cloud Next Generation Firewall (NGFW) Enterprise to inspect egress traffic from VMs in us-central1-a within a regular VPC network (prod-vpc) using the AFTER_CLASSIC_FIREWALL enforcement order. You attach a global network firewall policy (egress-l7-policy) with an egress apply_security_profile_group rule and logging enabled, while legacy egress allow VPC firewall rules remain active.
During an audit, you observe:
apply_security_profile_fallback_action="ALLOW" instead of disposition="INTERCEPTED".egress-l7-policy shadowed by a VPC firewall rule.What is causing these findings, and how should you resolve them to enforce Layer 7 egress inspection?
Associating a valid zonal firewall endpoint with prod-vpc establishes the Layer 7 inspection plane in us-central1-a, while switching the enforcement order to BEFORE_CLASSIC_FIREWALL ensures global network firewall policies take precedence over legacy VPC firewall rules.
apply_security_profile_fallback_action="ALLOW": When Cloud NGFW evaluates an apply_security_profile_group rule but finds no valid firewall endpoint—or no endpoint associated with the workload's VPC network—it falls back to allowing traffic and records apply_security_profile_fallback_action="ALLOW". Associating a healthy endpoint in us-central1-a restores packet interception, changing the logged disposition to INTERCEPTED and the fallback action to UNSPECIFIED.AFTER_CLASSIC_FIREWALL order, Cloud NGFW evaluates VPC firewall rules before global network firewall policies, allowing legacy egress allow VPC rules to match first and shadow rules in egress-l7-policy. Switching to BEFORE_CLASSIC_FIREWALL evaluates global and regional network firewall policies ahead of VPC firewall rules.Unlike modifying security profile overrides or waiting for idle timers, addressing both the missing firewall endpoint association and the policy enforcement order directly corrects the Layer 7 datapath failure and the Layer 3/4 rule precedence conflict.
Enabling Transport Layer Security (TLS) inspection decrypts selected encrypted traffic at the firewall endpoint for deep packet inspection, while consolidating secure tags simplifies identity-based rule targeting within firewall policies.
disposition="INTERCEPTED". The presence of apply_security_profile_fallback_action="ALLOW" specifically indicates that no valid firewall endpoint is associated with prod-vpc in us-central1-a.AFTER_CLASSIC_FIREWALL evaluation order where VPC firewall rules run before global network firewall policies.Traffic were already showing disposition="INTERCEPTED" in firewall logs, encrypted payloads were bypassing threat signature detection, and manual audits revealed redundant secure tags rather than an AFTER_CLASSIC_FIREWALL precedence conflict.
Adding threat-prevention overrides customizes the action (such as alert, deny, or reset) taken for specific threat signatures inside a security profile, while regional network firewall policies scope firewall rules to a single Google Cloud region.
apply_security_profile_fallback_action="ALLOW" appears in the firewall policy logs, traffic is never reaching a valid endpoint in prod-vpc, meaning profile overrides are never evaluated.AFTER_CLASSIC_FIREWALL, Cloud NGFW evaluates VPC firewall rules (step 3) before both global network firewall policies (step 4) and regional network firewall policies (step 5). Moving the rule to a regional policy leaves it shadowed by legacy VPC rules, and Cloud NGFW Enterprise Layer 7 inspection is configured via hierarchical or global network firewall policies rather than regional policies.apply_security_profile_group are supported in hierarchical and global network firewall policies, not regional network firewall policies.BEFORE_CLASSIC_FIREWALL places network firewall policies ahead of VPC firewall rules.Traffic was already logged as disposition="INTERCEPTED" by an associated firewall endpoint, specific malware or spyware signatures were using a permissive default action, and only Layer 3/4 regional segmentation was required.
Waiting 10 minutes addresses a Firewall Rules Logging delay for pre-existing TCP and UDP flows, while adding an explicit deny VPC firewall rule overrides the default implied egress allow behavior at the end of firewall evaluation.
apply_security_profile_fallback_action="ALLOW", proving a missing or unassociated firewall endpoint rather than a logging delay.goto_next. It cannot shadow a rule in egress-l7-policy; instead, an existing VPC firewall rule is shadowing it because AFTER_CLASSIC_FIREWALL evaluates VPC rules first.apply_security_profile_fallback_action="ALLOW" always signals that Cloud NGFW could not route packets to a valid firewall endpoint and defaulted to permitting traffic uninspected.allow VPC rules and does not change the AFTER_CLASSIC_FIREWALL precedence order.No firewall log entries appeared at all for long-lived connections immediately after enabling logging on a working rule, and uninspected egress traffic was reaching the final implied allow egress step without matching any higher-priority rule.
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