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 is preparing for a high-traffic flash sale event. The core web service is hosted on Google Kubernetes Engine (GKE) behind a global external Application Load Balancer with backends distributed across multiple Google Cloud regions.
To ensure the system meets a Service Level Objective (SLO) of 99th percentile (p99) latency below 200 ms, the engineering team needs to design a distributed load testing framework to simulate massive, concurrent user traffic originating from multiple geographic regions while verifying Horizontal Pod Autoscaler (HPA) and cluster autoscaling performance.
How should the team architect this load testing solution on Google Cloud?
Locust is an open-source, distributed load testing framework that allows engineers to define user behavior in standard Python code. When deployed on Google Kubernetes Engine (GKE), Locust operates in a coordinator-worker (master-worker) topology. The master pod coordinates test execution, collects metrics, and provides a centralized web UI/API for reporting, while multiple worker pods distributed across nodes scale out horizontally to generate high volumes of concurrent HTTP/HTTPS requests.
This approach uses a single vertically scaled virtual machine running Apache JMeter to execute multi-threaded test scripts targeted directly at private Kubernetes Pod IP addresses within the internal VPC network.
The objective were an isolated, low-concurrency micro-benchmark of an internal component without external dependencies or load balancer integration.
Google Cloud Armor security policies provide Layer 7 filtering, DDoS mitigation, and rate-limiting controls to protect web applications by restricting incoming request volumes or throttling suspicious clients at the Google edge.
The goal was to protect backend applications from volumetric abuse or throttle brute-force attacks from specific client IP ranges.
This approach uses traffic management capabilities on an internal Application Load Balancer to shift real live user production traffic to a non-production staging cluster during quiet periods to observe performance.
The team was performing a blue/green or canary rollout of a new microservice version to validate stability against live internal enterprise traffic.
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