H13-711_V3.5 · Question #274
Which statement about worker (work process), Executor (thread), and task (task) is correct?
The correct answer is A. Each Executor (thread) can run a task (task) B. Each Executor (thread) can run tasks (tasks) of different components (spout or bolt) C. Each worker can run multiple Executors (threads) D. Each worker can only run Executor (thread) for one topology. All four statements describe the layered architecture of Apache Storm's execution model, and each is independently true. Why all four are correct: In Storm, a worker is a JVM process dedicated to exactly one topology (D), and it hosts multiple executor threads (C). Each…
Question
Which statement about worker (work process), Executor (thread), and task (task) is correct?
Options
- AEach Executor (thread) can run a task (task)
- BEach Executor (thread) can run tasks (tasks) of different components (spout or bolt)
- CEach worker can run multiple Executors (threads)
- DEach worker can only run Executor (thread) for one topology
How the community answered
(49 responses)- A100% (49)
Explanation
All four statements describe the layered architecture of Apache Storm's execution model, and each is independently true.
Why all four are correct: In Storm, a worker is a JVM process dedicated to exactly one topology (D), and it hosts multiple executor threads (C). Each executor thread runs one or more tasks (A), which are the actual spout/bolt instances. Because a single worker can hold executors belonging to different spout or bolt components, executors in that worker collectively handle tasks across different component types (B) - though each individual executor is bound to one component type, a worker's executor pool spans the topology's components.
Why none are "wrong" distractors here: This is an "all of the above" question testing whether students mistakenly exclude any true statement. The common trap is thinking workers can serve multiple topologies (they cannot - D rules that out), or thinking executors can only hold one task (A clarifies they can hold many), causing students to second-guess individually correct options.
Memory tip: Think of it as a nesting doll - Topology → Worker (1 topology only) → Executors (many per worker, across components) → Tasks (many per executor). Each layer can hold multiples of the layer below it, except that a worker is locked to one topology.
Community Discussion
No community discussion yet for this question.