Why SDK integration enables applications in Kafka - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Kafka producer.

Kafka

from kafka import KafkaProducer
producer = KafkaProducer(bootstrap_servers=[1])

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

A'127.0.0.1:2181'

B'localhost:9092'

C'kafka:2181'

D'localhost:2181'

Attempts:

3 left

💡 Hint

Common Mistakes

Using ZooKeeper port instead of Kafka broker port.

The Kafka producer connects to the Kafka broker using the bootstrap server address, usually 'localhost:9092'.

2fill in blank

medium

Complete the code to send a message to a Kafka topic.

Kafka

producer.send([1], b'Hello Kafka')

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

A'my_topic'

B123

Cb'my_topic'

Dtopic

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a number or bytes instead of a string as topic name.

The send method requires the topic name as a string to send messages.

3fill in blank

hard

Fix the error in the code to properly flush the Kafka producer.

Kafka

producer.[1]()

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

Astart

Bsend

Cclose

Dflush

Attempts:

3 left

💡 Hint

Common Mistakes

Using close() instead of flush(), which stops the producer.

The flush() method ensures all buffered messages are sent to Kafka before continuing.

4fill in blank

hard

Fill both blanks to create a Kafka consumer that subscribes to a topic.

Kafka

from kafka import KafkaConsumer
consumer = KafkaConsumer([1], bootstrap_servers=[2])

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

A'my_topic'

B'localhost:9092'

C'localhost:2181'

D'my_group'

Attempts:

3 left

💡 Hint

Common Mistakes

Using ZooKeeper port 2181 instead of Kafka broker port 9092.

The KafkaConsumer needs the topic name and the Kafka broker address to subscribe and consume messages.

5fill in blank

hard

Fill all three blanks to create a Kafka producer that sends a message and flushes it.

Kafka

producer = KafkaProducer(bootstrap_servers=[1])
producer.send([2], b'Hello')
producer.[3]()

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

A'localhost:9092'

B'test_topic'

Cflush

Dclose

Attempts:

3 left

💡 Hint

Common Mistakes

Using close() instead of flush(), or wrong port for bootstrap_servers.

This code creates a producer connected to the Kafka broker, sends a message to 'test_topic', and flushes the producer to ensure delivery.

Practice

1. Why does integrating a Kafka SDK help developers build applications faster?

easy

A. Because SDKs provide ready-made tools to send and receive messages easily

B. Because SDKs replace the need for any Kafka server

C. Because SDKs automatically write application code for you

D. Because SDKs remove the need for any testing

Solution

1. Step 1: Understand what SDKs provide

   SDKs offer pre-built tools and functions that simplify working with Kafka messaging.

2. Step 2: Recognize how this speeds development

   Using these tools means developers don't write low-level Kafka code, making development faster.

3. Final Answer:

   Because SDKs provide ready-made tools to send and receive messages easily -> Option A

4. Quick Check:

   SDKs simplify messaging = Because SDKs provide ready-made tools to send and receive messages easily [OK]

Hint: SDKs simplify messaging tasks, speeding development [OK]

Common Mistakes:

• Thinking SDK replaces Kafka server
• Believing SDK writes all code automatically
• Assuming SDK removes need for testing

2. Which of the following is the correct way to initialize a Kafka producer using a typical SDK?

easy

A. producer = KafkaProducer('localhost:9092')

B. producer = KafkaProducer(servers=['localhost:9092'])

C. producer = KafkaProducer(bootstrap_servers='localhost:9092')

D. producer = KafkaProducer(connect='localhost:9092')

Solution

1. Step 1: Recall Kafka SDK producer initialization syntax

   Most Kafka SDKs use the parameter 'bootstrap_servers' to specify Kafka brokers.

2. Step 2: Match the correct parameter name

   producer = KafkaProducer(bootstrap_servers='localhost:9092') uses 'bootstrap_servers' correctly with the broker address.

3. Final Answer:

   producer = KafkaProducer(bootstrap_servers='localhost:9092') -> Option C

4. Quick Check:

   Correct parameter name = producer = KafkaProducer(bootstrap_servers='localhost:9092') [OK]

Hint: Remember 'bootstrap_servers' for Kafka connection [OK]

Common Mistakes:

• Using wrong parameter names like 'servers' or 'connect'
• Passing broker as a plain string without parameter
• Confusing producer initialization with consumer

3. Given this Kafka SDK code snippet, what will be the output if the message is sent successfully?

producer = KafkaProducer(bootstrap_servers='localhost:9092')
future = producer.send('my_topic', b'hello')
result = future.get(timeout=10)
print(result)

medium

A. None

B. TimeoutError

C. SyntaxError

D. RecordMetadata(topic='my_topic', partition=0, offset=0)

Solution

1. Step 1: Understand what producer.send returns

   It returns a Future object that resolves to RecordMetadata on success.

2. Step 2: Calling future.get(timeout=10) waits for send result

   If successful, it returns metadata including topic, partition, and offset.

3. Final Answer:

   RecordMetadata(topic='my_topic', partition=0, offset=0) -> Option D

4. Quick Check:

   Send success returns RecordMetadata = RecordMetadata(topic='my_topic', partition=0, offset=0) [OK]

Hint: Send returns metadata object on success [OK]

Common Mistakes:

• Expecting None as send returns a Future
• Confusing timeout error with normal output
• Thinking syntax error occurs here

4. Identify the error in this Kafka SDK consumer code snippet:

consumer = KafkaConsumer('my_topic', bootstrap_servers='localhost:9092')
for message in consumer:
    print(message.value.decode('utf-8'))
consumer.close()

medium

A. Incorrect method to decode message value

B. Topic name should be a list, not a string

C. Consumer.close() should be called before the loop

D. Missing group_id parameter in consumer initialization

Solution

1. Step 1: Check KafkaConsumer topic parameter type

   The KafkaConsumer expects a list of topics, not a single string.

2. Step 2: Identify the correct topic argument format

   Passing 'my_topic' as a string causes an error; it should be ['my_topic'].

3. Final Answer:

   Topic name should be a list, not a string -> Option B

4. Quick Check:

   Topic parameter must be list = Topic name should be a list, not a string [OK]

Hint: Pass topics as list, not string [OK]

Common Mistakes:

• Omitting group_id is allowed but not error here
• Decoding message value with decode('utf-8') is correct
• Calling close() after loop is correct

5. How does using a Kafka SDK help an application stay reliable when Kafka updates its protocol or features?

hard

A. SDKs abstract Kafka protocol details, so apps need fewer changes when Kafka updates

B. SDKs automatically update your application code without developer input

C. SDKs prevent any Kafka server downtime

D. SDKs replace Kafka brokers with cloud services

Solution

1. Step 1: Understand SDK role in protocol abstraction

   SDKs hide complex Kafka protocol details behind simple interfaces.

2. Step 2: Recognize how abstraction aids reliability

   When Kafka updates, SDKs update internally, so apps need fewer or no changes.

3. Final Answer:

   SDKs abstract Kafka protocol details, so apps need fewer changes when Kafka updates -> Option A

4. Quick Check:

   Abstraction reduces app changes = SDKs abstract Kafka protocol details, so apps need fewer changes when Kafka updates [OK]

Hint: SDKs hide Kafka changes from your app [OK]

Common Mistakes:

• Thinking SDKs auto-update app code
• Believing SDKs prevent server downtime
• Confusing SDKs with cloud Kafka replacements