KCNA Cloud Native Architecture Practice Question
In an event-driven architecture using a message broker, which component is responsible for receiving events and forwarding them to subscribed services?
⚠ Common exam trap
KCNA often tests whether candidates confuse the message broker (asynchronous event routing) with the API gateway (synchronous API fronting) or service mesh (service-to-service networking), so all three look like 'traffic' components.
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
✓
Message broker
In event-driven architecture, the message broker (Kafka, RabbitMQ, NATS, Pulsar) is the intermediary that receives published events and routes them to subscribers based on topics, queues, or routing keys. It decouples producers from consumers, buffers events, and handles delivery semantics. Option B names this component directly.
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
A service mesh manages service-to-service traffic, mTLS and observability at the network layer; it does not receive events from a broker nor forward them to subscribers. It is tempting because it handles inter-service communication, and would be correct for securing or observing pod-to-pod calls, not for broker-mediated event delivery.
- ✓
Message broker
Why this is correct
A message broker receives published events and routes them to subscribed services, decoupling producers from consumers. This directly satisfies the stem's requirement for the component that accepts incoming events and forwards them onward, rather than generating, storing or processing them itself.
- ✗
API gateway
Why it's wrong here
An API gateway routes synchronous north-south client requests to backend services, so it cannot receive broker-published events or fan them out to subscribers. It is tempting because it does forward traffic to services, but that role is HTTP request routing, not asynchronous event delivery. The broker itself performs this decoupling.
- ✗
Load balancer
Why it's wrong here
A load balancer distributes inbound connections across identical backends; it holds no subscription registry and cannot route by topic or event type, so it cannot deliver events to subscribed services. It is tempting because it does forward traffic, and would be correct for spreading HTTP requests across replicated stateless web servers.
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 →
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.