Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are deploying a stateful web application on Compute Engine Managed Instance Groups (MIGs) across multiple regions behind a load balancer. Your architecture must satisfy these requirements:
Which architectural configuration should you implement?
This configuration attaches Cloud Armor and IAP to a global external Application Load Balancer, but skips verifying the x-goog-iap-jwt-assertion header in application code and configures VPC ingress firewall rules with partner client IP ranges instead of Google Front End (GFE) and health check ranges.
x-goog-iap-jwt-assertion signed JWT prevents the application from cryptographically confirming that requests were authenticated by IAP for the intended backend service (aud).x-goog-iap-jwt-assertion against Google's public keys protects against firewall misconfigurations or intra-VPC spoofing.Allowing partner CIDRs in VPC firewall rules would only be appropriate for direct Layer 3/4 connections without an intervening proxy load balancer, though it would still fail to provide Cloud Armor WAF protection, IAP authentication, or application-level identity verification.
A classic Application Load Balancer is an older global Layer 7 load balancing mode, while Cloud CDN caches HTTP(S) content at Google Front End (GFE) edge locations to lower latency and offload origin servers.
Cache-control: private headers are applied.This setup would be valid only if you intentionally wanted IAP to authenticate requests prior to Cloud Armor evaluation on a legacy load balancer and restricted Cloud CDN strictly to public, non-sensitive static assets on a separate domain while marking authenticated content with Cache-control: private.
Always verify load balancer mode differences when integrating Cloud Armor and IAP, because choosing classic versus global external mode directly flips whether authentication or WAF filtering executes first.
This configuration combines a global external Application Load Balancer with Google Cloud Armor, Identity-Aware Proxy (IAP), session affinity, HTTP(S) health checks, and VPC ingress firewall rules. Together, these services deliver scalable Layer 7 routing, stateful session handling, edge threat filtering, and zero-trust identity verification.
x-goog-iap-jwt-assertion header (checking Google's public keys and the aud claim) to confirm user identity.Unlike a classic Application Load Balancer (where IAP evaluates requests before Cloud Armor), a global external Application Load Balancer executes edge security filtering first. It also avoids the Layer 7 limitations of TCP proxies and the bypass vulnerabilities of permissive VPC firewall rules.
A global external Proxy Network Load Balancer (backed by a Target TCP Proxy) distributes Layer 4 TCP streams across regions, while IAP TCP forwarding establishes encrypted HTTPS tunnels to internal VM ports for administrative protocols such as SSH (port 22) and RDP (port 3389).
x-goog-iap-jwt-assertion HTTP headers into application requests.x-goog-iap-jwt-assertion headers are generated exclusively by IAP for HTTP(S) workloads behind an Application Load Balancer, App Engine, or Cloud Run.This configuration would be appropriate if you needed to provide administrators with secure, zero-trust SSH or RDP access to internal Compute Engine instances via encrypted IAP tunnels rather than hosting an HTTPS web application requiring Layer 7 WAF rules and HTTP identity assertions.
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