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 manages a Shared VPC using hierarchical firewall policies, a global network firewall policy (BEFORE_CLASSIC_FIREWALL), and VPC firewall rules. After enabling Firewall Rules Logging for 30 days, logging costs spiked and east-west latency increased. Firewall Insights reports:
allow rules are shadowed by a parent folder policy.allow-web (TCP 80,443,8080-8090, ICMP, and health check IPs) has unused TCP ports; another zero-hit allow rule shows an 85% future hit prediction.0.0.0.0/0) is priority 100, while internal 10.0.0.0/8 allow is priority 500.Which actions should you take to optimize performance, security, and cost?
Combining Firewall Insights recommendations with Cloud Next Generation Firewall (Cloud NGFW) policy ordering and selective Firewall Rules Logging aligns rule evaluation with actual traffic patterns while controlling telemetry expenses.
allow rules after confirming equivalent coverage in the parent folder's hierarchical firewall policy eliminates configuration sprawl without altering enforcement, since hierarchical policies evaluate before VPC rules.8080-8090) from allow-web tightens the attack surface, while preserving Google Cloud load balancer health check IP ranges prevents backend probe failures. Retaining the zero-hit allow rule with an 85% future hit prediction protects intermittent or seasonal workloads identified by machine learning analysis of similar organizational rules.10.0.0.0/8 allow rule ahead of the Layer 7 URL filtering rule lets internal traffic match immediately without deep packet inspection overhead. Applying the Internet network context to the URL filtering rule prevents its security profile default action from affecting east-west flows.deny rules after troubleshooting stops recurring ingestion charges, which is critical because DENY firewall policy rules emit repeated log entries every 5 seconds for ongoing connection attempts.allow rules while cutting telemetry volume.Unlike indiscriminate rule deletion or elevating Layer 7 inspection to hierarchical policies, this approach respects machine learning hit predictions, mandatory platform IP ranges, Layer 7 evaluation order, and targeted logging to deliver low latency and cost efficiency without compromising security.
This configuration gives the URL filtering rule the highest possible precedence at priority 0 across All network contexts, leaves allow-web untouched due to ICMP, adjusts VPC rule priority numbers, and limits Firewall Rules Logging solely to deny rules.
apply_security_profile_group) at priority 0 with All network contexts forces internal 10.0.0.0/8 traffic through deep inspection before the priority 500 allow rule is reached. Best practices require placing URL filtering rules at the lowest priorities (highest integer values) and separating east-west traffic using network contexts.8080-8090 should be removed.1000 cannot eliminate shadowing from a hierarchical firewall policy, because hierarchical policies always evaluate before VPC rules regardless of VPC priority numbers.deny rules continues generating heavy log volume due to repeated 5-second log entries per denied connection attempt, while disabling logging on all allow rules halts overly permissive rule insights.0 evaluates before 500).All internal and external flows mandated Layer 7 inspection before any bypass rules, ports 8080-8090 were actively required, and the organization accepted ongoing deny logging costs solely for Cloud Monitoring attack alerting.
This configuration changes the global network firewall policy enforcement order to AFTER_CLASSIC_FIREWALL, retains shadowed VPC rules, converts allow-web to goto_next, and relies on VPC Flow Logs to power Firewall Insights.
AFTER_CLASSIC_FIREWALL only evaluates VPC firewall rules before the global network firewall policy. Because both the priority 100 URL filtering rule and the priority 500 10.0.0.0/8 allow rule reside inside the same global network firewall policy, internal egress traffic still hits priority 100 first and undergoes Layer 7 inspection.deny rules.allow-web with goto_next merely delegates matching traffic to downstream rules rather than removing the unused 8080-8090 ports.BEFORE_CLASSIC_FIREWALL and AFTER_CLASSIC_FIREWALL govern ordering between VPC firewall rules and network firewall policies, not priority ordering within a single policy.goto_next passes evaluation to subsequent policies or rules rather than enforcing least privilege.The internal 10.0.0.0/8 rule were a VPC firewall rule needing evaluation ahead of a global policy, while Firewall Rules Logging remained enabled on rules monitored by Firewall Insights.
This approach deletes every rule and IP range that recorded zero hits over the 30-day window, elevates Layer 7 URL filtering into a hierarchical firewall policy, and disables Firewall Rules Logging globally.
allow-web blocks Google Cloud load balancer health probes from reaching backend VMs, causing service outages. Deleting a zero-hit allow rule that carries an 85% future hit prediction disregards machine learning signals derived from active similar rules across the organization, risking failures for periodic batch jobs or failover traffic.allow or deny action on unintended traffic.The zero-hit rule had a low future hit prediction backed by inactive similar rules, the unhit IP blocks were confirmed not to belong to load balancer health checks, URL filtering remained in a global or regional network policy at low priority, and logging stayed enabled on rules requiring ongoing inspection.
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