KCNA Cloud Native Architecture Practice Question
Which component in an event-driven architecture is responsible for decoupling event producers from consumers?
⚠ Common exam trap
KCNA often tests the misconception that an API gateway or service mesh handles event decoupling, but they are for synchronous communication; the event broker is the correct component for asynchronous event-driven decoupling.
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
The event broker (e.g., Kafka, RabbitMQ, NATS) is the central component that receives events from producers and routes them to consumers, allowing producers and consumers to operate independently without direct knowledge of each other. It provides asynchronous, decoupled communication by buffering events, managing subscriptions, and ensuring delivery. This decoupling enables scalability, fault tolerance, and independent evolution of services.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Config server
Why it's wrong here
A config server supplies externalised configuration to applications; it holds no event routing or subscription state, so producers and consumers remain directly coupled. It is tempting because config servers are central to cloud-native architectures, and would be correct when the requirement is distributing configuration values to services rather than decoupling event flows.
- ✓
Event broker
Why this is correct
The event broker sits between producers and consumers, receiving published events and routing them onward, so neither side holds direct references to the other. This intermediary role provides the temporal and spatial decoupling that event-driven architectures require.
- ✗
API gateway
Why it's wrong here
An API gateway fronts synchronous request-response calls, routing them to backends; it does not persist events or maintain subscriber queues, so producers and consumers stay coupled. It is tempting because gateways do hide backend endpoints from clients, and would be correct when the requirement is exposing and managing REST or HTTP APIs.
- ✗
Service mesh
Why it's wrong here
A service mesh handles service-to-service traffic through sidecar proxies, providing mTLS, retries and observability, but it does not broker events or hold subscriptions, so producers still address consumers directly. It is tempting because meshes decouple networking concerns from application code, and would be correct when the requirement is securing and observing synchronous service calls.
Go deeper
Related to this question
About these practice questions
One of 930 original KCNA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.