Kafka Manager/UI tools - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start Kafka Manager with the default port.

Kafka

bin/kafka-manager [1]

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

A-Dhttp.port=8080

B-Dhttp.port=9092

C-Dhttp.port=7000

D-Dhttp.port=9000

Attempts:

3 left

💡 Hint

Common Mistakes

Using common web port 8080 instead of Kafka Manager's default 9000.

Using Kafka broker port 9092 instead of Kafka Manager UI port.

Not specifying any port and expecting it to start automatically.

The default port for Kafka Manager UI is 9000, so you need to specify -Dhttp.port=9000 to start it on that port.

2fill in blank

medium

Complete the configuration line to add a Kafka cluster in Kafka Manager.

Kafka

kafka-manager.zkhosts=[1]

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

Alocalhost:2181

Blocalhost:9092

Clocalhost:8080

Dlocalhost:7000

Attempts:

3 left

💡 Hint

Common Mistakes

Using Kafka broker port 9092 instead of ZooKeeper port 2181.

Using the Kafka Manager UI port instead of ZooKeeper port.

The zkhosts setting requires the ZooKeeper host and port, which is usually localhost:2181.

3fill in blank

hard

Fix the error in the command to start Kafka Manager with a custom config file.

Kafka

bin/kafka-manager -Dconfig.file=[1]

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

Aconf/application.conf

Bconf/application.txt

Cconf/application.yaml

Dconf/application.json

Attempts:

3 left

💡 Hint

Common Mistakes

Using unsupported config file formats like .txt, .json, or .yaml.

Misspelling the config file name.

The Kafka Manager config file must be a .conf file, usually named application.conf.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps topic names to their partition count if partitions are more than 3.

Kafka

{topic: [1] for topic, partitions in topics.items() if partitions [2] 3}

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

Apartitions

B==

C>

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using equality operator instead of greater than.

Mapping topic to topic name instead of partition count.

This comprehension maps each topic to its partition count only if the partition count is greater than 3.

5fill in blank

hard

Fill all three blanks to filter topics with more than 5 partitions and create a dictionary with uppercase topic names and their partition counts.

Kafka

{ [1]: [2] for [3], partitions in topics.items() if partitions > 5 }

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

Atopic.upper()

Bpartitions

Ctopic

Dpartition

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names like 'partition' instead of 'partitions'.

Not converting topic names to uppercase.

The comprehension creates a dictionary with uppercase topic names as keys and their partition counts as values, filtering only topics with more than 5 partitions.

Practice

1. What is the main purpose of Kafka Manager or similar UI tools for Kafka?

easy

A. To encrypt Kafka data during transmission

B. To provide a visual interface for monitoring Kafka clusters

C. To write Kafka messages automatically

D. To replace Kafka brokers with a graphical system

Solution

1. Step 1: Understand Kafka Manager's role

   Kafka Manager provides a web interface to monitor Kafka clusters visually.

2. Step 2: Compare options

   Options A, B, and C describe functions Kafka Manager does not perform.

3. Final Answer:

   To provide a visual interface for monitoring Kafka clusters -> Option B

4. Quick Check:

   Kafka Manager = Visual monitoring [OK]

Hint: Remember: Kafka Manager shows Kafka data visually [OK]

Common Mistakes:

• Thinking Kafka Manager replaces brokers
• Confusing monitoring with data encryption
• Assuming Kafka Manager writes messages automatically

2. Which command is typically used to start Kafka Manager UI after installation?

easy

A. java -jar kafka-manager.jar

B. kafka-server-start.sh

C. kafka-manager start

D. kafka-console-producer.sh

Solution

1. Step 1: Identify Kafka Manager start command

   Kafka Manager is a Java application started with java -jar kafka-manager.jar.

2. Step 2: Eliminate other options

   Options B and D start Kafka brokers or producers, not Kafka Manager. kafka-manager start is not a valid command.

3. Final Answer:

   java -jar kafka-manager.jar -> Option A

4. Quick Check:

   Start Kafka Manager = java -jar [OK]

Hint: Kafka Manager runs as a Java jar file [OK]

Common Mistakes:

• Using Kafka broker start commands instead
• Assuming a custom 'kafka-manager start' command exists
• Confusing producer commands with UI start

3. Given Kafka Manager is running and connected to a Kafka cluster, what will you see on its dashboard?

medium

A. List of topics, brokers, and consumer groups with their status

B. Only the raw Kafka log files

C. Source code of Kafka brokers

D. Encrypted Kafka messages

Solution

1. Step 1: Understand Kafka Manager dashboard content

   The dashboard shows topics, brokers, and consumer groups with their health and status.

2. Step 2: Check other options

   Raw logs, source code, or encrypted messages are not displayed on the dashboard.

3. Final Answer:

   List of topics, brokers, and consumer groups with their status -> Option A

4. Quick Check:

   Dashboard = Topics + Brokers + Consumers [OK]

Hint: Dashboard shows cluster components and status [OK]

Common Mistakes:

• Expecting raw logs or source code in UI
• Thinking encrypted messages are visible
• Confusing Kafka Manager with log viewer

4. You started Kafka Manager but the UI does not load in the browser. Which is the most likely cause?

medium

A. Kafka Manager requires a database to start

B. Kafka Manager is not connected to any Kafka cluster

C. Kafka topics are empty

D. Kafka Manager server is not running or listening on the expected port

Solution

1. Step 1: Check Kafka Manager server status

   If the UI does not load, the server might not be running or listening on the port.

2. Step 2: Evaluate other options

   Connection to Kafka cluster or empty topics won't prevent UI loading. Kafka Manager does not require a separate database to start.

3. Final Answer:

   Kafka Manager server is not running or listening on the expected port -> Option D

4. Quick Check:

   UI not loading = Server not running [OK]

Hint: Check if Kafka Manager server is running and port is open [OK]

Common Mistakes:

• Assuming empty topics block UI
• Thinking Kafka Manager needs a database to start
• Ignoring server running status

5. You want to monitor consumer lag using Kafka Manager UI. Which steps should you follow to set this up correctly?

hard

A. Install a separate lag monitoring tool and connect it to Kafka Manager

B. Modify Kafka broker configuration to enable lag monitoring

C. Add the Kafka cluster in Kafka Manager, then navigate to consumer groups to view lag metrics

D. Restart Kafka Manager with lag monitoring enabled via command line flag

Solution

1. Step 1: Add Kafka cluster to Kafka Manager

   You must first add your Kafka cluster details in Kafka Manager to connect and monitor it.

2. Step 2: Access consumer groups section

   Once connected, navigate to consumer groups in the UI to see lag metrics and consumer status.

3. Final Answer:

   Add the Kafka cluster in Kafka Manager, then navigate to consumer groups to view lag metrics -> Option C

4. Quick Check:

   Monitor lag = Add cluster + check consumer groups [OK]

Hint: Add cluster first, then check consumer groups for lag [OK]

Common Mistakes:

• Thinking lag monitoring needs separate tools
• Trying to enable lag via broker config
• Restarting Kafka Manager with flags instead of UI steps