Kafka - Topics and PartitionsWhy does Kafka retain deleted topic data for a configurable period instead of deleting it immediately?ATo allow time for consumers to finish reading data and avoid data lossBBecause immediate deletion causes broker crashesCTo archive data for audit purposes automaticallyDDue to limitations in the file system preventing instant deletionCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand Kafka's design for data safetyKafka retains deleted topic data temporarily to ensure consumers can finish processing messages.Step 2: Rule out incorrect reasonsImmediate deletion does not cause crashes, archiving is not automatic, and file system limitations are not the reason.Final Answer:To allow time for consumers to finish reading data and avoid data loss -> Option AQuick Check:Retention after deletion protects consumer data consumption [OK]Quick Trick: Retention delay protects consumers from losing unread data [OK]Common Mistakes:Thinking deletion delay is due to system crashesAssuming automatic archivingBlaming file system limits
Master "Topics and Partitions" in Kafka9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kafka Quizzes Consumer Groups - Partition assignment - Quiz 14medium Consumer Groups - Group coordinator - Quiz 12easy Consumer Groups - Cooperative vs eager rebalancing - Quiz 14medium Consumers - Why consumers process messages - Quiz 11easy Consumers - Offset management - Quiz 11easy Consumers - Deserialization - Quiz 3easy Kafka Basics and Event Streaming - Kafka vs RabbitMQ vs Redis Pub/Sub - Quiz 4medium Kafka Cluster Architecture - ZooKeeper role (and KRaft replacement) - Quiz 11easy Kafka Cluster Architecture - Broker configuration basics - Quiz 5medium Kafka Cluster Architecture - Broker configuration basics - Quiz 7medium