Confluent Cloud overview in Kafka - Commands & Configuration

Introduction

Managing Apache Kafka infrastructure can be complex and time-consuming. Confluent Cloud is a fully managed Kafka service that handles the setup, scaling, and maintenance for you, so you can focus on building your applications.

When you want to stream data between applications without managing servers or clusters.

When you need a reliable, scalable messaging system but lack Kafka operational expertise.

When you want to quickly prototype or deploy event-driven applications without setup delays.

When you want automatic backups, monitoring, and security without manual configuration.

When you need Kafka that integrates easily with cloud services and scales on demand.

Commands

Log in to Confluent Cloud CLI and save your credentials for future commands.

Terminal

confluent login --save

Expected Output

Logged in successfully.

List all Kafka clusters available in your Confluent Cloud account to choose one for your work.

Terminal

confluent kafka cluster list

Expected Output

ID                                   NAME           TYPE       CLOUD    REGION

lkc-123abcde456fgh78                example-cluster  Basic      aws      us-east-1

Create a new Kafka topic named 'example-topic' in the specified cluster to start sending and receiving messages.

Terminal

confluent kafka topic create example-topic --cluster lkc-123abcde456fgh78

Expected Output

Created topic "example-topic" on cluster "lkc-123abcde456fgh78".

→

--cluster - Specifies the Kafka cluster where the topic will be created.

List all topics in the specified Kafka cluster to verify the topic creation.

Terminal

confluent kafka topic list --cluster lkc-123abcde456fgh78

Expected Output

Name           Partitions   Replicas

example-topic  1            3

→

--cluster - Specifies the Kafka cluster to list topics from.

Key Concept

If you remember nothing else, remember: Confluent Cloud lets you use Kafka without managing servers, making streaming data easier and faster.

Common Mistakes

Trying to create a topic without specifying the cluster ID.

The CLI needs to know which Kafka cluster to create the topic in; without it, the command fails.

Always include the --cluster flag with the correct cluster ID when creating or managing topics.

Not logging in before running Confluent Cloud commands.

Commands require authentication; without login, they will not work and show errors.

Run 'confluent login --save' first to authenticate your CLI session.

Summary

Log in to Confluent Cloud CLI to authenticate your session.

List available Kafka clusters to select where to work.

Create Kafka topics in your chosen cluster to organize your data streams.

Verify topic creation by listing topics in the cluster.

Practice

1. What is the main purpose of Confluent Cloud in Kafka usage?

easy

A. It provides a managed Kafka service for easy data streaming.

B. It is a tool to write SQL queries on Kafka topics.

C. It is a database for storing Kafka messages permanently.

D. It is a programming language for Kafka applications.

Solution

1. Step 1: Understand Confluent Cloud's role

   Confluent Cloud is described as a managed Kafka service that simplifies data streaming.

2. Step 2: Compare options with this role

   Only It provides a managed Kafka service for easy data streaming. matches this description; others describe unrelated tools or concepts.

3. Final Answer:

   It provides a managed Kafka service for easy data streaming. -> Option A

4. Quick Check:

   Managed Kafka service = It provides a managed Kafka service for easy data streaming. [OK]

Hint: Remember: Confluent Cloud manages Kafka for you [OK]

Common Mistakes:

• Confusing Confluent Cloud with a database
• Thinking it is a programming language
• Assuming it runs SQL queries directly

2. Which of the following is the correct way to describe a Kafka topic in Confluent Cloud?

easy

A. A topic is a user account in Confluent Cloud.

B. A topic is a programming function to send messages.

C. A topic is a type of database index.

D. A topic is a place where messages are stored and organized.

Solution

1. Step 1: Define Kafka topic concept

   A Kafka topic is a category or feed name to which messages are published and stored.

2. Step 2: Match definition to options

   A topic is a place where messages are stored and organized. correctly states that a topic stores and organizes messages; others are incorrect.

3. Final Answer:

   A topic is a place where messages are stored and organized. -> Option D

4. Quick Check:

   Topic = message storage location [OK]

Hint: Topics hold messages, not functions or users [OK]

Common Mistakes:

• Confusing topics with user accounts
• Thinking topics are functions or indexes
• Mixing topics with database concepts

3. Given the following code snippet for producing a message in Confluent Cloud Kafka client:

producer.produce(topic='orders', value='order123')

What happens when this code runs successfully?

medium

A. The 'orders' topic is deleted.

B. The message 'order123' is sent to the 'orders' topic.

C. The producer client shuts down.

D. An error occurs because 'value' must be a number.

Solution

1. Step 1: Understand produce method

   The produce method sends a message to a specified topic with the given value.

2. Step 2: Analyze the code behavior

   Here, 'order123' is sent as a message to the 'orders' topic; no deletion or shutdown occurs.

3. Final Answer:

   The message 'order123' is sent to the 'orders' topic. -> Option B

4. Quick Check:

   Produce sends message to topic [OK]

Hint: Produce sends data to topic, no deletion or shutdown [OK]

Common Mistakes:

• Thinking produce deletes topics
• Assuming value must be numeric
• Confusing produce with client shutdown

4. You wrote this code to consume messages from a Confluent Cloud topic:

consumer.subscribe(['payments'])
message = consumer.poll(1.0)
print(message.value())

But you get an error: 'NoneType' object has no attribute 'value'. What is the likely cause?

medium

A. The print statement syntax is incorrect.

B. The topic 'payments' does not exist.

C. No messages were available to consume during poll timeout.

D. The consumer client was not connected to Confluent Cloud.

Solution

1. Step 1: Understand poll method behavior

   poll returns None if no messages are received within the timeout period.

2. Step 2: Analyze error cause

   Calling value() on None causes the error; this means no messages arrived during poll.

3. Final Answer:

   No messages were available to consume during poll timeout. -> Option C

4. Quick Check:

   poll returns None if no messages [OK]

Hint: poll returns None if no messages, check before accessing [OK]

Common Mistakes:

• Assuming topic absence causes this error
• Blaming connection issues without checking poll
• Thinking print syntax is wrong

5. You want to create a Confluent Cloud Kafka topic that automatically deletes messages after 7 days. Which configuration should you apply when creating the topic?

hard

A. Set the topic's retention.ms to 604800000 (7 days in milliseconds).

B. Set the topic's cleanup.policy to 'compact'.

C. Set the topic's max.message.bytes to 7.

D. Set the topic's partitions to 7.

Solution

1. Step 1: Understand retention.ms setting

   retention.ms controls how long messages are kept before deletion, in milliseconds.

2. Step 2: Calculate 7 days in milliseconds

   7 days x 24 hours x 60 minutes x 60 seconds x 1000 = 604800000 ms.

3. Step 3: Match configuration to requirement

   Setting retention.ms to 604800000 ensures messages delete after 7 days; other options do not control retention time.

4. Final Answer:

   Set the topic's retention.ms to 604800000 (7 days in milliseconds). -> Option A

5. Quick Check:

   retention.ms = 7 days in ms [OK]

Hint: Use retention.ms for message lifetime in ms [OK]

Common Mistakes:

• Confusing cleanup.policy with retention time
• Setting max.message.bytes instead of retention
• Changing partitions unrelated to retention