Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
An e-commerce platform hosts its core web application and transactional database in a single Google Cloud region (us-central1). Geographically distributed users in Europe and Asia experience high latency (Time to First Byte > 300 ms) when browsing catalog pages and loading static media assets. Additionally, repetitive database read queries during peak traffic spikes are causing high database CPU utilization and application degradation.
You need to optimize the architecture to minimize user latency at the edge and offload repetitive read queries from the central database while avoiding multi-region database replication complexity. What should you do?
us-central1 to cache frequent database read queries.This architecture combines edge-based content delivery via Google Cloud's global network with an in-region, high-performance in-memory caching tier.
us-central1.us-central1) establishes an in-memory caching layer that intercepts and serves frequent, identical database read queries, eliminating database CPU bottlenecks.This approach adheres to standard multi-layer caching best practices (edge caching via Cloud CDN combined with in-memory caching via Memorystore) while leveraging the global external Application Load Balancer to optimize ingress network paths.
us-central1 with Cloud CDN enabled, and implement local in-instance memory caching on each Compute Engine VM.An external passthrough Network Load Balancer is a regional, Layer 4 load balancer built on Google's Maglev technology that routes TCP/UDP traffic directly to backend instances without terminating the transport or application layer.
us-central1. Consequently, TCP and TLS handshakes must traverse the entire physical distance across continents, causing high latency.The workload used non-HTTP protocols, required raw TCP/UDP pass-through with direct server return, or did not require edge caching or SSL offloading.
This option configures load balancing across Google Cloud's Standard Tier network and leverages a secondary Cloud Storage bucket configured for static website hosting to handle catalog items.
The goal was to implement a low-cost, active-passive disaster recovery architecture for a completely static backup website during primary compute downtime.
europe-west1 and asia-east1, configured to query the us-central1 database directly over cross-region VPC peering without a caching layer.This option deploys regional compute clusters close to users in Europe and Asia but routes every dynamic request and database read back to the central us-central1 database across region boundaries.
The workload handled writes asynchronously or had read-only database replicas co-located in each regional compute location.
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