A consumer is configured with enable.auto.commit=false. What happens when close() is called on the consumer object?
Suggested Answer: B
Get Premium CCDAK Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Calling close() on consumer immediately triggers a partition rebalance as the consumer will not be available anymore.
12 comments · newest first
LO
Lonny
11 months ago
C is definitely the right answer here.
LA
Lashon
12 months ago
So, does that mean the offsets are lost if not committed?
FR
Francesco
12 months ago
Wait, I thought A was true? Why would offsets commit?
VI
Viola
12 months ago
Totally agree with C! Makes sense.
CY
Cyndy
1 year ago
C is correct, the consumer stops sending heartbeats.
NI
Nicolette
1 year ago
I practiced a similar question, and I think the consumer just stops without committing offsets, but I can't recall the exact details.
RO
Rosalia
1 year ago
I remember something about heartbeats and rebalancing, so I feel like option C might be correct.
LA
Lavera
1 year ago
I think when close() is called, it doesn't commit the offsets since enable.auto.commit is false, but I'm not entirely sure what happens next.
LA
Layla
1 year ago
I’m leaning towards option C too, but I wonder if there’s a chance it could trigger a rebalance immediately instead.
RO
Rosendo
1 year ago
Hmm, I'm a bit unsure about the details of the NSA network and the different message types. I'll need to think this through carefully.
TO
Tori
1 year ago
This is a good question to test our understanding of electronic support tools. I'll need to review my notes on the specific benefits to make sure I choose the most comprehensive answer.
FL
Floyd
1 year ago
I feel pretty confident about this one. The fake wireless network attack and the ability to view network probing information are the two biggest vulnerabilities with WZC on Windows XP. I'll select those two options.