Think in terms of supportability first. Choose D. Accordion. 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, action regions, activity surfaces, 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 remaining answers do not control the same Salesforce behavior. A (Highlights panel) would be fragile here because it could produce an inconsistent result once different users, records, or apps are tested. B (Record detail) does not fit cleanly; Master-detail is powerful, but it is wrong when the records need independent ownership or when the child-parent direction is reversed. C (Field section) is only a partial match because it does not provide the same direct administrative control as the selected option. 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.
---