Salesforce's official restriction-of-processing guidance directly addresses this scenario. When an organization no longer needs a person's data but must preserve it because the person is involved in a legal proceeding, Salesforce recommends exporting the data for retention and then deleting the person's data from Salesforce . This preserves the required historical evidence while preventing normal Salesforce processing of the retained information.
This distinction is important. Merely making Salesforce records invisible to ordinary users does not necessarily stop automated processing, integrations, background services, reporting, analytics, or administrative access. Therefore, option C does not provide the same level of processing restriction.
Salesforce provides the same guidance for constituent-oriented scenarios: if a constituent no longer engages with an organization but requests preservation because of potential legal proceedings while also requesting that processing stop, export the data and delete the Salesforce records.
Modern implementations with Privacy Center can also use Privacy Hold for defined legal-retention policies, but that is an additional licensed capability and isn't an option in this question.
Verified correction: the Set 2 screenshot marks C; official Salesforce restriction-of-processing documentation supports D .
Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – data privacy; restriction of processing; retention; legal proceedings; data export and deletion.
================
