The useful clue is the business action being requested. The best answer is C. Schema Builder. The scenario is asking for Lightning page configuration, and the reason is straightforward: Lightning App Builder controls page composition, component visibility, activation, assignments, and specialized surfaces such as record pages, home pages, and utility bars. The wording points to this control because the business result must be reliable when real users work with real records.
For the stated requirement - A new app builder on the Cloud Kicks team is getting familiar with the data Model. They want to see how standard objects and custom objects relate. Which functionality should the app builder use to view these. - the selected answer handles the behavior directly. It is not just a way to make the page look cleaner or to remind users what to do. It places the responsibility in the Salesforce feature that owns the outcome. That matters in an App Builder implementation because access, automation, relationships, page rendering, reporting, and deployment each have different enforcement points.
None of the other options gives the same administrative control. A (Object Manager) does not fit cleanly; it solves a symptom of the problem rather than the Salesforce mechanism that owns the result. B (Fields & Relationships) is only a partial match because it does not provide the same direct administrative control as the selected option. D (Lightning App Builder) is not enough: A Lightning component changes the interface; it does not automatically solve security, relationship, or data-quality requirements. This is the stronger design because it respects security, data quality, user experience, and lifecycle management at the same time.
---