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 operates a Shared VPC configured with the AFTER_CLASSIC_FIREWALL enforcement order. You want centralized policies to take precedence over legacy VPC rules while retaining a broader 10.0.0.0/8 block for other subnets, so you add a Global Network Firewall Policy rule (priority: 500, allow, ingress tcp:8443, source 10.20.0.0/16, logging enabled).
Connections from 10.20.0.5 to tcp:8443 on service-project VMs fail, and your diagnostics show:
firewall_hit_count metrics for the new rule.priority: 1000, deny, source 10.0.0.0/8, logging disabled).What explains the missing logs and metrics, and how should you restore reachability?
firewall_hit_count metrics require up to a week for Firewall Insights machine learning model training; query Logs Explorer in the service project and wait for model training to finish.In a Shared VPC architecture, virtual machines run in service projects while the Shared VPC network, subnets, and firewall rules belong to the host project. Google Cloud stores all Firewall Rules Logging entries in the project that owns the VPC network—the host project—not the service projects. Separately, Firewall Insights uses machine learning models that take up to a week to train predictions for overly permissive rules.
firewall_hit_count metric is exported to Cloud Monitoring every minute whenever a rule with logging enabled experiences TCP or UDP hits—it does not wait a week for machine learning training.deny rule is actively dropping 10.20.0.5 packets; waiting will not restore reachability.roles/logging.viewer.firewall_hit_count time series for rules with zero hits.An engineer was looking for future hit probability predictions on an overly permissive allow rule shortly after enabling Firewall Insights, rather than diagnosing an active packet drop caused by a shadowed rule.
500 vs. 1000); update the Global Network Firewall Policy rule priority to 100 and enable logging on the VPC deny rule.In Cloud NGFW, numerical rule priority (where 0 is the highest priority) governs the evaluation order only among rules within the same firewall policy or within the VPC firewall rules tier. Priorities are never compared across different evaluation steps, such as between a classic VPC firewall rule and a Global Network Firewall Policy.
500 to 100 does not move it ahead of the VPC deny rule at priority 1000. Under AFTER_CLASSIC_FIREWALL, every matching VPC firewall rule—even at priority 65534—still evaluates before the Global Network Firewall Policy.deny rule reveals the dropped packets in Logs Explorer, but it still drops legitimate 10.20.0.5 traffic and leaves the policy rule unhit.100 in a Global Network Firewall Policy only beats priority 500 inside that same policy.AFTER_CLASSIC_FIREWALL order, Cloud NGFW evaluates hierarchical policies, regional system policies, VPC firewall rules, global network policies, and finally regional network policies.deny rule matches, evaluation stops immediately without checking subsequent policy tiers.Both the allow rule and the deny rule existed inside the same Global Network Firewall Policy (or both were classic VPC firewall rules), where lowering the allow rule's numerical priority below 1000 would make it evaluate first.
deny rule because VPC deny rules always take precedence over network firewall policies; convert the VPC deny rule's action to goto_next and enable logging on it.goto_next DoClassic VPC firewall rules support only two actions on match: allow and deny, both of which immediately terminate firewall evaluation for the packet. The goto_next action—which delegates evaluation to the next step in the policy evaluation order—is available exclusively in firewall policies (hierarchical, global network, and regional network firewall policies), not in classic VPC firewall rules.
goto_next; that parameter does not exist for VPC firewall rules.deny rules do not permanently outrank Global Network Firewall Policies. Precedence is controlled by the network's enforcement order setting (AFTER_CLASSIC_FIREWALL versus BEFORE_CLASSIC_FIREWALL).10.0.0.0/8 rule, changing a deny rule to delegate evaluation without preserving its block for other subnets would risk exposing non-10.20.0.0/16 traffic if no subsequent deny rule exists.allow) or block (deny) traffic and stop further rule inspection.goto_next and apply_security_profile_group.BEFORE_CLASSIC_FIREWALL lets Global Network Firewall Policies evaluate ahead of VPC firewall rules.The blocking 10.0.0.0/8 rule were located in a higher-precedence Hierarchical Firewall Policy (at the organization or folder level) rather than a VPC firewall rule, where changing its action to goto_next would delegate evaluation down to lower policies.
AFTER_CLASSIC_FIREWALL order, so the VPC deny rule without logging stops evaluation; switch the Shared VPC enforcement order to BEFORE_CLASSIC_FIREWALL.BEFORE_CLASSIC_FIREWALL Enforcement Order IsNetwork firewall policy enforcement order determines whether Global Network Firewall Policies and Regional Network Firewall Policies are evaluated before or after classic VPC firewall rules in Cloud Next Generation Firewall (Cloud NGFW). By default, VPC networks use AFTER_CLASSIC_FIREWALL, which evaluates VPC firewall rules before network firewall policies. Switching to BEFORE_CLASSIC_FIREWALL reverses that sequence so Global and Regional Network Firewall Policies take precedence over classic VPC firewall rules.
AFTER_CLASSIC_FIREWALL, the VPC deny rule (10.0.0.0/8) matches 10.20.0.5 first, drops the packet, and halts evaluation. Since logging is disabled on that VPC rule, no log entries are written, and Cloud Monitoring only records firewall_hit_count for rules that experience hits.BEFORE_CLASSIC_FIREWALL restores reachability: The Global Network Firewall Policy (allow for 10.20.0.0/16 on tcp:8443) is evaluated before VPC firewall rules, permitting 10.20.0.5 traffic and generating logs and firewall_hit_count metrics in the host project.10.0.0.0/8 still falls through via an implied goto_next and is blocked by the legacy VPC deny rule.firewall_hit_count time series in Cloud Monitoring.Changing the enforcement order to BEFORE_CLASSIC_FIREWALL resolves both the traffic drop and the missing telemetry in a single configuration change while keeping existing 10.0.0.0/8 VPC protections intact.
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