In Apache Kafka, what is a topic and how is it structured?
A Kafka topic is a named stream of records, implemented as a durable, append-only log. Each topic is split into partitions, which are the unit of parallelism and ordering: records within a partition are strictly ordered by offset, while across partitions there is no global order. Producers append to partitions and consumers read from them. Topics retain data based on a retention policy (time or size), so unlike a traditional queue, messages are not deleted when read — they can be re-read by replaying offsets.
2 / 5
What is a consumer group in Kafka and how does it enable scaling?
A consumer group is how Kafka load-balances consumption. Kafka assigns each partition to exactly one consumer within a group, so the group collectively processes all partitions in parallel. Adding consumers increases throughput — up to the number of partitions, after which extra consumers sit idle (parallelism is capped by partition count). Different groups each get their own full copy of the stream (pub/sub), while members of the same group share the work (queue semantics). Rebalancing reassigns partitions when consumers join or leave.
3 / 5
What is an offset in Kafka?
An offset is the sequential position of a record within a partition — record 0, 1, 2, and so on. Consumers track their progress by committing the offset of the last record they processed, so after a restart or rebalance they resume from where they left off rather than reprocessing or skipping. Because Kafka retains records, a consumer can seek to an earlier offset to replay history, or to the latest to skip ahead. Offset management (when and whether to commit) directly determines at-least-once vs at-most-once delivery semantics.
4 / 5
Why does Kafka guarantee ordering only within a partition, not across the whole topic?
Ordering is a per-partition guarantee because partitions are the unit of parallelism. If Kafka enforced a single global order across a topic, all records would have to flow through one ordered sequence, destroying the horizontal scalability that partitioning provides. Instead, you control ordering by choosing the partition key: records with the same key (e.g. the same user_id) always go to the same partition and are therefore strictly ordered relative to each other. This lets you preserve order where it matters while scaling across keys.
5 / 5
What does exactly-once semantics (EOS) mean in Kafka stream processing, and why is it hard?
In distributed messaging, at-least-once (retries cause duplicates) and at-most-once (no retries, risk of loss) are easy; exactly-once is hard because network failures force retries, which naturally duplicate. Kafka achieves EOS with idempotent producers (the broker deduplicates retried sends using sequence numbers) and transactions (atomically commit the consumed offset and the produced output together). This ensures a record is processed and its effect recorded once and only once, even across failures — essential for correctness in financial or stateful stream processing.
What does the "Kafka & Event Streaming" vocabulary exercise cover?
This exercise tests real IT vocabulary related to kafka & event streaming through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — this module shares real-world context with 1 other vocabulary module. See "Related vocabulary" below to keep building a connected skill set.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.