When implementing "right to be forgotten" requests using the Data Cloud Consent API, it is crucial to understand the scope and process. Deletion requests are targeted at the unified 'Individual' profile, which represents a specific person within Data Cloud. This ensures the request is precise. Furthermore, the deletion is not a single, instantaneous event. To ensure thoroughness and prevent the reintroduction of data from connected sources, the deletion request is reprocessed at subsequent intervals (for example, at 30 and 60 days) to catch any in-flight data and enforce suppression of the deleted individual's record. These two points are critical for setting correct expectations with the customer regarding how the privacy request is honored.

1. Salesforce Help

Document: Data Deletion for Data Cloud.

For Correct Answer C: The documentation states

"You can request to delete a record from the Individual

Unified Individual Link

and Contact Point App objects." This confirms that requests are submitted for an Individual.

For Correct Answer A: The documentation explains the reprocessing mechanism: "To ensure that all of the individual’s data is deleted

the deletion request is reprocessed twice: 30 days after the initial request and 60 days after the initial request." While the option includes "90 days

" it correctly identifies the key consideration of a multi-stage reprocessing and suppression cycle.

For Incorrect Answer B: The same document notes

"Data deletion requests are processed daily." This contradicts the "within 1 hour" claim.

For Incorrect Answer D: The document clarifies the scope: "Data deletion requests submitted to Data Cloud apply only to data stored in Data Cloud. To delete data in other Salesforce clouds or in systems outside of Salesforce

you must submit separate requests."