KCNA Cloud Native Architecture Practice Question
In an event-driven architecture, what is the role of an event broker?
⚠ Common exam trap
CNCF often tests the misconception that the event broker performs processing or transformation, but its core role is purely intermediary—routing events without executing business logic.
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
✓
To intermediate between event producers and consumers
In an event-driven architecture, the event broker acts as a middleware that decouples event producers from consumers by receiving events from producers and forwarding them to interested consumers. This intermediary role ensures asynchronous communication, scalability, and fault tolerance without requiring producers and consumers to be directly aware of each other. Technologies like Apache Kafka, RabbitMQ, or cloud-native services such as AWS EventBridge exemplify this pattern.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
To intermediate between event producers and consumers
Why this is correct
An event broker decouples producers from consumers by receiving published events and routing them to subscribed parties, satisfying the asynchronous, many-to-many delivery constraint of event-driven architecture. It intermediates without producers knowing consumer identities, enabling independent scaling and fault tolerance across services.
- ✗
To run event-processing logic
Why it's wrong here
Processing logic runs in consumers or stream-processing engines such as Flink, which subscribe to the broker; the broker itself only routes and buffers events. A stream processor is correct when the scenario requires aggregation, filtering or windowing of event streams.
- ✗
To transform events into API calls
Why it's wrong here
Brokers route, queue and deliver events between producers and consumers; they do not convert events into synchronous API calls, which would destroy the asynchronous decoupling. Transformation into API calls belongs to an API gateway or integration layer, which would be correct when exposing event data to request-response clients.
- ✗
To store event schemas
Why it's wrong here
Schema storage sits in a schema registry, which persists and versions event contracts; a broker only transports events and may validate against a registered schema. A registry is the right choice when the requirement is enforcing compatibility across 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 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.