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 is deploying a regional internal Application Load Balancer in us-central1 backed by a managed instance group (MIG) in the same region. The backend VMs serve an internal microservice over HTTPS on TCP port 8443 using self-signed TLS certificates and expose a readiness endpoint at /healthz that returns HTTP 200 (OK).
You must configure the load balancer and VPC networking to meet the following requirements:
europe-west1 within the same VPC network and on-premises clients connecting through a Cloud VPN tunnel in europe-west1 must be able to reach the load balancer's VIP./healthz over HTTPS every 10 seconds, wait up to 5 seconds for a response, and mark a backend unhealthy after 3 consecutive failed probes.8443.Which configuration should you implement?
8443 with --check-interval=10s, --timeout=5s, and --unhealthy-threshold=3 to avoid certificate validation errors; configure ingress allow firewall rules on tcp:8443 from 35.191.0.0/16 and the regional proxy-only subnet; and enable --allow-global-access on the regional forwarding rule.This option replaces the regional HTTPS health check with a global TCP health check, assuming that global access requires a global health check scope and that self-signed TLS certificates will cause HTTPS probes to fail.
regionHealthChecks) created in the same region (us-central1). Attempting to attach a global health check (healthChecks) to a regional backend service is unsupported and fails validation./healthz and HTTP status: A TCP health check only verifies that a TCP three-way handshake completes on port 8443. It cannot query the /healthz path or confirm that the application returns an HTTP 200 (OK) status code.HTTP 500 responses) to pass if the web server process is still listening./healthz check.Enabling global access on a regional forwarding rule only alters which client regions can reach the VIP; it does not change the regional scope of the backend service or its associated health check.
us-central1 on port 8443 with --request-path=/healthz, --check-interval=10s, --timeout=15s, and --unhealthy-threshold=3; configure ingress allow firewall rules on tcp:8443 from the europe-west1 client subnet and the regional proxy-only subnet; and enable --allow-global-access on the regional forwarding rule.This option configures a regional HTTPS health check with a 15-second timeout paired with a 10-second check interval, and opens backend firewall rules to the europe-west1 client subnet and the proxy-only subnet while omitting Google's centralized health check probe IP range.
--timeout=15s with --check-interval=10s is rejected by the API because a probe's wait window cannot overlap into or extend the interval between successive probes.GCE_VM_IP_PORT NEG) backends behind a regional internal Application Load Balancer, health check probes originate from Google's centralized health checking system (35.191.0.0/16), not from the proxy-only subnet. Omitting 35.191.0.0/16 causes the implied deny ingress rule to drop all health probes, marking every backend VM as UNHEALTHY.europe-west1 client subnet directly to the backend VM firewall rule is unnecessary and overly permissive.NON_GCP_PRIVATE_IP_PORT) and regional internet NEGs, not for Compute Engine MIGs.5s (or the check interval raised to at least 15s), 35.191.0.0/16 replaced the client subnet in the firewall rule, and the backends were MIGs or zonal NEGs.If a backend service mixes hybrid NEGs and zonal NEGs or MIGs, firewall rules must allow both the proxy-only subnet (for distributed Envoy probes and data traffic) and 35.191.0.0/16 (for centralized probes).
us-central1 on port 8443 with --request-path=/healthz, --check-interval=10s, --timeout=5s, and --unhealthy-threshold=3; configure ingress allow firewall rules on tcp:8443 from 35.191.0.0/16 and the regional proxy-only subnet; and enable --allow-global-access on the regional forwarding rule.This configuration pairs a regional HTTPS health check (regionHealthChecks) with least-privilege VPC ingress firewall rules and global access on a regional internal Application Load Balancer forwarding rule. Together, these settings monitor backend application readiness accurately while permitting cross-region VPC and hybrid client traffic to reach a localized backend deployment.
us-central1). Enabling --allow-global-access on the regional forwarding rule removes this regional restriction so client VMs in europe-west1 within the same VPC network (or a peered VPC) and on-premises clients traversing Cloud VPN tunnels or VLAN attachments in europe-west1 can reach the VIP.us-central1 matches the scope of the regional backend service. Setting --request-path=/healthz, --check-interval=10s, --timeout=5s (valid because timeout is less than or equal to the check interval), and --unhealthy-threshold=3 enforces the exact probing cadence and failure tolerance. Google Cloud health check probers do not perform TLS certificate validation, meaning self-signed certificates on the backend VMs are accepted as long as the endpoint returns HTTP 200 (OK).tcp:8443 exclusively from 35.191.0.0/16 and the proxy-only subnet CIDR satisfies both planes without exposing backends to broader client subnets./healthz path routing, and HTTP 200 (OK) application status.us-central1 without duplicating infrastructure in europe-west1.Unlike cross-region load balancers or multi-region backend deployments, enabling global access on a regional internal Application Load Balancer preserves single-region backend locality and operational simplicity while still delivering full multi-region and hybrid client reachability.
us-central1 on port 8443 with --request-path=/healthz, --check-interval=10s, --timeout=5s, and --unhealthy-threshold=3; configure ingress allow firewall rules on tcp:8443 from 35.191.0.0/16 and the regional proxy-only subnet; and enable global dynamic routing mode on the VPC network instead of global access on the forwarding rule.This option correctly configures the regional HTTPS health check and least-privilege VPC firewall rules, but attempts to solve multi-region and hybrid reachability by enabling global dynamic routing mode on the VPC network rather than enabling global access on the forwarding rule.
us-central1) as the load balancer. Client VMs located in europe-west1 cannot reach the regional VIP even when they share the exact same VPC network.us-central1. Traffic arriving through a Cloud VPN tunnel in europe-west1 is dropped regardless of VPC dynamic routing mode.--allow-global-access is explicitly enabled.us-central1, or if --allow-global-access were enabled on the regional forwarding rule.By contrast, a cross-region internal Application Load Balancer has global access enabled by default, whereas a regional internal Application Load Balancer requires explicit global access activation on its forwarding rule to accept traffic from remote regions.
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