The important question is which feature owns the result. In this case, The proper configuration is C. Lightning App Builder; D. Lightning components in Setup. Lightning App Builder controls page composition, component visibility, activation, assignments, and specialized surfaces such as record pages, home pages, and utility bars.
The stem gives enough detail to reject surface-level fixes. Salesforce should be configured so the behavior is enforced or rendered by the feature designed for it. When the requirement touches User Interface, the builder should avoid crossing into a different layer unless there is a real platform limitation. The selected answer follows that discipline and creates the least surprising result for admins and users.
The rejected choices solve different problems. A (Visualforce components in Setup) is less defensible because A Lightning component changes the interface; it does not automatically solve security, relationship, or data- quality requirements. B (Salesforce Optimizer App) should be rejected because it works at the wrong scope for the object, field, page, automation, or deployment condition in the stem. The configuration remains understandable for future admins because the decision is visible in metadata rather than buried in a workaround.
For Lightning pages, activation and assignment determine who sees the page. Component visibility then controls whether a specific component appears for a given condition.
---