QuizzesTopic Configuration & Tuning — Concept Check
intermediate
kafka

Topic Configuration & Tuning — Concept Check

Questions on Topic Configuration & Tuning. Key configs: replication.factor, min.insync.replicas, unclean.leader.election.enable, message.max.bytes, segment.ms — each has significant durability and performance implications.

8 minutes 8 questions Pass at 70%
Time Limit
8 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

8 questions on Topic Configuration & Tuning — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.A Kafka topic is experiencing data loss after a broker failure. The configuration is replication.factor=3, min.insync.replicas=1, and acks=all. What is the likely cause?

    • Amin.insync.replicas=1 is effectively acks=1
    • BReplication factor is too high
    • Cmin.insync.replicas should be 3
    • Dacks=all is incorrect
  2. 2.A Kafka topic has cleanup.policy=compact,delete and retention.ms=604800000. What will happen to the data?

    • AData is only compacted, not deleted
    • BData is compacted and deleted after 7 days
    • CData is deleted immediately after compaction
    • DData is only deleted after 7 days
  3. 3.You notice increased disk usage on a Kafka broker. The topic has segment.bytes=268435456 and segment.ms=3600000. What might be the cause?

    • ARetention period is too long
    • BSegments are too large
    • CMessage size is too small
    • DSegments are rolling too frequently
  4. 4.A topic is configured with replication.factor=3 and min.insync.replicas=2. What is the maximum number of broker failures it can tolerate without data loss?

    • ANo broker failures
    • B3 broker failures
    • C2 broker failures
    • D1 broker failure
  5. 5.A Kafka topic has message.max.bytes=10485760, but consumers are failing to fetch messages. What could be the issue?

    • ASegment.bytes is too large
    • BConsumer max.partition.fetch.bytes is too low
    • CReplication factor is too high
    • DRetention.ms is too short
  6. 6.What happens if unclean.leader.election.enable is set to true in a Kafka topic?

    • AFaster leader election
    • BData loss may occur during leader election
    • CIncreased data durability
    • DNo impact on data durability
  7. 7.A Kafka topic has retention.ms=86400000 and cleanup.policy=delete. What happens to the data after 1 day?

    • AData older than 1 day is deleted
    • BData is compacted
    • CData is archived
    • DData is duplicated
  8. 8.Which configuration ensures that a Kafka topic can recover quickly after a broker restart?

    • AHigher min.insync.replicas
    • BHigher replication.factor
    • CSmaller segment.ms and segment.bytes
    • DLarger retention.bytes