Why cloud-native deployment matters in Kafka - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use cloud-native deployment for Kafka?

Which of the following is the main advantage of deploying Kafka in a cloud-native environment?

A It disables Kafka's ability to handle large data streams.

B It makes Kafka run only on physical servers, improving performance.

C It allows Kafka to automatically scale and recover from failures without manual intervention.

D It requires Kafka to be installed on each client machine separately.

💡 Hint

Think about how cloud-native systems handle resources and failures.

Cloud-native deployment enables Kafka to scale up or down automatically and recover quickly from failures, making it more reliable and efficient.

❓ Predict Output

intermediate

Kafka topic creation in cloud-native setup

What will be the output of this Kafka CLI command when run in a cloud-native environment with auto topic creation enabled?

Kafka

kafka-topics.sh --bootstrap-server localhost:9092 --create --topic test-topic --partitions 3 --replication-factor 2

A Error: Topic test-topic already exists

B Created topic test-topic with 3 partitions and replication factor 2

C Error: Replication factor cannot be greater than number of brokers

D No output, command silently succeeds

💡 Hint

Assume the cluster has enough brokers and auto topic creation is enabled.

The command creates the topic with specified partitions and replication factor, so it outputs confirmation.

🔧 Debug

advanced

Troubleshooting Kafka pod restart in cloud-native deployment

A Kafka pod in a Kubernetes cluster keeps restarting. Which of the following is the most likely cause?

A Kafka topics are not created before starting the pod.

B Kafka does not support running in containers.

C The pod is missing a required environment variable for Kafka's configuration.

D The pod's resource limits are too low, causing it to be killed by the system.

💡 Hint

Consider what happens when a pod uses more memory or CPU than allowed.

If resource limits are too low, the pod can be killed and restarted repeatedly by Kubernetes.

📝 Syntax

advanced

Identify the correct Kafka consumer configuration in cloud-native YAML

Which YAML snippet correctly configures a Kafka consumer group in a cloud-native deployment?

A

consumer:
  group.id: my-group
  bootstrap.servers: kafka:9092
  auto.offset.reset: earliest

B

consumer:
  groupId: my-group
  bootstrapServers: kafka:9092
  autoOffsetReset: earliest

C

consumer:
  group-id: my-group
  bootstrap-servers: kafka:9092
  auto-offset-reset: earliest

D

consumer:
  group id: my-group
  bootstrap servers: kafka:9092
  auto offset reset: earliest

💡 Hint

Kafka configuration keys use dots and lowercase letters.

Kafka consumer configs use dot notation like 'group.id' and 'bootstrap.servers'.

🚀 Application

expert

Designing a resilient Kafka deployment in cloud-native environment

You want to deploy Kafka in a cloud-native environment to ensure high availability and fault tolerance. Which design choice best supports this goal?

A Deploy Kafka brokers across multiple availability zones with replication factor set to 3.

B Deploy all Kafka brokers in a single availability zone with replication factor set to 1.

C Use a single Kafka broker with local storage for faster access.

D Disable replication and rely on client-side retries only.

💡 Hint

Think about how to avoid data loss and downtime if one zone fails.

Deploying brokers across zones with replication factor 3 ensures data is copied and available even if one zone fails.