Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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?
Publish order checkout events to a Cloud Pub/Sub topic and implement independent microservices subscribing to dedicated subscriptions with dead-letter topics
Configure the checkout service to write orders directly to Cloud SQL and use scheduled database polling scripts to invoke downstream APIs
Place an Internal Application Load Balancer with strict rate-limiting policies in front of the existing synchronous REST services
Implement an API Gateway with client-side retry logic using exponential backoff across all synchronous downstream service calls
Publish order checkout events to a Cloud Pub/Sub topic and implement independent microservices subscribing to dedicated subscriptions with dead-letter topics
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.
Configure the checkout service to write orders directly to Cloud SQL and use scheduled database polling scripts to invoke downstream APIs
Place an Internal Application Load Balancer with strict rate-limiting policies in front of the existing synchronous REST services
Implement an API Gateway with client-side retry logic using exponential backoff across all synchronous downstream service calls
StudyCerts
StudyCerts