Auto-scaling strategies in Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the minimum number of Kafka partitions to 3.

Kafka

partitions = [1]

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

A5

B3

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Setting partitions to 0 disables the topic.

Using 1 partition limits scaling.

The minimum number of partitions is set to 3 to allow auto-scaling.

2fill in blank

medium

Complete the code to increase partitions dynamically using the Kafka admin client.

Kafka

admin_client.create_partitions(topic='my_topic', new_total_partitions=[1])

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

A1

B2

C6

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Setting partitions less than current causes errors.

Using 0 partitions is invalid.

Increasing partitions to 6 allows more parallelism for scaling.

3fill in blank

hard

Fix the error in the code to correctly configure auto-scaling based on lag.

Kafka

if consumer_lag > [1]:
    scale_up()

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

A'high_lag'

Bconsumer_lag

C0

D1000

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a number for comparison.

Comparing lag to itself causes no scaling.

The lag threshold is set to 1000 messages to trigger scaling.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps each partition to its lag if lag is greater than 500.

Kafka

partition_lag = {partition: [1] for partition, lag in lags.items() if lag [2] 500}

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

Alag

B>

C<

Dpartition

Attempts:

3 left

💡 Hint

Common Mistakes

Using partition instead of lag as the value.

Using less than operator reverses the filter.

This comprehension selects partitions with lag greater than 500 and maps them to their lag values.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps each partition to its lag if lag is greater than 1000 and partition number is less than 10.

Kafka

filtered_lags = { [1]: [2] for [3], lag in lags.items() if lag > 1000 and [3] < 10 }

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

Apartition

Blag

Dindex

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent variable names for partition.

Mapping lag as key instead of value.

This comprehension filters partitions with lag over 1000 and partition number less than 10, mapping partition to lag.

Practice

1. What is the main purpose of auto-scaling in Kafka clusters?

easy

A. To backup data to external storage

B. To manually add brokers when needed

C. To automatically adjust resources based on workload changes

D. To encrypt messages for security

Solution

1. Step 1: Understand auto-scaling concept

   Auto-scaling means adjusting resources automatically without manual intervention.

2. Step 2: Apply to Kafka context

   Kafka auto-scaling adjusts brokers or partitions based on workload changes.

3. Final Answer:

   To automatically adjust resources based on workload changes -> Option C

4. Quick Check:

   Auto-scaling = automatic resource adjustment [OK]

Hint: Auto-scaling means automatic resource changes, not manual [OK]

Common Mistakes:

• Confusing auto-scaling with manual scaling
• Thinking auto-scaling is for data backup
• Assuming auto-scaling handles security

2. Which of the following is a correct way to trigger auto-scaling in Kafka using metrics?

easy

A. Increase partition count without checking load

B. Manually restart brokers every hour

C. Disable monitoring to save resources

D. Monitor CPU usage and add brokers when usage exceeds threshold

Solution

1. Step 1: Identify correct auto-scaling trigger

   Auto-scaling triggers on metrics like CPU usage crossing a threshold.

2. Step 2: Evaluate options

   Only Monitor CPU usage and add brokers when usage exceeds threshold uses monitoring metrics to trigger scaling automatically.

3. Final Answer:

   Monitor CPU usage and add brokers when usage exceeds threshold -> Option D

4. Quick Check:

   Auto-scale triggers = metric thresholds [OK]

Hint: Auto-scaling triggers on metrics, not manual actions [OK]

Common Mistakes:

• Confusing manual restarts with auto-scaling
• Ignoring monitoring importance
• Scaling without checking load

3. Given this pseudo-code for auto-scaling Kafka brokers:

if (cpu_usage > 80%) {
  add_broker()
} else if (cpu_usage < 30%) {
  remove_broker()
} else {
  do_nothing()
}

What happens if CPU usage is 85%?

medium

A. A broker is added

B. No change in brokers

C. A broker is removed

D. Error occurs due to syntax

Solution

1. Step 1: Check CPU usage condition

   CPU usage is 85%, which is greater than 80%.

2. Step 2: Determine action based on condition

   Since cpu_usage > 80%, the code calls add_broker() to add a broker.

3. Final Answer:

   A broker is added -> Option A

4. Quick Check:

   CPU > 80% triggers add_broker() [OK]

Hint: CPU > 80% means add broker, CPU < 30% means remove [OK]

Common Mistakes:

• Confusing add and remove actions
• Ignoring else conditions
• Assuming syntax error without cause

4. This auto-scaling script snippet has an error:

if cpu_usage > 70%:
  add_broker()
elif cpu_usage < 20%:
  remove_broker()

What is the error?

medium

A. Incorrect percentage symbol usage in condition

B. add_broker() function is undefined

C. Missing colon after if statement

D. No error, code is correct

Solution

1. Step 1: Analyze condition syntax

   Using '%' directly in conditions like 'cpu_usage > 70%' is invalid syntax in most languages.

2. Step 2: Identify correct syntax

   Percent values should be numeric (e.g., 0.7 or 70) without '%' symbol in code.

3. Final Answer:

   Incorrect percentage symbol usage in condition -> Option A

4. Quick Check:

   Conditions must use numbers, not '%' symbol [OK]

Hint: Don't use % symbol in code conditions, use numbers only [OK]

Common Mistakes:

• Assuming missing colon is the error
• Thinking functions are undefined without context
• Believing code is correct as is

5. You want to auto-scale Kafka partitions based on message lag. Which strategy best fits this goal?

hard

A. Add brokers randomly without monitoring lag

B. Increase partitions when lag exceeds threshold; decrease when lag is low

C. Scale partitions only based on CPU usage

D. Manually change partitions daily regardless of lag

Solution

1. Step 1: Understand message lag as scaling metric

   Message lag indicates how many messages are waiting to be processed, a key metric for scaling partitions.

2. Step 2: Choose strategy matching lag metric

   Increasing partitions when lag is high and decreasing when low optimizes processing capacity.

3. Final Answer:

   Increase partitions when lag exceeds threshold; decrease when lag is low -> Option B

4. Quick Check:

   Lag-based scaling = adjust partitions by lag [OK]

Hint: Scale partitions based on lag, not random or CPU only [OK]

Common Mistakes:

• Ignoring lag metric importance
• Scaling without monitoring
• Manual scaling instead of auto