The right answer avoids a brittle workaround. The best answer is A. Account Object. 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 - An app builder is tasked with adding key performance indicators on client Pages.
They want to see a summary of the number of open Opportunities and the Number of won Opportunities for each Account. Where should the app. - 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. B (Lightning Object Creator) is only a partial match because A Lightning component changes the interface; it does not automatically solve security, relationship, or data-quality requirements. C (Opportunity Object) misses the mark because it addresses a neighboring feature area rather than the exact behavior requested. 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.
---