Context API
interview questions.

Context makes a provider value available to descendants without passing it through each intermediate component. Consumers read the nearest matching provider.

It distributes a value through a subtree. That value can include data and update functions, but context itself is not a persistence mechanism.

Decide from update frequency, consumer count, debugging requirements, and transition complexity. Context can suit scoped configuration; Redux can suit coordinated feature state. Neither choice is universally better.

Consider render behavior and maintenance. Context consumers update when their provider value changes. Split unrelated contexts and stabilize values when useful; store selectors can narrow subscriptions for frequently changing data.

The provider component or an external store owns changing state. Context exposes its current value. Pair it with useState or useReducer when consumers need updates.

React data flow remains one-way. A provider passes values down; a consumer can invoke a supplied callback to request an update at the owner. The changed value then flows down on the next render.