CCAAK · Question #64
A company has an existing Kafka cluster running without SSL/TLS enabled. The customer wants to enable SSL on brokers to secure data in transit, but they would like to give applications connecting to…
The correct answer is C. Create a new listener with SSL enabled. Kafka supports multiple listeners, allowing you to run PLAINTEXT and SSL simultaneously. By creating a new SSL-enabled listener (e.g., on a different port), existing applications can continue using PLAINTEXT while gradually migrating to the SSL listener. This approach avoids…
Question
A company has an existing Kafka cluster running without SSL/TLS enabled. The customer wants to enable SSL on brokers to secure data in transit, but they would like to give applications connecting to this cluster some time to migrate to using SSL connection instead of putting a hard stop. Which solution will meet the customer's requirements?
Options
- AEnable SSL on the current Listener, and do not enable mTLS.
- BModify the advertised listeners setting on brokers to use SSL.
- CCreate a new listener with SSL enabled.
- DEnable SSL on the current listener, and do not implement SSL on application side.
How the community answered
(65 responses)- A12% (8)
- B2% (1)
- C80% (52)
- D6% (4)
Explanation
Kafka supports multiple listeners, allowing you to run PLAINTEXT and SSL simultaneously. By creating a new SSL-enabled listener (e.g., on a different port), existing applications can continue using PLAINTEXT while gradually migrating to the SSL listener. This approach avoids downtime and gives clients time to adapt without enforcing a hard cutover.
Topics
Community Discussion
No community discussion yet for this question.