The safest reading of the scenario is practical, not theoretical. Use D. For use on the utility bar. Lightning App Builder controls page composition, component visibility, activation, assignments, and specialized surfaces such as record pages, home pages, and utility bars.
The selected answer is stronger because it meets both the functional requirement and the maintainability requirement. In a Salesforce implementation, a solution that only works for one user, one page, or one data sample is not good enough. The correct feature has to behave consistently across the intended profiles, record types, apps, and devices that are part of the design.
The alternatives are plausible only if the requirement is read too narrowly. A (For use in App Manager.) should be rejected because it works at the wrong scope for the object, field, page, automation, or deployment condition in the stem. B (For use in Lightning App Builder.) would be fragile here because A Lightning component changes the interface; it does not automatically solve security, relationship, or data-quality requirements. C (For use on record pages.) does not fit cleanly; it solves a symptom of the problem rather than the Salesforce mechanism that owns the result. A complete implementation should also check page assignment, field access, record ownership, and mobile behavior where those factors apply.
---