CCAAK · Question #14
A developer is working for a company with internal best practices that dictate that there is no single point of failure for all data stored. What is the best approach to make sure the developer is…
The correct answer is D. Set the topic replication factor to 3. Replication factor determines how many copies of each partition exist across different brokers. A replication factor of 3 ensures that even if one or two brokers fail, the data is still available, thus eliminating a single point of failure.
Question
A developer is working for a company with internal best practices that dictate that there is no single point of failure for all data stored. What is the best approach to make sure the developer is complying with this best practice when creating Kafka topics?
Options
- ASet 'min.insync.replicas' to 1.
- BUse the parameter --partitions=3 when creating the topic.
- CMake sure the topics are created with linger.ms=0 so data is written immediately and not held in
- DSet the topic replication factor to 3.
How the community answered
(46 responses)- A4% (2)
- B7% (3)
- C15% (7)
- D74% (34)
Explanation
Replication factor determines how many copies of each partition exist across different brokers. A replication factor of 3 ensures that even if one or two brokers fail, the data is still available, thus eliminating a single point of failure.
Topics
Community Discussion
No community discussion yet for this question.