The Saga pattern is the correct choice for handling distributed transactions across microservices because it decomposes a long-lived transaction into a sequence of local, atomic transactions, each paired with a compensating action to undo its effects if a subsequent step fails. This approach avoids the tight coupling and performance bottlenecks of distributed locking or two-phase commit, making it ideal for cloud-native, highly scalable environments where eventual consistency is preferred over strong consistency. On the Google Professional Cloud Developer exam, this question tests your understanding of how to maintain data integrity without sacrificing availability—a core challenge in microservices migrations. A common trap is confusing Sagas with two-phase commit; remember that Sagas embrace failure by design, using compensating transactions rather than blocking locks. Memory tip: think of a “Saga” as a story with a safety net—each chapter (local transaction) has an undo button (compensating action) if the plot goes wrong.
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 app to microservices. They need to handle distributed transactions across services. Which pattern should they use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Saga pattern
The Saga pattern is the correct choice for managing distributed transactions across microservices because it breaks a long-lived transaction into a sequence of local transactions, each with a compensating action to roll back if a subsequent step fails. This avoids the tight coupling and performance bottlenecks of distributed locking or two-phase commit, which are unsuitable for cloud-native, highly scalable environments. Sagas can be orchestrated (via a coordinator) or choreographed (via events), and they align with eventual consistency principles required for high availability.
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.
✗
Eventual consistency with compensation
Why it's wrong here
This is a component of the saga pattern, but the question asks for the pattern itself, which is saga.
✓
Saga pattern
Why this is correct
Saga pattern uses local transactions and compensations, providing consistency without locking resources across services.
Related concept
Read the scenario before looking for a memorised answer.
✗
Distributed lock manager
Why it's wrong here
Distributed locks introduce contention and are not a pattern for transactions; they can cause bottlenecks.
✗
Two-phase commit
Why it's wrong here
Two-phase commit requires a coordinator and is not suitable for distributed microservices due to blocking and scalability issues.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that two-phase commit (2PC) is suitable for microservices, but the trap is that 2PC is a synchronous, blocking protocol that undermines scalability and availability, whereas the Saga pattern is the correct asynchronous, compensating approach for distributed transactions in cloud-native apps.
Detailed technical explanation
How to think about this question
Under the hood, the Saga pattern uses either choreography (services emit events and listen for compensating events) or orchestration (a central coordinator invokes each service and triggers compensations on failure). A real-world scenario is an e-commerce order flow: the Order service creates an order, the Payment service charges the card, and the Inventory service reserves stock; if inventory fails, a compensating action refunds the payment. This pattern relies on idempotent operations and reliable event delivery (e.g., via Kafka or AWS SQS) to ensure eventual consistency without distributed locks.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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: Saga pattern — The Saga pattern is the correct choice for managing distributed transactions across microservices because it breaks a long-lived transaction into a sequence of local transactions, each with a compensating action to roll back if a subsequent step fails. This avoids the tight coupling and performance bottlenecks of distributed locking or two-phase commit, which are unsuitable for cloud-native, highly scalable environments. Sagas can be orchestrated (via a coordinator) or choreographed (via events), and they align with eventual consistency principles required for high availability.
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.