How does Data 360 handle an individual ' s Right to Be Forgotten?
A.
Deletes the records from all data source objects, and any downstream data model objects are updated at the next scheduled ingestion
B.
Deletes the specified Individual and records from any data model object/data lake object related to the Individual
C.
Deletes the specified Individual record and its Unified Individual Link record
D.
Deletes the specified Individual and records from any data source object mapped to the Individual data model object
The Answer Is:
B
This question includes an explanation.
Explanation:
The governance lens is least privilege, purpose limitation, and honoring privacy operations against the individual profile. Deletes the specified Individual and records from any data model object/data lake object related to the Individual 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.
Data-Cloud-Consultant PDF/Engine
Printable Format
Value of Money
100% Pass Assurance
Verified Answers
Researched by Industry Experts
Based on Real Exams Scenarios
100% Real Questions
Get 65% Discount on All Products,
Use Coupon: "ac4s65"