Back-End Development Message Queues and Event-Driven Architecture 2

Question 1

How does Apache Kafka differ from traditional message queues?

Accepted Answer

It stores messages as an immutable, ordered log that consumers can replay

Answer

Kafka persists messages in an append-only log with configurable retention, allowing consumers to re-read or replay historical messages from any offset.

Question 2

In RabbitMQ, what is the role of an 'exchange'?

Accepted Answer

A routing component that receives messages and routes them to queues based on rules

Answer

An exchange receives messages from producers and routes them to one or more queues according to its type and binding rules.

Question 3

What is a Kafka consumer group?

Accepted Answer

A collection of consumers that together consume all partitions of a topic

Answer

A consumer group distributes a topic's partitions among its members so that each partition is consumed by exactly one member, enabling parallel processing.

Question 4

What does 'at-least-once delivery' mean in a messaging system?

Accepted Answer

A message is delivered one or more times, potentially resulting in duplicates

Answer

At-least-once delivery guarantees no messages are lost but may redeliver messages after failures, requiring consumers to handle duplicates.

Question 5

What is 'event sourcing' in back-end architecture?

Accepted Answer

Storing all state changes as an ordered, immutable sequence of events

Answer

Event sourcing persists every state change as an event so the current state can always be rebuilt by replaying the event log.

Back-End Development Practice Test

Back-End Development Practice Test

Back-End Development Message Queues and Event-Driven Architecture 2