What does a Provider do in the Context API?

What does a Provider do in the Context API?

• A. The Provider creates a new DOM node for rendering.
• B. The Provider supplies a value to the consuming components within its subtree.
• C. The Provider renders a component multiple times for each consumer.
• D. The Provider forces all consumers to re-render on every change.

Answer: (B)

In the Context API, the Provider supplies a value to the consuming components within its subtree. You wrap part of your UI with the Provider and pass data via the value prop. Any components inside can access that value using useContext or a Context.Consumer, allowing them to render based on shared data without prop drilling. The Provider itself isn’t creating DOM nodes or rendering multiple copies per consumer. When the value changes, subscribed consumers can re-render, but only those that depend on that context and receive the updated value. You can also nest Providers to scope different values to different parts of the tree.

In the Context API, the Provider supplies a value to the consuming components within its subtree. You wrap part of your UI with the Provider and pass data via the value prop. Any components inside can access that value using useContext or a Context.Consumer, allowing them to render based on shared data without prop drilling. The Provider itself isn’t creating DOM nodes or rendering multiple copies per consumer. When the value changes, subscribed consumers can re-render, but only those that depend on that context and receive the updated value. You can also nest Providers to scope different values to different parts of the tree.