KCNA Cloud Native Architecture Practice Question
In event-driven architecture, which component is responsible for decoupling event producers from consumers?
⚠ Common exam trap
CNCF often tests the distinction between synchronous and asynchronous communication patterns, and the trap here is that candidates mistakenly think an API gateway (which handles synchronous requests) can decouple producers and consumers in an event-driven architecture, when in fact it only routes requests without persistent event storage or asynchronous delivery.
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., Apache Kafka, RabbitMQ, or AWS EventBridge) acts as an intermediary that receives events from producers and forwards them to consumers. By decoupling the two, the producer does not need to know the consumer's location or status, and the consumer does not need to be actively listening when the event is published. This enables asynchronous, scalable, and fault-tolerant communication in event-driven architectures.
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
Why this is correct
An event broker sits between producers and consumers, receiving published events and routing them to subscribers, so neither side needs direct knowledge of the other. This intermediary role satisfies the decoupling constraint: producers publish without waiting, and consumers subscribe independently, enabling asynchronous, scalable communication across the event-driven architecture.
- ✗
Event consumer
Why it's wrong here
The consumer only receives and processes events; it does not decouple itself from producers. It is tempting because consumers are the other endpoint, but the broker or event bus provides the intermediary that decouples producers from consumers in event-driven architecture.
- ✗
Event producer
Why it's wrong here
The producer only emits events; it does not decouple itself from consumers. It is tempting because producers initiate events, but decoupling is achieved by the broker or event bus, which sits between producers and consumers and routes events asynchronously.
- ✗
API gateway
Why it's wrong here
An API gateway handles synchronous request-response routing for APIs, not asynchronous event decoupling. It is tempting because gateways sit between clients and services, but event-driven decoupling requires a broker or event bus that buffers and routes events independently of producers.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on KCNA
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which component in an event-driven architecture is responsible for decoupling event producers from consumers?
medium- A.Config server
- ✓ B.Event broker
- C.API gateway
- D.Service mesh
Why B: 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.
Variation 2. In event-driven architecture, which pattern is commonly used to decouple producers and consumers, allowing asynchronous communication?
hard- ✓ A.Event broker (message queue or event bus)
- B.Shared database
- C.Circuit breaker pattern
- D.Synchronous REST API calls
Why A: 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.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.