Choosing a State Management Approach — Concept Check
Questions on Choosing a State Management Approach. Most applications need far less global state than they install. Separate server data from client state first, and the remaining global state is usually small enough for a light store.
Questions in this quiz
7 questions on Choosing a State Management Approach — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A developer is building a new application and needs to manage the state of a shopping cart. Which approach should they consider first?
- AUse useSearchParams for URL state
- BUse Redux for structured state management
- CUse useState for local UI state
- DUse Zustand for a light store
2.Your team is experiencing slow performance due to frequent re-renders. What could be the cause?
- AUsing Zustand with selectors
- BUsing context for frequently-changing state
- CUsing useState for global state
- DUsing URL state for local UI interactions
3.Which state management approach is suitable for managing server data that changes independently?
- ARedux
- BZustand
- CuseState
- DTanStack Query
4.A developer wants to ensure the state persists across route changes and can be updated from anywhere. What signal indicates the need for a store?
- AState is only used in a single component
- BState is static and rarely changes
- CState must survive route changes
- DState is local to a component
5.In a large codebase, why might Redux still be used despite newer alternatives?
- ARedux is the only option for managing URL state
- BRedux is required for caching API responses
- CRedux is suitable for complex cross-cutting state
- DRedux is less verbose than Zustand
6.A developer is deciding between context and a store for global client state. What is a key advantage of using a store like Zustand?
- AStores automatically manage server data
- BSelectors prevent unnecessary re-renders
- CStores are easier to set up than context
- DStores are always faster than context
7.Which state should be managed by useSearchParams?
- AGlobal client state like theme
- BServer state like fetched data
- CURL state like filters and search
- DLocal UI state like dropdowns