The answer is the API gateway and event-driven architecture. An API gateway decouples microservices by acting as a single entry point that routes client requests to the appropriate backend service, hiding internal service topology and reducing direct client-to-service coupling. Event-driven architecture further decouples services by enabling asynchronous communication through a message broker like Pub/Sub or Kafka, where services publish and consume events without needing to know about each other, allowing independent evolution and failure isolation. On the Google Professional Cloud Developer exam, this pattern tests your understanding of how to build resilient, loosely coupled systems on Google Cloud, often appearing in scenario-based questions about reducing latency or avoiding cascading failures. A common trap is confusing synchronous API calls with true decoupling—remember that direct HTTP calls between services create tight coupling. Memory tip: "Gateway for direction, Events for connection"—the API gateway handles routing, while events handle service-to-service communication without blocking.
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. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
Which two design patterns help decouple microservices?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Event-driven architecture
Event-driven architecture (B) decouples microservices by allowing them to communicate asynchronously through events, eliminating direct dependencies between services. This pattern uses a message broker (e.g., Kafka, RabbitMQ) to publish and consume events, enabling services to evolve independently without blocking each other.
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.
✗
Service mesh
Why it's wrong here
Service mesh provides observability and security, but does not inherently decouple services.
✓
Event-driven architecture
Why this is correct
Events allow services to communicate without direct dependencies, achieving loose coupling.
Related concept
Read the scenario before looking for a memorised answer.
✗
Database per service
Why it's wrong here
Database per service is a pattern for data isolation, not service decoupling.
✓
API gateway
Why this is correct
API gateway decouples clients from internal service endpoints, enabling independent evolution.
Related concept
Read the scenario before looking for a memorised answer.
✗
Circuit breaker
Why it's wrong here
Circuit breaker improves resilience but does not decouple services.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between patterns that manage coupling (like service mesh or circuit breaker) versus patterns that fundamentally eliminate coupling (like event-driven architecture), leading candidates to select service mesh as a decoupling solution when it actually operates within existing coupled communication.
Detailed technical explanation
How to think about this question
In event-driven architecture, services emit events to a broker (e.g., Apache Kafka using topics and partitions) and other services consume them asynchronously, often with at-least-once delivery semantics. This pattern enables eventual consistency and can be combined with CQRS to separate read and write models, but it introduces complexity in event ordering and idempotency handling. A real-world scenario is an e-commerce system where an order service publishes an 'OrderPlaced' event, and inventory, shipping, and notification services consume it independently without direct RPC calls.
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: Event-driven architecture — Event-driven architecture (B) decouples microservices by allowing them to communicate asynchronously through events, eliminating direct dependencies between services. This pattern uses a message broker (e.g., Kafka, RabbitMQ) to publish and consume events, enabling services to evolve independently without blocking each other.
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.