Treat the requirement as something users will depend on daily. Custom links and detail page links give users a direct navigation point from the record they are viewing. They are appropriate when the requirement is quick access to a document, URL, or related resource from a record page. The proper configuration is A. A custom detail page link on the Contract object. 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 rejected choices solve different problems. B (Quick Action on the Account object) should be rejected because Actions improve user entry, but they are not a substitute for relationship modeling, reporting logic, or back-end automation. C (A custom detail page link on the Account object) would be fragile here because Master-detail is powerful, but it is wrong when the records need independent ownership or when the child- parent direction is reversed. D (Quick Action on the Contracts object) does not fit cleanly; Actions improve user entry, but they are not a substitute for relationship modeling, reporting logic, or back-end automation.
The configuration remains understandable for future admins because the decision is visible in metadata rather than buried in a workaround.
---