Which statement best describes a component?

Which statement best describes a component?

• A. An event listener bound to a window
• B. A style sheet
• C. A data model for API calls
• D. A small, reusable chunk of code responsible for rendering some HTML

Answer: (D)

In UI development, a component is a small, reusable chunk of code that renders a portion of the user interface. It encapsulates its own markup (HTML) and often its own behavior, so you can reuse it across different parts of an app and compose larger interfaces by putting components together. This makes components the building blocks of UIs: you create simple pieces, and then combine them to build more complex screens. That’s why the best description is the one that highlights a small, reusable piece of code responsible for rendering some HTML. It captures the core idea: a component renders UI, is reusable, and can be composed with other components. The other options don’t fit as components because they describe things that don’t directly render UI blocks. An event listener bound to a window handles interactions but isn’t a piece of UI that renders HTML. A style sheet governs appearance, not structure or rendering. A data model for API calls handles data management, not rendering.

In UI development, a component is a small, reusable chunk of code that renders a portion of the user interface. It encapsulates its own markup (HTML) and often its own behavior, so you can reuse it across different parts of an app and compose larger interfaces by putting components together. This makes components the building blocks of UIs: you create simple pieces, and then combine them to build more complex screens.

That’s why the best description is the one that highlights a small, reusable piece of code responsible for rendering some HTML. It captures the core idea: a component renders UI, is reusable, and can be composed with other components.

The other options don’t fit as components because they describe things that don’t directly render UI blocks. An event listener bound to a window handles interactions but isn’t a piece of UI that renders HTML. A style sheet governs appearance, not structure or rendering. A data model for API calls handles data management, not rendering.