The uploaded study guide identifies B. Only the body, footer, and header helper components can be styled using styling hooks as the correct answer.
The item tests an implementation constraint that matters when a UX Designer is attempting to align a Lightning modal with organizational branding. The guide distinguishes between the primary modal framework and its associated helper components.
According to the answer key, the relevant styling-hook support applies to the body, footer, and header helper components, rather than to the primary Lightning Modal component as described in option A.
Option C is too broad because the study guide does identify supported styling-hook usage within the modal's helper-component structure.
The UX implication is that brand requirements must be evaluated against the styling capabilities Salesforce actually exposes. A designer should not assume that every visual property of every base component can be overridden freely. Design-system components deliberately constrain customization so that accessibility, structure, and platform consistency can be maintained.
Therefore, when preparing specifications for a custom modal experience, the designer must account for the specific styling surfaces supported by the Lightning modal architecture rather than designing treatments that cannot be implemented through the available hooks.
Study Guide reference/topics: Lightning Modal, styling hooks, LWC, branding constraints, SLDS.
==================================
