The correct answer is the one that enforces the intended result. Choose C. Validation Role. In Salesforce terms, this is a Lightning page configuration issue. Lightning App Builder controls page composition, component visibility, activation, assignments, and specialized surfaces such as record pages, home pages, and utility bars.
The selected configuration is the professional answer because it is native, declarative, and placed at the right scope. If the requirement later expands, another administrator can inspect the same metadata area and understand how the behavior is being produced. That is far better than a solution that depends on hidden assumptions or user training.
The other options fall short for clear platform reasons. A (Record Type) is not enough: it would require extra assumptions that the scenario does not support. B (Page Layout) handles a different concern; Page layouts affect presentation; they do not grant the underlying object or field capability by themselves. D (Activity History) should be rejected because it works at the wrong scope for the object, field, page, automation, or deployment condition in the stem. Before release, test the configuration with the affected profile and realistic records, not only with a system administrator account.
For Lightning pages, activation and assignment determine who sees the page. Component visibility then controls whether a specific component appears for a given condition.
---