Salesforce Certified Data 360 Consultant free question 1 / 10 · Domain 1: Solution Positioning
A retailer uses an Individual DMO, a Contact Point Email DMO that has a direct relationship to Individual through the Individual ID, and a Sales Order DMO that holds orders. Sales Order has a field for the customer's email address, but no relationship to Individual is defined. Each DMO has a DLO from a data stream mapped to it. The company sends a data deletion request for one customer through the Consent API. According to the Help article, what is deleted?
- The rows in Individual and Contact Point Email and in their mapped DLOs are deleted, and the Sales Order rows remain
- The rows in the Individual, Contact Point Email, and Sales Order DMOs are deleted, and the rows in the mapped DLOs remain
- The rows in the Individual and Contact Point Email DMOs are deleted, and the Sales Order rows and the DLO rows remain
- The rows in the Individual, Contact Point Email, and Sales Order DMOs and in their mapped DLOs are all deleted
Show the answer and explanation
Answer: A
Why this is correct
A data deletion request removes the rows of the specified person from the Individual DMO and from the DMOs that have a direct relationship to Individual through the Individual ID, such as Contact Point Address, Contact Point Email, and Contact Point Phone. It also removes the rows in the DLOs mapped to those DMOs and the data in related calculated insights. Sales Order holds personal data (an email address), but because it has no relationship to the Individual ID, it is not in scope. The Help article carries a warning that a deletion request removes only records tied to the individual's ID, and does not delete data in DMOs that have no direct relationship to Individual or that are unrelated.
Why the other options are wrong
"The rows in the Individual, Contact Point Email, and Sales Order DMOs are deleted, and the rows in the mapped DLOs remain" … Sales Order is not deleted because it has no relationship to the Individual ID. The DLO rows are deleted together with the mapped DMOs; the process does not delete DMO rows and leave the source DLO rows behind.
"The rows in the Individual and Contact Point Email DMOs are deleted, and the Sales Order rows and the DLO rows remain" … Sales Order is correctly left alone, but the DLO rows mapped to Individual and Contact Point Email are also in scope. The Help article says the request deletes the DLOs mapped to the affected DMOs and the related calculated insights.
"The rows in the Individual, Contact Point Email, and Sales Order DMOs and in their mapped DLOs are all deleted" … The DLO deletion is right, but a DMO with no relationship to the Individual ID is not deleted. The request does not search for records with the same email value; it deletes records connected through the person's ID.
Designing to avoid gaps
If you want personal data in a DMO such as Sales Order to be covered by deletion requests, define a data model relationship between that DMO's customer ID field and the Individual Id on Individual (see Impact of Data Modeling on Data Subject Rights Requests). Also remember that deleting in Data 360 does not reach other connected systems or other Salesforce clouds, so the request has to be sent to each of them separately.