To add functionality allowing customers to attach digital files to case records, Web-to-Case is recommended.
This feature enables customers to submit cases through a web form, including the capability to attach files, facilitating the collection of additional information that can assist in case resolution.

A record-triggered Flow can be used to automatically update or restrict future messaging access when a customer's record (for example, contact or messaging session) meets specific criteria-such as detecting abusive behavior or a flag field being set. This automation can block or flag future messaging sessions at the data level.
Option A (IP blocking) is not supported natively in Salesforce Messaging.
Option B (Omni-Flow) manages work routing, not user eligibility for channel access.
Referenced Salesforce Materials:
* Service Cloud Consultant Exam Guide - Interaction Channels Domain.
* Salesforce Help: "Automate Messaging Restrictions Using Record-Triggered Flows."
* Salesforce Spring '24 Release Notes - Messaging Controls and Automation Enhancements.

For Experience Cloud customer users, Sharing Sets are the correct mechanism to provide access to records linked to their own Contact or Account. By creating a sharing set for the Case object, UC can ensure users see only the cases where they are the associated contact-even if the cases were created internally.
Option A (sharing rule) applies to internal users, not Experience users.
Option C (Public Read/Write) violates data security and exposes all customer cases.
Referenced Salesforce Materials:
* Service Cloud Consultant Exam Guide - Service Cloud Solution Design Domain.
* Salesforce Help: "Grant Record Access to Portal Users with Sharing Sets."
* Salesforce Experience Cloud Implementation Guide - Sharing Set Configuration.

For creating a secure, branded mobile app for Experience Cloud customers, utilizing Salesforce Mobile Publisher is recommended. This tool allows for the creation of a unified mobile app compatible with both Apple and Android devices, providing a seamless experience for customers to engage with the brand, track cases, and interact with the community.

In a Case History report, Salesforce tracks field changes for any fields that have field history tracking enabled.
For each tracked field, the Old Value and New Value are recorded, providing an audit trail of how and when data changed. These two fields - Old Value and New Value - are available for viewing only and cannot be edited or updated.
This report helps service managers analyze how cases evolve over time and identify process bottlenecks or data integrity issues.
Option A is incorrect because "Data Type" is not a tracked field in history reports.
Option B is incorrect because the "User" field (who made the change) is editable in user management, not view-only within this report type.
Referenced Salesforce Materials:
* Service Cloud Consultant Exam Guide - Contact Center Analytics Domain.
* Salesforce Help: "Case History Reports and Field History Tracking Behavior."
* Salesforce Trailhead: "Track Field History for Auditing and Reporting."