A Structured Streaming query reads a 12-partition Kafka topic that feeds a Delta table. During traffic spikes, single micro-batches grow enormous and overwhelm the cluster. The team wants to cap how much data each micro-batch consumes and asks what controls the number of concurrent read tasks. Which configuration answers both concerns?
Reveal answer
Correct answer: Offset cap: set kafka.maxOffsetsPerTrigger to bound each micro-batch; read tasks follow the topic's partitions, raised by minPartitions
Reference: https://docs.databricks.com/aws/en/connect/streaming/kafka/
Noos Visual & Functional Recognition
The “Sphere Embrace”: how Noos embraces top contributors without a childish mascot.
In neurobiology, glial cells wrap axons in myelin sheaths to accelerate neural impulses. On Noos, as your explanations earn accelerations and enter the Wiki Synthesis, the Noos Sphere wraps your Identicon with Keplerian orbits and two quantum nodes on its shoulders.
Pure 5×5 geometric Identicon (no personal photo, zero tracking). 1px frame.
Single dashed orbit with 1 bright polar node at the apex. Highlights those who passed the exam.
Two coaxial ellipses (±35°) wrap the avatar with two lateral nodes.
The Sphere Embrace: The Noos Sphere hood wraps the top of the Identicon and rests two luminous nodes on its shoulders.
02 — The Myelin Layer · Canonical Discussion
Where the exam tries to trick you — and how those who passed solved it.
contributed to this question
No community synthesis consolidated for this question yet. Below is the verifiable official starting point — if you passed the exam, open the option dissection.
Official Answer (D): Offset cap: set kafka.maxOffsetsPerTrigger to bound each micro-batch; read tasks follow the topic's partitions, raised by minPartitions
Contribute to this Question
✦ I PASSED!Peer contributions
No public contribution yet. Be the first who passed to explain why the distractors trick candidates — your contribution builds your Orbital Sheath.