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.
Your team operates a real-time multiplayer gaming platform hosted in us-central1 behind an External Application Load Balancer with Cloud CDN. Users in Europe and East Asia report sluggish gameplay and high Time To First Byte (TTFB) on dynamic matchmaking and state-update API calls, despite observing low ICMP ping times and fast loading for static images.
Your platform has the following requirements:
Which architectural change should you implement?
us-central1, europe-west1, and asia-east1 behind a global External Application Load Balancer using Premium Tier networking.Multi-region deployment places both compute backends and local data stores in multiple Google Cloud regions close to major user populations. Combined with a global External Application Load Balancer and Premium Tier networking, user traffic enters Google's private global network at the nearest edge Point of Presence (PoP) and is routed to the closest healthy region with available capacity.
europe-west1 and asia-east1 eliminates transoceanic round-trips for European and Asian players.us-central1.Unlike caching-only solutions or regional proxies that still depend on a single central backend, placing both compute and data close to end users directly solves the physical distance bottleneck that causes high Time To First Byte (TTFB) on real-time, non-cacheable traffic.
europe-west1 and asia-east1 behind the External Application Load Balancer while keeping the backend services and database centralized in us-central1.In a distributed frontend, single-region backend architecture, stateless frontend tiers are deployed across multiple geographic regions while core business logic and databases remain centralized in one region (such as us-central1).
europe-west1 or asia-east1 quickly, every dynamic matchmaking or game-state API call still requires a synchronous full round-trip across continents to us-central1.us-central1 introduces over 75 ms of pure fiber-optic propagation delay per round-trip.This architecture would be appropriate if the application served mostly cacheable content or handled writes asynchronously—allowing regional frontends to respond immediately without waiting on round-trips to us-central1.
us-central1 and configure Cloud CDN with the External Application Load Balancer to cache and terminate all dynamic API sessions at Google Front Ends (GFEs).Google Front Ends (GFEs) operate at Google's network edge to terminate TCP and TLS connections close to users, while Cloud CDN caches static and cacheable HTTP(S) responses at edge nodes worldwide.
us-central1.ping results: Pinging an External Application Load Balancer measures round-trip latency only to the nearest GFE (often ~1 ms in the same city), not to the backend VM in us-central1.us-central1.us-central1 leaves distant regions exposed to unavoidable propagation delay.Keeping a single-region deployment with Cloud CDN and External Application Load Balancer optimizations would be optimal if the platform served primarily static or cacheable content, or if users had a high tolerance for latency (100 ms or more).
us-central1 from Premium Tier to Standard Tier networking and replace the External Application Load Balancer with a regional External passthrough Network Load Balancer.Standard Tier networking routes external traffic over public transit ISPs until it enters Google's network at a PoP near the destination region. An External passthrough Network Load Balancer is a regional Layer 4 load balancer that forwards TCP/UDP packets directly to backend VMs without proxying or terminating connections at the edge.
us-central1.us-central1, and a regional load balancer cannot distribute traffic across multiple regions.This configuration would only make sense if you needed to reduce networking egress costs for a single-region, latency-insensitive application, or if you needed to preserve client source IP addresses and handle non-HTTP protocols like UDP within one region.
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