Question 600
A memory-intensive stateful aggregation spills on small interactive compute during peak processing. What platform behavior caused the observed result?
Explanation
Correct Answer
Stateful aggregation memory demand can exceed the originally chosen executor resources. This is the most directly relevant technical explanation because stateful aggregation memory demand can exceed the originally chosen executor resources. A concrete acceptance check is: Peak-event replay finishes without uncontrolled spill or memory failure. To reduce recurrence: Monitor state and task-memory trends before raising data volumes.
Incorrect Answers
Mutable aggregate sources are not equivalent to a never-changing append event stream. The controlling issue in this question is that stateful aggregation memory demand can exceed the originally chosen executor resources.
Pipeline scheduling requires explicit data lineage to enforce upstream-before-downstream execution. Here the important technical distinction is that stateful aggregation memory demand can exceed the originally chosen executor resources.
Importing a source file cannot provide confidentiality for embedded production passwords. The reported failure instead depends on this fact: stateful aggregation memory demand can exceed the originally chosen executor resources.