The right answer avoids a brittle workaround. The best answer is A. Roll-up Summary. The scenario is asking for roll-up summary design, and the reason is straightforward: Roll-up summary fields calculate values from child detail records and store the result on the master. The relationship type and field type decide whether the calculation is available declaratively. The wording points to this control because the business result must be reliable when real users work with real records.
For the stated requirement - Dreamhouse Realty (DR) has many properties for sale and wants to Identify the highest value of all offer records on each Property_ record Which solution should the app builder use to meet DR ' s needs provided that there. - 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 (Summary) is only a partial match because it does not provide the same direct administrative control as the selected option. C (Text Area (Long)) misses the mark because That field type either stores the wrong kind of value or fails to support the required behavior as cleanly as the selected option. D (Multi-select Picklist) is not enough: That field type either stores the wrong kind of value or fails to support the required behavior as cleanly as the selected option. This is the stronger design because it respects security, data quality, user experience, and lifecycle management at the same time.
---