Standalone vs distributed mode in Kafka - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a Kafka broker in standalone mode.

Kafka

bin/kafka-server-start.sh config/server[1].properties

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

A1

Bstandalone

Cdistributed

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'distributed' or 'standalone' as part of the filename causes errors.

Omitting the number leads to missing configuration.

In standalone mode, Kafka uses server1.properties to start a single broker.

2fill in blank

medium

Complete the code to start multiple Kafka brokers in distributed mode.

Kafka

bin/kafka-server-start.sh config/server[1].properties

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

Adefault

Bstandalone

C2

Dsingle

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'standalone' instead of a number causes startup failure.

Using 'default' does not specify a broker number.

In distributed mode, you start multiple brokers with different numbered config files like server2.properties.

3fill in blank

hard

Fix the error in the command to start Kafka in distributed mode.

Kafka

bin/kafka-server-start.sh config/server[1].properties

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

Asingle

Bdefault

Cstandalone

D3

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'standalone' or 'default' instead of a number causes errors.

Omitting the broker number leads to wrong configuration.

To start the third broker in distributed mode, use server3.properties.

4fill in blank

hard

Fill both blanks to configure Kafka for distributed mode with correct broker ID and port.

Kafka

broker.id=[1]
port=[2]

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

A2

B9093

C9092

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same broker ID for multiple brokers causes conflicts.

Using the default port 9092 for all brokers causes port conflicts.

In distributed mode, each broker has a unique broker.id and port. Here, broker 2 uses port 9093.

5fill in blank

hard

Fill all three blanks to create a Kafka producer command for standalone and distributed modes.

Kafka

bin/kafka-console-producer.sh --broker-list localhost:[1] --topic [2] --producer-property acks=[3]

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

A9092

Btest-topic

Call

D9093

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 9092 for distributed mode causes connection issues.

Setting acks to '0' or '1' may cause message loss.

For distributed mode, use port 9093, topic 'test-topic', and set acks to 'all' for full acknowledgment.