Question 100
A memory-intensive stateful aggregation spills on small interactive compute during peak processing. How should the team correct this issue while preserving the required data contract?
Explanation
Correct Answer
Choose appropriately sized job or serverless compute and tune workload memory needs. This is the most directly relevant remediation 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
Overlapping writers can create conflicts or duplicate side effects on shared targets. That consideration does not remove the current constraint: stateful aggregation memory demand can exceed the originally chosen executor resources.
Mutable aggregate sources are not equivalent to a never-changing append event stream. In this situation, stateful aggregation memory demand can exceed the originally chosen executor resources.
Unbounded event-time join state retains data awaiting hypothetical future matches. For the observed behavior, stateful aggregation memory demand can exceed the originally chosen executor resources.