[Solved] Given this Kafka client configuration snippet:props.put("security.protocol", "SASL_SSL"); props.put("sasl.mechanism", "SCRAM-SHA-256"); props.put("sasl.jaas.config", "org.apache.kafka.common.security.... | Kafka

Kafka - Security

Given this Kafka client configuration snippet:

props.put("security.protocol", "SASL_SSL");
props.put("sasl.mechanism", "SCRAM-SHA-256");
props.put("sasl.jaas.config", "org.apache.kafka.common.security.scram.ScramLoginModule required username=\"user1\" password=\"pass1\";");

What will happen when the client tries to connect?

AClient connects using PLAINTEXT mechanism

BClient connects but without encryption

CClient fails due to missing SSL configuration

DClient connects securely using SCRAM-SHA-256 with encrypted channel

Step-by-Step Solution

Solution:

Step 1: Analyze security.protocol setting
Setting security.protocol to SASL_SSL means the client uses SASL authentication over SSL encrypted connection.
Step 2: Check SASL mechanism and JAAS config
The mechanism is SCRAM-SHA-256 with proper JAAS config providing username and password, so authentication will succeed if credentials are correct.
Final Answer:
Client connects securely using SCRAM-SHA-256 with encrypted channel -> Option D
Quick Check:
SASL_SSL + SCRAM = secure auth [OK]

Quick Trick: SASL_SSL means secure auth with encryption [OK]

Common Mistakes:

Assuming SASL_SSL means no encryption
Ignoring JAAS config for credentials
Confusing SCRAM with PLAINTEXT

Master "Security" in Kafka

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Kafka Quizzes

Given this Kafka client configuration snippet:

Step 1: Analyze security.protocol setting

Step 2: Check SASL mechanism and JAAS config

Final Answer:

Quick Check:

Want More Practice?