5 collocation exercises on state management verbs.
0 / 5 completed
1 / 5
A complex application needs a clear way to ___ state across many components.
We manage state when we organise how data is stored, updated, and shared across an app. Manage is the standard collocation, behind the whole category of "state management libraries" like Redux and Zustand. Rule, govern, and drive do not pair with state in development. Developers say "global state management," so manage state is the precise, expected collocation for handling application data flow in a frontend codebase.
2 / 5
When two siblings need the same data, you ___ the state up to their common parent.
To lift state up means to move shared state to the closest common ancestor component so siblings can access it. Lift is the exact React idiom, documented as "lifting state up" in official guides. Raise, push, and pull do not form this fixed phrase. The pattern is so common it has a dedicated name, so lift state up is the precise collocation for centralising data that multiple components must share.
3 / 5
To avoid recalculating an expensive value on every render, you can ___ it.
To memoize means to cache the result of a computation so it is reused instead of recomputed. Memoize is the precise technical term, behind React hooks like useMemo and useCallback. Memorize is the everyday word for learning by heart, and remember and recall are too general. Developers say "memoize the selector," so memoize the value is the correct collocation for caching results to prevent wasteful recalculation.
4 / 5
React will ___ multiple state updates together to avoid unnecessary renders.
To batch updates means to combine several state changes into a single render pass for efficiency. Batch is the exact term, central to "automatic batching" introduced in React 18. Group, bunch, and pile lack the precise sense of processing multiple changes as one unit. Developers discuss "batched state updates," so batch updates is the correct collocation for coalescing changes to minimise rendering work.
5 / 5
When state changes, the component will ___ to reflect the new data on screen.
To re-render means to run a component again so the UI updates after its state or props change. Re-render is the standard frontend term, as in "unnecessary re-renders hurt performance." Re-show and re-build are not used this way, and re-paint refers to a browser step, not the framework lifecycle. Developers profile "wasted re-renders," so re-render the component is the precise collocation for updating the view in response to changes.