Kafka - ConnectIf a Kafka source connector is configured with "tasks.max" set to 2 but only one task runs, what is the most likely reason?AThe Kafka broker is down, preventing task creation.BThe connector's implementation only supports a single task regardless of configuration.CThe connector class is incorrectly specified in the configuration.DThe 'topics' property is missing from the configuration.Check Answer
Step-by-Step SolutionSolution:Step 1: Understand 'tasks.max'This property sets the maximum number of tasks but does not guarantee multiple tasks will run.Step 2: Check connector capabilitiesSome connectors only support a single task due to their design.Step 3: Rule out other causesBroker status or config errors would cause failures, not just fewer tasks.Final Answer:The connector's implementation only supports a single task regardless of configuration. -> Option BQuick Check:Connector may limit tasks despite 'tasks.max' [OK]Quick Trick: Connector implementation may limit tasks to one [OK]Common Mistakes:MISTAKESAssuming 'tasks.max' always creates that many tasksBlaming Kafka broker status for task countIgnoring connector-specific task limits
Master "Connect" in Kafka9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kafka Quizzes Kafka with Java/Python - Error handling in clients - Quiz 13medium Kafka with Java/Python - Configuration best practices - Quiz 5medium Kafka with Java/Python - Configuration best practices - Quiz 14medium Kafka with Java/Python - Error handling in clients - Quiz 8hard Kafka with Java/Python - Error handling in clients - Quiz 12easy Message Delivery Semantics - Transactional producer - Quiz 9hard Monitoring and Operations - Why monitoring prevents outages - Quiz 14medium Monitoring and Operations - Consumer lag monitoring - Quiz 5medium Schema Registry - Why schema management prevents data issues - Quiz 13medium Schema Registry - JSON Schema and Protobuf support - Quiz 7medium