Scenario-Based · Section 26
Scenarios: Concurrent Features & Suspense
11 questions. Practical scenarios for useTransition, useDeferredValue, Suspense boundaries, lazy loading and error recovery in React 18/19 apps.
Concurrent features and Suspense are where senior React interviews get practical: how do you keep typing smooth over huge datasets, and how do you stop one slow API from blanking the whole page? These scenarios cover prioritizing updates, placing boundaries, and designing loading and error states users actually like.
01A search input filters 50,000 records. How would you keep typing responsive?02A dashboard performs expensive filtering. How would you prioritize updates?03A chart takes two seconds to render. How can you keep the UI interactive?04Which updates should be wrapped inside startTransition?05When would useDeferredValue be a better choice than debouncing?06A page contains three independent API sections. How would you use Suspense?07One slow component blocks the entire page. How would Suspense help?08Where would you place Suspense boundaries in a dashboard?09A lazy-loaded component fails to load. How should the UI behave?10How can Suspense improve the perceived loading experience?11Why is a single Suspense boundary around the whole app usually not ideal?