- A
Use Apache Kafka with idempotent producers and transactional APIs.
Kafka's transactional support ensures exactly-once semantics, and its log-based architecture handles bursty data well.
- B
Use Amazon SQS with FIFO queues for ordering and deduplication.
Why wrong: SQS FIFO provides exactly-once but is a proprietary service, deviating from cloud-native portability principles.
- C
Use RabbitMQ with publisher confirms and consumer acknowledgements.
Why wrong: RabbitMQ's at-least-once semantics don't guarantee exactly-once processing.
- D
Implement an HTTP endpoint that the IoT devices call directly.
Why wrong: HTTP callbacks are unreliable and don't guarantee delivery or exactly-once processing.
Question 478 of 997
Exactly-Once Semantics — Apache Kafka in Cloud Native | Kubernetes and Cloud Native Associate Explained
This KCNA practice question tests your understanding of cloud native architecture. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A startup is designing a cloud-native application that processes IoT sensor data. The data arrives in bursts, and processing must be fault-tolerant with exactly-once semantics. The team considers Apache Kafka, RabbitMQ, and Amazon SQS. Which choice best meets the requirements of a cloud-native architecture?
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
✓
Use Apache Kafka with idempotent producers and transactional APIs.
Apache Kafka with idempotent producers and transactional APIs is the correct choice because it provides exactly-once semantics (EOS) for bursty IoT data in a cloud-native architecture. Kafka's transactional API ensures atomic writes across partitions, while idempotent producers prevent duplicate records from retries, meeting the fault-tolerance and exactly-once requirements. Kafka also scales horizontally and handles high-throughput bursts natively, aligning with cloud-native principles.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use Apache Kafka with idempotent producers and transactional APIs.
Why this is correct
Kafka's transactional support ensures exactly-once semantics, and its log-based architecture handles bursty data well.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use Amazon SQS with FIFO queues for ordering and deduplication.
Why it's wrong here
SQS FIFO provides exactly-once but is a proprietary service, deviating from cloud-native portability principles.
- ✗
Use RabbitMQ with publisher confirms and consumer acknowledgements.
Why it's wrong here
RabbitMQ's at-least-once semantics don't guarantee exactly-once processing.
- ✗
Implement an HTTP endpoint that the IoT devices call directly.
Why it's wrong here
HTTP callbacks are unreliable and don't guarantee delivery or exactly-once processing.
Common exam traps
Common exam trap: answer the scenario, not the keyword
A common misconception is that Amazon SQS FIFO queues provide exactly-once processing, which might lead candidates to choose it. However, while SQS FIFO does offer exactly-once processing via deduplication, it is a proprietary AWS service. In a CNCF context, Apache Kafka (a CNCF graduated project) is preferred for cloud-native architectures because it provides exactly-once semantics with transactional APIs that guarantee atomicity across partitions, and it handles high-throughput bursts natively. The key distinction is not about whether exactly-once is possible, but about alignment with open-source cloud-native principles.
Detailed technical explanation
How to think about this question
Kafka's exactly-once semantics rely on the transactional coordinator and a unique producer ID (producer.id) combined with a sequence number per partition; the broker rejects duplicate sequence numbers, ensuring idempotent writes. The transactional API uses a two-phase commit protocol (prepare and commit) to atomically write to multiple partitions, with a transaction timeout (default 1 minute) that aborts uncommitted transactions. In a real-world IoT scenario, bursty data from thousands of sensors can overwhelm systems without Kafka's partitioning and log-compacted topics, which retain the latest state for each key.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the KCNA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Cloud Native Architecture — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Native Architecture practice questions
Targeted practice on this topic area only
- →
All KCNA questions
997 questions across all exam domains
- →
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
- →
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related KCNA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Kubernetes Fundamentals practice questions
Practise KCNA questions linked to Kubernetes Fundamentals.
Container Orchestration practice questions
Practise KCNA questions linked to Container Orchestration.
Cloud Native Architecture practice questions
Practise KCNA questions linked to Cloud Native Architecture.
Cloud Native Observability practice questions
Practise KCNA questions linked to Cloud Native Observability.
Cloud Native Application Delivery practice questions
Practise KCNA questions linked to Cloud Native Application Delivery.
KCNA fundamentals practice questions
Practise KCNA questions linked to KCNA fundamentals.
KCNA scenario practice questions
Practise KCNA questions linked to KCNA scenario.
KCNA troubleshooting practice questions
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Start a free KCNA practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this KCNA question test?
Cloud Native Architecture — This question tests Cloud Native Architecture — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Apache Kafka with idempotent producers and transactional APIs. — Apache Kafka with idempotent producers and transactional APIs is the correct choice because it provides exactly-once semantics (EOS) for bursty IoT data in a cloud-native architecture. Kafka's transactional API ensures atomic writes across partitions, while idempotent producers prevent duplicate records from retries, meeting the fault-tolerance and exactly-once requirements. Kafka also scales horizontally and handles high-throughput bursts natively, aligning with cloud-native principles.
What should I do if I get this KCNA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More KCNA practice questions
- Which CNCF project provides a graduated service mesh implementation that includes features like traffic management, secu…
- A pod in the 'production' namespace is in a CrashLoopBackOff state. The pod has been running successfully for several da…
- You need to ensure that a pod runs on a node with SSD storage. How can you achieve this?
- Match each Kubernetes resource to its primary purpose.
- Match each Kubernetes security concept to its definition.
- Which three of the following are valid methods to create or update resources in Kubernetes? (Choose three.)
Last reviewed: Jun 30, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.