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 e-commerce company runs a microservices-based checkout system deployed across Google Kubernetes Engine (GKE) and Cloud Run. During peak shopping events, end users report intermittent latency spikes that violate response time Service Level Objectives (SLOs), accompanied by sudden increases in cluster compute consumption. The operations team needs to pinpoint which specific inter-service calls introduce the delays and identify the exact application functions consuming excessive CPU and memory in production.
Which observability strategy should you implement to diagnose these performance bottlenecks?
Active Assist Recommender analyzes infrastructure utilization data to generate recommendations for rightsizing virtual machines and node pools. Horizontal Pod Autoscaler (HPA) dynamically scales the number of Pod replicas up or down in response to observed metrics like average CPU or memory utilization.
The system architecture was already optimized and the objective was simply to dynamically adjust compute capacity to accommodate predictable seasonal traffic fluctuations.
Cloud Logging aggregates system and application log events. By routing logs via an aggregated sink into BigQuery, organizations can perform long-term trend analysis, complex analytical SQL queries, and visualize log patterns in Looker Studio.
The primary requirement was performing deep historical audits of application errors, business transaction records, or retrospective compliance reviews across all projects.
Cloud Monitoring provides infrastructure and platform-level time-series metrics, customizable dashboards, and alerting policies. GKE usage metering tracks resource requests and actual usage (such as CPU, GPU, and TPU consumption) aggregated by Kubernetes namespaces and labels to assist in cost allocation.
The goal was solely to set up high-level operational dashboards, establish SLO alert thresholds, and divide Kubernetes infrastructure costs among different organizational cost centers.
Cloud Trace is a distributed tracing system that collects latency data from applications and displays the flow of requests across multiple network boundaries and microservices in near real time. Cloud Profiler is a continuous, statistical, low-overhead profiling tool that captures CPU utilization and memory allocations directly from production workloads, mapping resource consumption directly to specific source code functions.

Using Cloud Trace alongside Cloud Profiler provides complete vertical observability. Cloud Trace isolates the problematic microservice in the distributed transaction, while Cloud Profiler pinpoints the exact method or loop causing CPU exhaustion and latency inside that service.
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