KCNA Cloud Native Architecture Practice Question
In event-driven architecture, which pattern is commonly used to decouple producers and consumers, allowing asynchronous communication?
⚠ Common exam trap
KCNA often tests the difference between synchronous and asynchronous communication; candidates may pick REST API calls because they are familiar, but they do not decouple producers and consumers.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Event broker (message queue or event bus)
An event broker (message queue or event bus) decouples producers and consumers by allowing producers to publish events without knowing who consumes them, and consumers to subscribe and process events asynchronously. This enables loose coupling, scalability, and resilience. Examples include Apache Kafka, RabbitMQ, and cloud services like AWS EventBridge.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Event broker (message queue or event bus)
Why this is correct
An event broker sits between producers and consumers, persisting and routing messages so neither side knows the other. This satisfies the asynchronous decoupling constraint: producers publish without waiting, consumers process at their own pace, and neither blocks on the other's availability.
- ✗
Shared database
Why it's wrong here
A shared database couples components through a common schema and synchronous reads and writes, so producers and consumers remain tightly bound rather than asynchronously decoupled. It suits simple, low-scale applications sharing state directly, not event-driven architectures needing independent, buffered message exchange.
- ✗
Circuit breaker pattern
Why it's wrong here
Circuit breakers halt calls to a failing dependency to prevent cascading failure; they do not decouple producers from consumers or broker asynchronous delivery. The pattern would be correct when wrapping remote calls that must fail fast during outages, not for enabling event-driven message flow.
- ✗
Synchronous REST API calls
Why it's wrong here
Synchronous REST calls block the caller until a response returns, directly contradicting the asynchronous, decoupled communication the scenario requires. REST is the right choice for request-response interactions needing immediate results, not for fire-and-forget event propagation between independent producers and consumers.
Go deeper
Related to this question
About these practice questions
Courseiva writes every KCNA question from scratch — 930 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CNCF exam blueprint
This KCNA practice question is part of Courseiva's free CNCF 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 KCNA exam.