Designing cloud-native applications
Practise only this domain. 41 questions with explanations, 20 at a time.
Start this domainSample questions
- During an incident, calls from a checkout service to a fraud-scoring service in GKE begin timing out, and failing calls keep piling up. The team needs the failures to be cut off quickly without changing application code. Which control should they add?Hard
- A checkout service on GKE needs a promotional banner turned on for 10 percent of users and turned off later. Changes must reach running pods within about a minute, and no image rebuild may be required. Which approach fits best?Medium
- A worker Deployment on GKE should add replicas when a Pub/Sub subscription's backlog grows and remove them when the backlog drains. Which combination makes this work?Hard
- An order service calls a loyalty service to show reward points during checkout. When the loyalty service is down, checkout should still complete. What should the order service do?Medium
- A Cloud Run aggregator calls pricing, inventory, and shipping APIs for every page view. The pricing API occasionally takes 20 seconds, which exhausts the request time budget and holds up the other calls. What design change best contains that risk?Medium
- A legacy billing monolith must be replaced over the next year. You want a growing share of invoice requests sent to new Cloud Run services while the monolith keeps serving everything else, and you need to be able to roll a route back quickly. Which approach and traffic mechanism fit?Medium