The answer is the Circuit Breaker pattern. This pattern is correct because it prevents cascading failures in a microservices architecture by monitoring calls to a downstream service and, once a defined failure threshold is exceeded, immediately short-circuits the request, returning a fallback response instead of making the failing call. In a GKE environment, this is typically implemented using a service mesh like Istio or Envoy sidecar proxies, which can be configured with circuit breaker settings to stop routing traffic to unhealthy pods, allowing the system to recover gracefully. On the Google Professional Cloud Developer exam, this question tests your understanding of resilience patterns for distributed systems, often appearing in scenarios about fault isolation and traffic management. A common trap is confusing the Circuit Breaker with the Retry pattern—retries can actually worsen cascading failures by overwhelming a struggling service. Memory tip: think of an electrical circuit breaker that trips to prevent a short circuit from damaging the entire house; in microservices, it trips to stop failures from spreading across your GKE cluster.
PCD Practice Question: Designing highly scalable, available, and reliable cloud-native applications
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 team is migrating a monolithic application to microservices on Google Kubernetes Engine (GKE). They want to ensure that if one microservice fails, it does not cascade to other services. Which design pattern should they implement?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Circuit Breaker pattern
The Circuit Breaker pattern is correct because it prevents cascading failures by monitoring for failures in a downstream microservice and, once a threshold is exceeded, immediately failing requests to that service without attempting the call. In GKE, this can be implemented using tools like Istio or Envoy sidecar proxies, which can be configured with circuit breaker settings to stop traffic to unhealthy pods, allowing the system to recover gracefully.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Circuit Breaker pattern
Why this is correct
Circuit Breaker pattern prevents cascading failures by opening the circuit when failures exceed a threshold.
Related concept
Read the scenario before looking for a memorised answer.
✗
Event-driven architecture
Why it's wrong here
Event-driven architecture decouples services but does not directly prevent cascading failures.
✗
Retry with exponential backoff
Why it's wrong here
Retry with exponential backoff helps with transient failures but does not prevent cascading failures.
✗
Bulkhead pattern
Why it's wrong here
Bulkhead isolates resources per service but does not stop requests to a failing service.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between patterns that prevent cascading failures (Circuit Breaker) versus patterns that handle transient failures (Retry) or isolate resources (Bulkhead), so candidates mistakenly choose Retry or Bulkhead because they sound like they prevent failure spread, but they do not provide the fail-fast mechanism that stops the cascade.
Detailed technical explanation
How to think about this question
Under the hood, the Circuit Breaker pattern operates in three states: closed (normal operation), open (failures exceed threshold, requests fail immediately), and half-open (a probe request is allowed to test recovery). In GKE, this can be implemented via Istio's DestinationRule with trafficPolicy.connectionPool.http.maxRequestsPerConnection and outlierDetection settings, which automatically eject unhealthy pods from the load balancing pool. A real-world scenario is a payment service that fails due to a downstream database outage; without a circuit breaker, all services calling it would hang and exhaust their own resources, leading to a system-wide outage.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
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
Got this wrong? Here's your next step.
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 — This question tests Designing highly scalable, available, and reliable cloud-native applications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Circuit Breaker pattern — The Circuit Breaker pattern is correct because it prevents cascading failures by monitoring for failures in a downstream microservice and, once a threshold is exceeded, immediately failing requests to that service without attempting the call. In GKE, this can be implemented using tools like Istio or Envoy sidecar proxies, which can be configured with circuit breaker settings to stop traffic to unhealthy pods, allowing the system to recover gracefully.
What should I do if I get this PCD question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
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 →
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.
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.