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 (host-vpc) connected via VPC Network Peering to a transit VPC that exports dynamic routes to on-premises networks. After recent infrastructure changes, an internal passthrough Network Load Balancer in a service project stops forwarding traffic, and VMs lose connectivity to an on-premises CIDR (10.240.0.0/22).
Network Analyzer reports two active insights:
10.240.0.0/22.Which remediation and validation workflow should you execute to restore data-plane forwarding and verify path integrity?
host-vpc, create a high-priority custom static route for 10.240.0.0/22 pointing to the peering network, add an ingress allow firewall rule in the service project permitting traffic from the load balancer forwarding rule IP, and immediately run Connectivity Tests configuration analysis.This approach attempts to override a shadowed peering dynamic route with a custom static route, isolate load balancer traffic using a service-project firewall rule, and verify results immediately with Connectivity Tests.
host-vpc), not the service project. Additionally, allowing the forwarding rule IP does not permit Google Cloud health check probes, which originate from Google's dedicated health check IP ranges.Creating a custom static route in host-vpc would be valid only when routing traffic for a non-overlapping external CIDR (such as a default route or a prefix outside any VPC subnet) toward a specific next-hop VM or internal load balancer, and when waiting at least 120 seconds before validating.
host-vpc for the internal client subnet, and use Network Topology to simulate end-to-end packet paths.This approach configures a Cloud Monitoring metrics scope for multi-project visibility, opens host-vpc ingress firewalls for client subnets, and inspects traffic in Network Topology.
host-vpc, leaving 10.240.0.0/22 trapped by local subnet routing.Configuring a metrics scope and using Network Topology would be appropriate when you need a unified operational dashboard across independent projects to investigate historical latency trends or regional throughput bottlenecks rather than active configuration drops.
ip route list table local on the backend VMs to confirm the forwarding rule route, advertise a more specific /23 dynamic route from the transit VPC peer, and wait 10 minutes for Network Analyzer to clear both insights as proof of data-plane delivery.This workflow checks the Linux guest OS local routing table on backend instances, adjusts BGP prefix advertisements from the peered transit VPC, and relies on Network Analyzer's periodic refresh to confirm packet delivery.
ip route list table local verifies that the Google Guest Agent installed the load balancer VIP local route inside the VM, but it does not unblock the VPC implied deny ingress rule dropping health check probes before packets ever reach the VM./23 subnets within 10.240.0.0/22, the overlapping subnet route in host-vpc still encompasses those addresses and takes strict routing precedence over imported peering dynamic routes.Checking ip route list table local is the right step when health checks succeed and VPC firewalls allow traffic, yet backend VMs fail to accept packets destined for the load balancer VIP due to a stopped Guest Agent or metadata server blockage.
host-vpc, create an ingress allow firewall rule permitting the Google Cloud health check probe ranges to the backend VMs, delete and re-create the overlapping subnet identified via the Cloud Logging link with a non-conflicting CIDR, and wait 20–120 seconds before validating the paths with Connectivity Tests configuration analysis.This workflow combines Shared VPC firewall remediation, subnet conflict resolution guided by Network Analyzer's change correlation, and propagation-aware validation using Connectivity Tests to restore and verify end-to-end forwarding.
host-vpc for the Google Cloud health check probe ranges overrides the implied deny ingress rule so probes reach the backends.10.240.0.0/22 to follow the imported peering dynamic route.Unlike static route workarounds or guest OS checks, this approach directly removes the VPC-level implied deny and subnet route precedence conflict while following the exact timing requirements for Connectivity Tests verification.
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