Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is designing a globally distributed multi-tier web application deployed across multiple Google Cloud regions. The compute backends reside in multiple service projects connected to a centralized Shared VPC hosted in a dedicated Production folder.
The architecture must meet the following requirements:
Which architecture and security implementation should you recommend?
This configuration proposes using a cross-region Internal Application Load Balancer and applying hierarchical policies that target the link-local metadata server address (169.254.169.254).
169.254.169.254 provides internal instance metadata and is always allowed by default; it is not the source range used by GFE proxies or standard health check systems.169.254.0.0/16) are reserved for internal infrastructure communication and not load-balanced client workloads.The goal was to build a private, multi-region internal microservices mesh reachable only by clients located within the corporate private network.
This approach deploys a Global External Application Load Balancer but manages firewall rules locally inside individual service projects using standard VPC firewall rules.
35.191.0.0/16 and 130.211.0.0/22). Allowing 0.0.0.0/0 unnecessarily widens the attack surface.The application were deployed within standalone, unshared VPCs where each development team had full administrative control over their isolated network security.
A Global External Application Load Balancer is a Layer 7 load balancer built on globally distributed Google Front End (GFE) proxies that terminates HTTP(S) traffic at points of presence (PoPs) close to users. A hierarchical firewall policy allows organization or folder administrators to define and enforce firewall rules across the entire resource hierarchy, taking precedence over project-level and VPC-level firewall rules.
Production folder covering the host project centrally applies the policy to all backends across all connected service projects.
35.191.0.0/16 and 130.211.0.0/22) are permitted without depending on decentralized service project configurations.This solution combines edge-terminated global HTTP(S) distribution with enterprise governance. It guarantees optimal multi-region traffic balancing while enforcing immutable security perimeters across distributed application backends.
This configuration deploys regional External Passthrough Network Load Balancers in each region and relies on regional network firewall policies configured locally within individual service projects.
0.0.0.0/0 at the service project level exposes workloads directly rather than restricting access to verified load balancer proxies and health checks.The workload required direct Layer 4 passthrough of non-HTTP protocols with client IP preservation and was strictly confined to isolated single-region deployments.
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