Governance, Privacy, and Data Lifecycle
Labels, policies, and enforcement
Adobe data governance uses data usage labels applied to schemas/fields/datasets, marketing actions on destinations, and policies (DULE) that combine them. Enforcement happens at activation and dataset level. A frequent trap: labels on a field don't automatically block ingestion - they block use at destinations where a conflicting marketing action exists. Know the common labels (e.g., contractual, sensitive, consent-related) and that custom labels can be defined.
Consent and privacy
Consent is captured via the Consent field group and evaluated against policies. Privacy Service handles access and delete requests across datasets and the profile. Understand that delete requests remove data from the data lake and profile, but downstream destinations may retain copies - questions test this lifecycle gap.
Data lifecycle
Dataset expiration and pseudonymous data expiration manage retention. Data hygiene removes expired records. Know the difference between TTL on datasets (lake retention) and profile retention. Traps: assuming a delete request instantly purges activated data at a destination, or that expiration applies to profile without configuration.
Audit and access control
Audit logs track changes; attribute-based access control (ABAC) and role-based access restrict who sees what. Questions may describe a user unable to view a field - check ABAC labels and roles.
Rule of thumb
For governance questions, trace the chain: label → policy → marketing action → enforcement point. Missing any link means no block, and privacy deletes don't guarantee downstream erasure.
Worked example: A field labeled sensitive is exported to a destination whose marketing action conflicts with the policy. Activation is blocked. The developer must either change the destination's marketing action or obtain policy exemption - not just relabel the field.