Bird
Raised Fist0

You want to safely update Kafka broker configurations without downtime. Which approach follows best practices?

hard🚀 Application Q15 of Q15
Kafka - with Java/Python
You want to safely update Kafka broker configurations without downtime. Which approach follows best practices?
AUpdate configs on all brokers simultaneously and restart all at once
BStop the entire Kafka cluster, update configs, then restart all brokers
CUpdate configs on one broker at a time, restart it, then move to next
DChange configs dynamically without any restarts or backups
Step-by-Step Solution
Solution:
  1. Step 1: Understand safe config update practices

    Updating one broker at a time avoids cluster downtime and data loss.
  2. Step 2: Evaluate options for safety and availability

    Update configs on one broker at a time, restart it, then move to next follows the best practice of rolling updates with restarts.
  3. Final Answer:

    Update configs on one broker at a time, restart it, then move to next -> Option C
  4. Quick Check:

    Rolling updates = safer config changes [OK]
Quick Trick: Update brokers one by one to avoid downtime [OK]
Common Mistakes:
MISTAKES
  • Restarting all brokers simultaneously causing downtime
  • Stopping entire cluster unnecessarily
  • Changing configs without backups or restarts

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes