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 a Shared VPC where service project VMs reside in Folder2, a child of Folder1. You add an ingress allow rule (TCP port 80, source 10.10.0.0/24) with logging enabled to a hierarchical firewall policy (policy-Y) on Folder2.
When 10.10.0.0/24 traffic reaches the VMs, you observe two issues:
policy-Y is enforcing the traffic or being bypassed by a rule in Folder1.Which approach should you use to diagnose the missing logs and verify hierarchical rule enforcement?
A low-priority (65534) ingress deny rule with logging enabled acts as a "final drop" catch-all rule to log packets that are not matched by any higher-priority allow or deny rules (before hitting the unlogged implied deny-all rule at 65535). The networksecurity.googleapis.com/firewall_threat log records Layer 7 Intrusion Prevention Service (IPS) threat detections from Cloud Next Generation Firewall (Cloud NGFW) firewall endpoints.
10.10.0.0/24 is already reaching the VMs, it is matching an allow rule either in Folder1 or in policy-Y before evaluation could ever reach priority 65534.allow rules in hierarchical firewall policies emit logs to compute.googleapis.com/firewall, not networksecurity.googleapis.com/firewall_threat. Threat logs are only generated when traffic matches an apply_security_profile_group rule and is intercepted by a FirewallEndpoint.65534 deny rules only capture dropped traffic that falls through all explicit higher-priority rules.firewall_threat logs require Cloud NGFW Enterprise, a Security Profile Group, and an active FirewallEndpoint association in the same zone.You were troubleshooting unexpectedly dropped packets in a standalone VPC, or auditing Layer 7 IPS threat signatures intercepted by a Cloud NGFW FirewallEndpoint.
Google Cloud evaluates hierarchical firewall policies from the top of the resource hierarchy downward—from the organization node through parent folders (Folder1) to child folders (Folder2)—before evaluating network-level policies and VPC firewall rules. Only one matching rule is applied per connection, and if a higher-precedence rule matches without logging enabled, lower-priority rules with logging enabled will not generate log entries.
Folder1 (policy-X) shares overlapping attributes (such as 10.10.0.0/16 on TCP port 80) at a higher or equal priority, rendering policy-Y's rule unreachable.10.10.0.0/24 to the VM traces the exact evaluation order and identifies the winning rule.This workflow directly addresses both Shared VPC log placement and top-down hierarchical evaluation, combining static configuration analysis (Firewall Insights), live path simulation (Connectivity Tests), and authoritative log inspection in the host project.
VPC Flow Logs capture sampled metadata about network flows (such as source and destination IP addresses, ports, and protocols) entering or leaving VM network interfaces. A global network firewall policy set to AFTER_CLASSIC_FIREWALLS is evaluated after hierarchical firewall policies and classic VPC firewall rules.
AFTER_CLASSIC_FIREWALLS drops its evaluation precedence below both parent-folder hierarchical policies and classic VPC firewall rules, increasing the likelihood that it will be shadowed by an existing higher-precedence rule.BEFORE_CLASSIC_FIREWALLS, whereas AFTER_CLASSIC_FIREWALLS is specifically intended for fallback rules evaluated last.Folder1 is shadowing Folder2.You did not know the exact source IP addresses, ports, or protocols being used by the application traffic and needed to discover them before writing a new fallback firewall rule.
The Allow rules with no hits insight uses machine learning (ML) models trained on organization-wide firewall rule patterns to predict whether an unused allow rule is likely to receive traffic in the future. Meanwhile, Logs Viewer (roles/logging.viewer) grants read-only access to logs stored within a specific project's Cloud Logging buckets.
Folder1) is shadowing a rule in a child folder (Folder2).You were auditing a standalone (non-Shared VPC) project to identify stale allow rules for decommissioning after at least a week of logging data had been collected.
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