Quick Answer
The Circuit Breaker pattern is the correct choice for preventing cascading failures in microservices because it acts as a safety valve that monitors remote service calls and opens the circuit when failures exceed a defined threshold, causing the system to fail fast and avoid resource exhaustion. This pattern directly isolates failures by stopping repeated calls to a failing service, allowing it time to recover while the rest of the application continues functioning. On the Google Professional Cloud Developer exam, this concept often appears in scenario-based questions about designing resilient distributed systems, where a common trap is confusing the Circuit Breaker with the Retry pattern—remember that retries can actually worsen cascading failures by overwhelming a struggling service. The key distinction is that Circuit Breaker provides proactive failure isolation, while Retry assumes transient issues. A simple memory tip: think of a household circuit breaker that trips to prevent an electrical fire—when the microservice circuit is “open,” it stops the current of requests to prevent a system-wide meltdown.
This PCD practice question tests your understanding of designing highly scalable, available, and reliable cloud-native applications. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company is designing a microservices application. They want to ensure that if one service fails, it does not cascade to other services. Which pattern should they implement?
Auto-scaling
Why wrong: Autoscaling helps with load but does not prevent cascading failures.
Retry with exponential backoff
Why wrong: Retries are useful for transient errors but can compound load if the downstream service is slow.
Load shedding
Why wrong: Load shedding drops requests but does not prevent cascading effectively.
Circuit Breaker
Circuit breaker stops calls to a failing service, preventing cascade.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Circuit Breaker
The Circuit Breaker pattern is the correct choice because it prevents cascading failures by monitoring service calls and opening the circuit when failures exceed a threshold, allowing the system to fail fast and avoid resource exhaustion. This pattern directly addresses the requirement to isolate failures between microservices, ensuring that a failure in one service does not propagate to others.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Auto-scaling
Why it's wrong here
Autoscaling helps with load but does not prevent cascading failures.
Retry with exponential backoff
Why it's wrong here
Retries are useful for transient errors but can compound load if the downstream service is slow.
Load shedding
Why it's wrong here
Load shedding drops requests but does not prevent cascading effectively.
Circuit Breaker
Why this is correct
Circuit breaker stops calls to a failing service, preventing cascade.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Cisco often tests the misconception that retry mechanisms or load shedding are sufficient for failure isolation, but they do not prevent cascading failures because they lack the stateful tripping and fast-fail behavior of the Circuit Breaker pattern.
Detailed technical explanation
The Circuit Breaker pattern operates in three states: closed (normal operation), open (failures exceed threshold, requests are immediately rejected), and half-open (allows a test request to check recovery). In cloud-native applications, this is often implemented with libraries like Hystrix or Resilience4j, which track failure counts and timeouts to trip the circuit. A real-world scenario is a payment service failing; without a circuit breaker, the order service would keep waiting and exhaust its connection pool, causing a cascade; with it, the order service fails fast and can fall back gracefully.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Designing highly scalable, available, and reliable cloud-native applications — study guide chapter
Learn the concepts, then practise the questions
Designing highly scalable, available, and reliable cloud-native applications practice questions
Targeted practice on this topic area only
All PCD questions
500 questions across all exam domains
Google Professional Cloud Developer study guide
Full concept coverage aligned to exam objectives
PCD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PCD questions linked to Designing highly scalable, available, and reliable cloud-native applications.
Practise PCD questions linked to Building and testing applications.
Practise PCD questions linked to Deploying applications.
Practise PCD questions linked to Integrating Google Cloud services.
Practise PCD questions linked to Managing application performance monitoring.
Practise PCD questions linked to PCD fundamentals.
Practise PCD questions linked to PCD scenario.
Practise PCD questions linked to PCD troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Designing highly scalable, available, and reliable cloud-native applications — This question tests Designing highly scalable, available, and reliable cloud-native applications — Read the scenario before looking for a memorised answer..
The correct answer is: Circuit Breaker — The Circuit Breaker pattern is the correct choice because it prevents cascading failures by monitoring service calls and opening the circuit when failures exceed a threshold, allowing the system to fail fast and avoid resource exhaustion. This pattern directly addresses the requirement to isolate failures between microservices, ensuring that a failure in one service does not propagate to others.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 25, 2026
This PCD practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCD exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.