Kafka - Schema RegistryIf a Kafka consumer expects JSON Schema but receives a Protobuf message, what is the likely outcome?AConsumer processes message as plain textBConsumer automatically converts Protobuf to JSONCConsumer ignores the message silentlyDConsumer fails to deserialize and throws an errorCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand schema mismatch impactIf consumer expects JSON Schema but gets Protobuf, it cannot parse the binary format correctly.Step 2: Identify typical consumer behaviorConsumer throws deserialization error due to incompatible formats.Final Answer:Consumer fails to deserialize and throws an error -> Option DQuick Check:Schema mismatch causes deserialization error [OK]Quick Trick: Schema mismatch causes deserialization failure [OK]Common Mistakes:MISTAKESAssuming automatic format conversionThinking consumer ignores message silentlyBelieving message is processed as text
Master "Schema Registry" in Kafka9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kafka Quizzes Kafka Connect - Why connectors integrate external systems - Quiz 11easy Kafka Connect - Transform and converter chains - Quiz 4medium Kafka Streams - GroupBy and aggregation - Quiz 7medium Kafka with Java/Python - Error handling in clients - Quiz 9hard Kafka with Java/Python - Client metrics monitoring - Quiz 6medium Message Delivery Semantics - Transactional producer - Quiz 1easy Message Delivery Semantics - At-most-once delivery - Quiz 10hard Monitoring and Operations - Consumer lag monitoring - Quiz 7medium Monitoring and Operations - Log compaction - Quiz 8hard Monitoring and Operations - Log compaction - Quiz 14medium