Question Bank · Section 07
Internals: Fiber & Reconciliation
15 questions. How React's Fiber architecture represents work, diffs trees, uses keys, and splits updates into render and commit phases.
Senior React interviews almost always probe what happens between setState and the screen changing. This section covers Fiber nodes, the current/workInProgress trees, the reconciliation heuristics, keys, and how the render and commit phases let React pause, prioritize and resume work.
01What is React Fiber?02Why did React introduce the Fiber architecture?03Explain React's reconciliation algorithm.04How does React decide which components need to re-render?05What is the difference between reconciliation and rendering?06How does React compare two Virtual DOM trees?07What is the role of keys during reconciliation?08What happens if keys are unstable?09Why shouldn't we use array indexes as keys?10What is the Render phase and Commit phase?11Can React pause rendering? How?12What is interruptible rendering?13How does Fiber improve user experience?14How does React schedule work internally?15What are Fiber nodes?