Bird
Raised Fist0

In a distributed Kafka Connect cluster, a connector configuration is updated but the changes do not apply. What is a common cause?

medium📝 Debug Q7 of Q15
Kafka - Connect
In a distributed Kafka Connect cluster, a connector configuration is updated but the changes do not apply. What is a common cause?
AKafka brokers are down
BThe connector configuration file is missing
CThe worker nodes have different Kafka versions
DThe connector was not restarted or reconfigured properly
Step-by-Step Solution
Solution:
  1. Step 1: Understand connector config update process

    In distributed mode, connector configs must be updated via REST API or reconfigured to apply changes.
  2. Step 2: Identify why changes might not apply

    If the connector is not restarted or updated properly, changes won't take effect.
  3. Final Answer:

    The connector was not restarted or reconfigured properly -> Option D
  4. Quick Check:

    Config update requires proper restart or reconfiguration [OK]
Quick Trick: Update connector configs via REST and restart if needed [OK]
Common Mistakes:
MISTAKES
  • Blaming Kafka brokers for connector config issues
  • Assuming version mismatch causes config update failure
  • Expecting config file changes to auto-apply

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes