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 experiences frequent checkout failures during flash sale events. The current monolithic order service uses synchronous REST calls to communicate with an inventory reservation service, a payment processing gateway, and an email notification system.
During peak traffic, downstream processing delays cause cascading timeouts across the application, leading to dropped checkout transactions and a degraded user experience. The engineering team wants to modernize the architecture using cloud-native design principles to ensure high availability, fault tolerance, and independent service scalability.
Which architectural approach should you recommend to decouple the checkout workflow?
API Gateway acts as an entry point for APIs, managing authentication, routing, and telemetry. Client-side retry logic with exponential backoff instructs client applications or calling services to wait for exponentially increasing intervals before retrying a failed HTTP request.
The system experienced infrequent, transient network blips between a small number of distributed services rather than massive traffic spikes causing downstream resource saturation.
Cloud Pub/Sub is a fully managed, scalable, and durable real-time messaging service that forms the foundation of cloud-native, asynchronous event-driven architectures. By placing Pub/Sub between the ingestion layer and backend processors, producers (such as the frontend checkout service) and consumers (such as payment, inventory, and notification services) are completely decoupled.

This approach eliminates synchronous request-response coupling, eradicates cascading failure domains, and allows each operational domain to evolve, deploy, and scale independently.
An Internal Application Load Balancer (ALB) distributes internal HTTP/HTTPS traffic across multiple backend instances within a Virtual Private Cloud (VPC), while rate limiting throttles requests that exceed predefined thresholds to protect backends from overload.
429 Too Many Requests errors to upstream services. In a flash sale, this directly causes lost customer purchases instead of queuing them for guaranteed asynchronous processing.The primary goal were to protect sensitive internal microservice endpoints against denial-of-service traffic or enforce strict per-client consumption quotas in a synchronous RPC environment.
Database polling uses a centralized relational database, such as Cloud SQL, as a communication queue where the primary service writes records with status flags (e.g., status = PENDING), and background worker scripts periodically query the database to find and process unprocessed rows.
SELECT ... FOR UPDATE or polling queries degrade transactional write performance for checkout users.The application processed low-volume batch tasks where real-time responsiveness is not required and transactional atomicity within a single relational database is mandated.
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