Why securing Kafka protects data - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable SSL encryption in Kafka configuration.

Kafka

security.protocol=[1]

Drag options to blanks, or click blank then click option'

ASASL_SSL

BPLAINTEXT

CSASL_PLAINTEXT

DSSL

Attempts:

3 left

💡 Hint

Common Mistakes

Using PLAINTEXT leaves data unencrypted.

Confusing SASL options with SSL encryption.

Setting security.protocol to SSL enables encryption of data in transit, protecting it from interception.

2fill in blank

medium

Complete the code to configure Kafka to require client authentication.

Kafka

ssl.client.auth=[1]

Drag options to blanks, or click blank then click option'

Arequired

Boptional

Cdisabled

Dnone

Attempts:

3 left

💡 Hint

Common Mistakes

Setting client auth to none allows anonymous connections.

Using optional does not enforce strict security.

Setting ssl.client.auth to required forces clients to present certificates, ensuring only authorized clients connect.

3fill in blank

hard

Fix the error in the Kafka ACL command to allow user 'alice' to read from topic 'orders'.

Kafka

kafka-acls --add --allow-principal User:[1] --operation Read --topic orders

Drag options to blanks, or click blank then click option'

Aguest

Balice

Cadmin

Dbob

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong user name in the ACL command.

Forgetting to specify the correct topic.

The principal must match the user name 'alice' to grant read access to that user.

4fill in blank

hard

Fill both blanks to create a Kafka ACL that denies user 'eve' from writing to topic 'payments'.

Kafka

kafka-acls --add --deny-principal User:[1] --operation [2] --topic payments

Drag options to blanks, or click blank then click option'

Aeve

BWrite

CRead

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using Read instead of Write operation.

Specifying the wrong user name.

To deny user 'eve' from writing, the principal must be 'eve' and the operation 'Write'.

5fill in blank

hard

Fill the two blanks to configure Kafka to use SASL authentication with the SCRAM-SHA-256 mechanism.

Kafka

security.protocol=[1]
sasl.mechanism=[2]
sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required;

Drag options to blanks, or click blank then click option'

ASASL_SSL

BSCRAM-SHA-256

CPLAINTEXT

DSCRAM-SHA-512

Attempts:

3 left

💡 Hint

Common Mistakes

Using PLAINTEXT disables encryption.

Confusing SCRAM-SHA-256 with SCRAM-SHA-512.

Mismatching security.protocol and sasl.mechanism.

Using SASL_SSL for security.protocol enables SASL authentication over SSL. The mechanism SCRAM-SHA-256 specifies the authentication method. The JAAS config line is standard for SCRAM login.

Practice

1. Why is it important to secure Apache Kafka in a data system?

easy

A. To reduce the size of messages

B. To make Kafka run faster

C. To allow anyone to access data easily

D. To prevent unauthorized users from reading or changing messages

Solution

1. Step 1: Understand Kafka's role in data systems

   Kafka handles message streams that may contain sensitive data.

2. Step 2: Identify the risk of unsecured Kafka

   If Kafka is not secured, unauthorized users can read or modify messages, risking data leaks or corruption.

3. Final Answer:

   To prevent unauthorized users from reading or changing messages -> Option D

4. Quick Check:

   Securing Kafka = Prevent unauthorized access [OK]

Hint: Think about who should see your data [OK]

Common Mistakes:

• Confusing security with performance
• Thinking security reduces message size
• Assuming open access is safe

2. Which Kafka configuration enables encryption of data in transit?

easy

A. enable.idempotence=true

B. auto.offset.reset=earliest

C. security.protocol=SSL

D. log.retention.hours=168

Solution

1. Step 1: Identify encryption setting in Kafka configs

   Encryption in transit uses SSL/TLS protocols.

2. Step 2: Match setting to encryption

   The config security.protocol=SSL enables SSL encryption for Kafka communication.

3. Final Answer:

   security.protocol=SSL -> Option C

4. Quick Check:

   Encryption setting = security.protocol=SSL [OK]

Hint: Look for SSL or TLS in config names [OK]

Common Mistakes:

• Choosing unrelated configs like retention or offsets
• Confusing idempotence with security
• Ignoring protocol settings

3. Given this Kafka producer config snippet:

props.put("security.protocol", "SASL_SSL");
props.put("sasl.mechanism", "PLAIN");
props.put("ssl.truststore.location", "/path/to/truststore.jks");

What is the main security feature enabled here?

medium

A. Data encryption and user authentication

B. Only data compression

C. No security, just logging

D. Automatic message deletion

Solution

1. Step 1: Analyze the config properties

   The security.protocol is set to SASL_SSL, which means SSL encryption plus SASL authentication.

2. Step 2: Understand SASL and SSL roles

   SSL encrypts data in transit, SASL provides user authentication. The truststore location supports SSL trust verification.

3. Final Answer:

   Data encryption and user authentication -> Option A

4. Quick Check:

   SASL_SSL = encryption + authentication [OK]

Hint: SASL_SSL means both encryption and authentication [OK]

Common Mistakes:

• Thinking it only compresses data
• Ignoring authentication part
• Assuming no security is set

4. You configured Kafka with SASL_PLAINTEXT but forgot to set sasl.jaas.config. What will happen?

medium

A. Kafka will allow connections without authentication

B. Kafka will reject connections due to missing credentials

C. Kafka will encrypt data automatically

D. Kafka will crash immediately

Solution

1. Step 1: Understand SASL_PLAINTEXT usage

   SASL_PLAINTEXT requires authentication but does not encrypt data.

2. Step 2: Effect of missing sasl.jaas.config

   This config provides credentials. Without it, Kafka cannot authenticate clients and will reject connections.

3. Final Answer:

   Kafka will reject connections due to missing credentials -> Option B

4. Quick Check:

   Missing credentials = connection rejected [OK]

Hint: Missing auth config blocks connections [OK]

Common Mistakes:

• Assuming no authentication needed
• Thinking data is encrypted automatically
• Expecting Kafka to crash

5. You want to secure Kafka to meet privacy rules by encrypting data at rest and in transit, and controlling who can read topics. Which combination should you use?

hard

A. Enable SSL for encryption in transit, enable Kafka ACLs for access control, and use disk encryption for data at rest

B. Only enable SSL, no access control needed

C. Use SASL_PLAINTEXT and disable ACLs

D. Rely on network firewall only

Solution

1. Step 1: Identify encryption needs

   Encrypting data in transit requires SSL/TLS; data at rest needs disk or volume encryption.

2. Step 2: Identify access control needs

   Kafka ACLs control who can read or write topics, essential for privacy compliance.

3. Step 3: Combine security features

   Enable SSL for encryption in transit, enable Kafka ACLs for access control, and use disk encryption for data at rest covers encryption in transit, encryption at rest, and access control.

4. Final Answer:

   Enable SSL for encryption in transit, enable Kafka ACLs for access control, and use disk encryption for data at rest -> Option A

5. Quick Check:

   Encryption + ACLs + disk encryption = full security [OK]

Hint: Combine encryption and access control for full protection [OK]

Common Mistakes:

• Thinking SSL alone is enough
• Ignoring access control
• Relying only on network firewall