Exam Data-Cloud-Consultant Topic 2 Question 81 Discussion

Actual exam question for Salesforce's Data-Cloud-Consultant exam
Question #: 81
Topic #: 2
A company stores customer data in Marketing Cloud and uses the Marketing Cloud Connector to ingest data into Data 360. Where does a request for Data Deletion or Right to Be Forgotten get submitted?

Suggested Answer: B Vote an answer

The governance lens is least privilege, purpose limitation, and honoring privacy operations against the individual profile. Through Consent API supports the governance requirement because Data 360 implementations should minimize unnecessary access, avoid over-collection, and process deletion or consent requests at the profile level where Salesforce expects them. The safest design is explicit, auditable, and limited to the business purpose. The distractors fall short because they either move the problem into the wrong system, add needless duplication, ignore Data 360 object relationships, or rely on a feature built for a different lifecycle stage. In a real implementation, those choices usually create brittle pipelines, stale data, security exposure, or segments that look correct on paper but fail when activated. Thinking like an architect, the selected option places the logic where Data 360 can govern it and reuse it reliably. This is the nuance exam questions often test: the platform capability must match both the technical layer and the business timing requirement, not just sound related to data.

by adrian.armijos at Jun 08, 2026, 04:00 PM

Limited Time Offer

15%

Off

Get Premium Data-Cloud-Consultant Questions as Interactive Self Test Engine or PDF

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Nick name: Submit Cancel
adrian.armijos
2026-06-08 16:00:27
In Marketing Cloud settings
When using the Marketing Cloud Connector, data deletion and Right to Be Forgotten requests are submitted in Marketing Cloud, not in Data 360. This is because Marketing Cloud is the system of record for that data — Data 360 ingested the data from Marketing Cloud via the connector, so the deletion request must originate at the source.
The key principle here is: delete where the data lives at the source. The connector relationship means Marketing Cloud owns the data lifecycle, and a deletion request made there will propagate through to Data 360. Submitting it only in Data 360 settings or on an individual profile would not guarantee removal from the originating system, which would be insufficient for true RTBF compliance.

Here's why B (Consent API) is not the answer:
The Consent API is used to manage communication preferences and opt-outs — things like unsubscribing a contact from emails or suppressing them from future sends. It controls whether you can contact someone, not whether their data is deleted.
Right to Be Forgotten / Data Deletion is a fundamentally different request — it means permanently removing a person's data from the system, which is a more drastic and irreversible action than just suppressing communication.
In short:

Consent API → "Don't contact this person"
Data Deletion in Marketing Cloud settings → "Erase this person's data entirely"

They are separate concerns, and using the Consent API to handle a RTBF request would leave the actual stored data intact, which would not satisfy GDPR or similar privacy regulations. That's why it's not the right answer here.
upvoted 1 times
...
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
0
0
0
10