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 enterprise is preparing for an annual flash sale and needs to validate that its multi-tier web application hosted on Google Cloud meets a strict Service Level Objective (SLO) of 99.9% availability with 95th-percentile response times under 250 ms during peak load.
The application architecture comprises an External Application Load Balancer, an autoscaled managed instance group (MIG) across multiple zones, and a distributed backend database. During initial 3-minute load test runs generated from an on-premises VM, the backend autoscaling triggers properly, but performance metrics show erratic latency spikes, and the target compute resources fail to reach expected utilization thresholds.
Which load testing strategy should you execute to identify performance bottlenecks and accurately validate system scalability against the SLOs?
This approach utilizes Cloud Pub/Sub to ingest and buffer massive message volumes that are subsequently pulled or pushed to backend subscribers to create sudden load.
The primary architectural goal was to validate the ingestion throughput and dead-letter handling of an asynchronous event-driven pipeline rather than an interactive web service.
Executing a distributed load test using a dedicated test harness (such as Apache JMeter running on Compute Engine VMs within Google Cloud) for an extended duration (at least 20 minutes) ensures that the testing environment properly exercises the entire application stack under realistic conditions.
This approach directly targets the causes of erratic test results—insufficient test duration and client-side resource/network constraints—allowing the team to benchmark true autoscaling responsiveness and load balancer distribution.
This approach changes multiple system parameters at once—such as doubling backend VM sizes, adjusting database configurations, and raising instance bounds—before rerunning benchmark cycles.
The infrastructure baseline had already been isolated and individual parameters were systematically benchmarked in discrete, repeatable cycles.
This method replaces the real business application code with a minimal, non-processing stub (such as a static "hello world" or ping handler) to evaluate raw connection handling.
The sole intent was isolated benchmarking of network edge switching fabrics without evaluating application-tier autoscaling or end-to-end data processing.
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