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 deploying an internal microservices application across multiple Google Cloud regions. The application architecture has the following technical requirements:
Which load balancing architecture should you deploy to meet these requirements?
A regional internal Application Load Balancer is an Envoy proxy-based Layer 7 load balancer that distributes HTTP and HTTPS traffic to backends located strictly within a single Google Cloud region. Enabling global access allows client virtual machines located in any region of the VPC to send traffic to the regional load balancer's internal forwarding rule.
While enabling global access expands client reach across regions, a regional internal Application Load Balancer strictly mandates that all associated backend services and backends (such as instance groups or NEGs) reside in the same single region as the load balancer. Consequently, it cannot distribute traffic across multi-region backends or execute automatic cross-region failover when the local region's backends become unhealthy.
--allow-global-access flag only impacts client accessibility from remote VPC regions, not backend placement.All application backends were concentrated in a single region, and the only requirement was allowing cross-region VPC clients to access that single-region service privately.
Confusing client global access with multi-region backend distribution is a common misconception. Global access governs where requests can originate, whereas cross-region load balancers govern where backend instances can reside and fail over.
A cross-region internal Application Load Balancer is a proxy-based Layer 7 load balancing managed service built on the open-source Envoy proxy. It allows organizations to deploy, scale, and manage internal HTTP and HTTPS services using private IP addresses while distributing traffic across backends situated in multiple Google Cloud regions.
INTERNAL_MANAGED load balancing scheme, ensuring traffic never traverses or is exposed to the public internet.GLOBAL_MANAGED_PROXY purpose.The cross-region internal Application Load Balancer is specifically designed for multi-region internal architectures needing Layer 7 routing intelligence and resilient regional failover without requiring external exposure or complex custom proxy layers.
A global external Application Load Balancer is a Layer 7 system implemented across globally distributed Google Front Ends (GFEs). It provides global anycast IPv4/IPv6 external VIPs to terminate user traffic at the edge of Google's network before routing to backends worldwide.
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