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.