A consumer has auto.offset.reset=latest, and the topic partition currently has data for offsets going from 45 to 2311. The consumer group never committed offsets for the topic before. Where will the consumer read from?

• A.offset 2311
• B.offset 0
• C.offset 45
• D.it will crash

Comment: *

Name: *

Email: *

Verification: *

Select all that applies (select THREE)

• A.min.insync.replicas is a producer setting
• B.acks is a topic setting
• C.acks is a producer setting
• D.min.insync.replicas is a topic setting
• E.min.insync.replicas matters regardless of the values of acks
• F.min.insync.replicas only matters if acks=all

Comment: *

Name: *

Email: *

Verification: *

To enhance compression, I can increase the chances of batching by using

• A.acks=all
• B.linger.ms=20
• C.batch.size=65536
• D.max.message.size=10MB

Comment: *

Name: *

Email: *

Verification: *

We would like to be in an at-most once consuming scenario. Which offset commit strategy would you recommend?

• A.Commit the offsets on disk, after processing the data
• B.Do not commit any offsets and read from beginning
• C.Commit the offsets in Kafka, after processing the data
• D.Commit the offsets in Kafka, before processing the data

Comment: *

Name: *

Email: *

Verification: *

What's is true about Kafka brokers and clients from version 0.10.2 onwards?

• A.Clients and brokers must have the exact same version to be able to communicate
• B.A newer client can talk to a newer broker, but an older client cannot talk to a newer broker
• C.A newer client can talk to a newer broker, and an older client can talk to a newer broker
• D.A newer client can't talk to a newer broker, but an older client can talk to a newer broker

Comment: *

Name: *

Email: *

Verification: *