Kafka integration with Hadoop - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Kafka and Hadoop Integration

Which component is primarily responsible for moving data from Kafka to Hadoop in a typical integration setup?

A Kafka Connect with HDFS Sink Connector

B Apache Spark Streaming directly writing to Kafka

C Hadoop MapReduce reading from Kafka topics

D Kafka Producer sending data to HDFS

💡 Hint

Think about the tool designed to connect Kafka with external systems like Hadoop.

Kafka Connect with HDFS Sink Connector is designed to stream data from Kafka topics directly into Hadoop's HDFS storage.

❓ Predict Output

intermediate

Output of Kafka Connect HDFS Sink Configuration

Given the following Kafka Connect HDFS Sink configuration snippet, what is the expected output directory structure in HDFS?

Hadoop

name=hdfs-sink-connector
connector.class=io.confluent.connect.hdfs.HdfsSinkConnector
tasks.max=1
topics=test-topic
hdfs.url=hdfs://namenode:8020
flush.size=3
format.class=io.confluent.connect.hdfs.avro.AvroFormat
hdfs.topics.dir=/user/kafka/topics

A /user/hdfs/data/test-topic/ with JSON files flushed every 3 records

B /user/kafka/topics/test-topic/partition=0/ with Avro files flushed every 3 records

C /tmp/kafka/test-topic/partition=1/ with Parquet files flushed every 1 record

D /user/kafka/test-topic/partition=0/ with CSV files flushed every 5 records

💡 Hint

Look at the topic name, flush size, and format class in the config.

The connector writes to /user/kafka/topics/{topic}/partition={partition}/ with Avro files flushed after 3 records as per flush.size.

❓ data_output

advanced

Data Output Format from Kafka to Hadoop

When using Kafka Connect HDFS Sink with the default Avro format, what is the schema of the stored data files?

A Avro files containing both data and schema embedded in each file

B Plain text files with JSON strings only

C Binary files without any schema information

D CSV files with header rows describing schema

💡 Hint

Consider how Avro format handles schema and data storage.

Avro files embed the schema along with the data, enabling schema evolution and self-describing files.

🔧 Debug

advanced

Identifying Error in Kafka to Hadoop Data Pipeline

Given a Kafka Connect HDFS Sink connector failing with error 'Failed to write to HDFS: Permission denied', what is the most likely cause?

A HDFS Namenode is down

B Kafka topic does not exist

C Kafka Connect worker does not have write permissions on the target HDFS directory

D Kafka Connect configuration missing flush.size parameter

💡 Hint

Think about file system permissions and access rights.

The error indicates the connector cannot write to HDFS due to insufficient permissions on the target directory.

🚀 Application

expert

Optimizing Kafka to Hadoop Data Ingestion

You want to optimize the Kafka Connect HDFS Sink to reduce small file creation and improve throughput. Which configuration change is most effective?

A Set topics to multiple unrelated topics

B Decrease the tasks.max to 1

C Change format.class to CSVFormat

D Increase the flush.size parameter to a larger number

💡 Hint

Think about how flush.size affects file creation frequency.

Increasing flush.size causes the connector to write larger files less frequently, reducing small file overhead and improving throughput.

Practice

1. What is the main purpose of integrating Kafka with Hadoop in data science?

easy

A. To move streaming data into Hadoop storage for analysis

B. To replace Hadoop's storage with Kafka's storage

C. To run machine learning models inside Kafka

D. To visualize data directly from Kafka without storage

Solution

1. Step 1: Understand Kafka and Hadoop roles

   Kafka streams data in real-time, Hadoop stores large data for analysis.

2. Step 2: Identify integration purpose

   Integration moves streaming data from Kafka into Hadoop for big data processing.

3. Final Answer:

   To move streaming data into Hadoop storage for analysis -> Option A

4. Quick Check:

   Kafka streams + Hadoop stores = Integration purpose [OK]

Hint: Kafka streams data; Hadoop stores it for analysis [OK]

Common Mistakes:

• Thinking Kafka replaces Hadoop storage
• Assuming Kafka runs ML models
• Believing visualization happens directly in Kafka

2. Which of the following is the correct command to consume messages from a Kafka topic named sensor_data?

easy

A. kafka-run-class kafka.Consumer sensor_data

B. kafka-console-producer --topic sensor_data --bootstrap-server localhost:9092

C. kafka-console-consumer --topic sensor_data --bootstrap-server localhost:9092

D. hadoop fs -cat /sensor_data

Solution

1. Step 1: Identify Kafka consumer command

   The command to read messages is kafka-console-consumer with topic and server options.

2. Step 2: Match command to options

   kafka-console-consumer --topic sensor_data --bootstrap-server localhost:9092 uses correct consumer command and parameters for topic sensor_data.

3. Final Answer:

   kafka-console-consumer --topic sensor_data --bootstrap-server localhost:9092 -> Option C

4. Quick Check:

   Consumer command with topic and server [OK]

Hint: Consumer command starts with kafka-console-consumer [OK]

Common Mistakes:

• Using producer command instead of consumer
• Confusing Hadoop fs commands with Kafka
• Using outdated or incorrect Kafka class commands

3. Given the following Flume configuration snippet to move Kafka data to HDFS:

agent.sources = kafkaSource
agent.channels = memoryChannel
agent.sinks = hdfsSink

agent.sources.kafkaSource.type = org.apache.flume.source.kafka.KafkaSource
agent.sources.kafkaSource.kafka.bootstrap.servers = localhost:9092
agent.sources.kafkaSource.kafka.topics = sensor_data

agent.channels.memoryChannel.type = memory

agent.sinks.hdfsSink.type = hdfs
agent.sinks.hdfsSink.hdfs.path = /data/sensor
agent.sinks.hdfsSink.channel = memoryChannel

What will be the HDFS directory where Kafka data is stored?

medium

A. /data/sensor

B. /kafka/sensor_data

C. /user/flume/kafka

D. /tmp/kafka_data

Solution

1. Step 1: Locate HDFS path in sink configuration

   The sink hdfsSink has hdfs.path = /data/sensor.

2. Step 2: Confirm data storage directory

   Kafka data consumed by Flume will be stored in /data/sensor on HDFS.

3. Final Answer:

   /data/sensor -> Option A

4. Quick Check:

   HDFS sink path = /data/sensor [OK]

Hint: Check hdfs.path in sink config for storage location [OK]

Common Mistakes:

• Confusing Kafka topic name with HDFS path
• Assuming default Flume user directory
• Ignoring channel configuration

4. You set up Kafka to HDFS data transfer using Flume, but no data appears in HDFS. Which of the following is the most likely error in the Flume config?

medium

A. The memory channel type is set to file

B. The HDFS path is set correctly

C. The Flume agent name is missing

D. The Kafka topic name in kafka.topics is misspelled

Solution

1. Step 1: Check common config errors

   Misspelling Kafka topic means Flume reads no data from Kafka.

2. Step 2: Evaluate options

   Correct HDFS path and channel type do not cause no data; missing agent name causes startup error, not silent failure.

3. Final Answer:

   The Kafka topic name in kafka.topics is misspelled -> Option D

4. Quick Check:

   Wrong topic name = no data read [OK]

Hint: Check Kafka topic spelling first if no data in HDFS [OK]

Common Mistakes:

• Assuming HDFS path causes no data
• Changing channel type incorrectly
• Ignoring agent name errors

5. You want to build a pipeline that streams sensor data from Kafka into Hadoop HDFS and then runs batch analysis daily. Which combination of tools and steps is best?

hard

A. Use Kafka producer to write directly to HDFS, then run Spark streaming

B. Use KafkaSource in Flume to ingest data into HDFS, then run Hadoop MapReduce daily

C. Use Hadoop fs commands to read Kafka topics, then store in local files

D. Use Kafka consumer to write data to local disk, then upload manually to HDFS

Solution

1. Step 1: Identify streaming ingestion method

   Flume with KafkaSource is designed to stream Kafka data into HDFS efficiently.

2. Step 2: Choose batch analysis tool

   Hadoop MapReduce runs batch jobs on HDFS data daily, fitting the requirement.

3. Final Answer:

   Use KafkaSource in Flume to ingest data into HDFS, then run Hadoop MapReduce daily -> Option B

4. Quick Check:

   Flume + KafkaSource + HDFS + MapReduce = correct pipeline [OK]

Hint: Flume streams Kafka to HDFS; MapReduce runs batch jobs [OK]

Common Mistakes:

• Using Kafka producer to write directly to HDFS (not supported)
• Confusing streaming with batch tools
• Manual upload instead of automated pipeline