You need to set up the capability to view the change history for the food...

Feature: Audit changes to its data. Table: Resident.

Food type and amount are columns on the Resident table, so Dataverse auditing must be enabled for that table and for the two relevant columns. The Audit changes to its data setting records create, update, and delete events and captures the user and time associated with audited changes. This directly supports the requirement to identify who changed the values during the preceding three months. The audit-retention policy should therefore retain records for at least that period. The Feeding table is not the correct target because the scenario explicitly states that food type and amount are stored on each Resident row. A timeline displays activities and notes but does not automatically provide field-level before-and-after history. Audit user access records access events and is not a substitute for auditing data changes. Environment-level auditing must also be enabled before table and column auditing produces history. Microsoft documents that audited changes can be retrieved with Changed By and Created On information, allowing authorized staff to determine who made each modification and when it occurred.