When implementing a saga pattern for distributed transactions in Kafka, which approach best fits the event choreography style?

hard📝 Application Q9 of 15

Kafka - Event-Driven Architecture

AA central orchestrator sends commands to each service to execute transaction steps sequentially

BEach service emits events and reacts to others' events to progress the transaction independently

CAll services write to a shared database to coordinate transaction state

DKafka brokers manage transaction rollback automatically without service involvement

Step-by-Step Solution

Solution:

Step 1: Understand saga pattern
Saga manages distributed transactions via compensating actions.
Step 2: Identify choreography approach
Services communicate by emitting and consuming events without central control.
Final Answer:
Each service emits events and reacts to others' events to progress the transaction independently -> Option B
Quick Check:
Choreography relies on event-driven independent service coordination [OK]

Quick Trick: Saga choreography uses event-driven independent service reactions [OK]

Common Mistakes:

MISTAKES

Master "Event-Driven Architecture" in Kafka

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kafka Quizzes