Universal Containers are concerned that after each release, reports and dashboards seem to roll back...

The correct selection is C. Reports and dashboards edited directly in production are being overwritten by older source-controlled versions during releases. Regularly retrieving that metadata and merging it into development branches keeps the repository current and prevents subsequent deployments from rolling back business-authored changes. From an operating perspective, production stability depends on disciplined incident handling, environment synchronization, backup/recovery, observability, and control of configuration drift. Emergency actions can be faster than normal releases, but they still require traceability and must be reconciled back into the managed development baseline. The rejected choices do not provide a sustainable operating control because they fail to preserve traceability and synchronization after the immediate incident or environment change. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (C. Ensure report metadata is exported daily and that it is merged into the developer branches before the next release.). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: Operating — production governance; environment drift; incident response; backup/recovery; post-refresh controls; hotfix synchronization.