The platform gives a native tool for this situation. Use A. Data loss may occur when changing custom field types.; D. Field History Tracking records value changes of 255 characters or less. The scenario is asking for platform configuration, and the reason is straightforward: The Platform App Builder role is to choose the standard Salesforce capability that owns the behavior: data structure, access, automation, user experience, reporting, or deployment. 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) is expanding into subsidized housing by partnering with local government entities. DR uses Sales Cloud and has Enabled field history tracking on the Opportunity object. Due to increased. - 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.
The other choices would leave a gap in the implementation. B (Audit Trail is available through REST API extracts.) is not enough: it would require extra assumptions that the scenario does not support. C (Rich text field values of all lengths are displayed fully in reports.) handles a different concern; Reporting configuration helps analysis, but it does not enforce the requested record behavior. In a real org, the builder should include negative testing as well, proving that the rule does not fire or display outside the intended conditions.
---