MCB Data Cloud Certification Practice Exam

How should a consultant respond to a "Request to be Forgotten" from a customer?

1. Use the Consent API to delete all customer records.

2. Add the Individual ID to a headerless file for deletion.

3. Use Data Explorer to manually remove the individual.

4. Delete all incoming data streams related to the individual.

The correct answer is: Add the Individual ID to a headerless file for deletion.

When responding to a "Request to be Forgotten" from a customer, it is crucial to follow a specific process that ensures compliance with data protection regulations while maintaining proper records of the deletion procedure. Adding the Individual ID to a headerless file for deletion is a method that allows for systematic and compliant removal of a customer's data. This approach ensures that the Individual ID is documented appropriately, facilitating future audits or verification of the deletion process. By using a headerless file, the details about the data and its context are abstracted, which can be helpful in managing privacy while still capturing the necessary identifiers for behind-the-scenes processes. This technique also supports tracking and confirms that the request has been processed without inadvertently affecting other related data unnecessarily. It ensures the specific request is honored without risking data integrity or violating data retention policies tied to other elements of the database. In contrast, other options may not align as well with best practices for handling this type of request. For instance, using the Consent API to delete all customer records could result in broader data loss than necessary. Manually removing individuals through Data Explorer might be prone to human error or be inconsistent, while deleting all incoming data streams related to the individual does not focus explicitly on compliance with the specific request to remove personal