Think in terms of supportability first. Lightning App Builder controls page composition, component visibility, activation, assignments, and specialized surfaces such as record pages, home pages, and utility bars. Choose B). Validation Rule. This is the option that best matches the Salesforce responsibility being tested under User Interface.
A practical administrator would confirm the object context, the user action, and whether the result must be stored, calculated, displayed, automated, approved, or deployed. Here the selected answer is the one that acts at the correct point in that chain. It keeps the configuration declarative and avoids inventing a process around a problem that Salesforce already has a native feature to solve.
The remaining answers do not control the same Salesforce behavior. A (Page Layout) would be fragile here because Page layouts affect presentation; they do not grant the underlying object or field capability by themselves. C (Activity History) is only a partial match because it does not provide the same direct administrative control as the selected option. D (Record Type) misses the mark because it addresses a neighboring feature area rather than the exact behavior requested. The result is a cleaner app design because the behavior is handled by the feature Salesforce built for that purpose.
For Lightning pages, activation and assignment determine who sees the page. Component visibility then controls whether a specific component appears for a given condition.
---