A React component should use 'props' to store information that can be changed, but can only be changed by a different component.

A React component should use 'props' to store information that can be changed, but can only be changed by a different component.

• A. True
• B. Props can be changed by the component itself
• C. Props should be stored in state
• D. Props are read-only and cannot be changed by the child component

Answer: (D)

Props are the inputs a component receives from its parent, and they are read-only for the child. This means a child cannot directly modify the props it was given; instead, data flows one way—from parent to child. If a child needs to trigger a change, it calls a function passed down via props (an event handler), and the parent updates its own state accordingly. The updated state in the parent then passes new props down to the child, causing a re-render with the latest values. If you want data that the component itself can change, you’d store that in its internal state (using useState or this.setState) rather than in props.

Props are the inputs a component receives from its parent, and they are read-only for the child. This means a child cannot directly modify the props it was given; instead, data flows one way—from parent to child. If a child needs to trigger a change, it calls a function passed down via props (an event handler), and the parent updates its own state accordingly. The updated state in the parent then passes new props down to the child, causing a re-render with the latest values. If you want data that the component itself can change, you’d store that in its internal state (using useState or this.setState) rather than in props.