AD0-E605 · Question #31
A company has a policy to restrict access of marketers from viewing PII fields within the Real- Time CDP. The data architect plans to use the attribute-based access control feature to fulfill this req
The correct answer is C. Labels are applied at a field within a field group and inherited by the schemas that use that field. In Adobe Experience Platform (AEP), schemas are composed of reusable field groups - shared building blocks that can be included in multiple schemas. When a data usage label is applied to a specific field inside a field group, every schema that includes that field group automatica
Question
A company has a policy to restrict access of marketers from viewing PII fields within the Real- Time CDP. The data architect plans to use the attribute-based access control feature to fulfill this requirement. The data architect notices that when they apply labels in one schema, other schemas inherit those same labels. Why is this happening?
Options
- ALabels are applied at a field level and inherited by the schemas that use that field.
- BLabels are applied at a field group and inherited by the schemas that use that field group.
- CLabels are applied at a field within a field group and inherited by the schemas that use that field
- DLabels are applied to datasets, and all schemas linked to those datasets inherit the labels.
How the community answered
(55 responses)- A13% (7)
- B9% (5)
- C75% (41)
- D4% (2)
Explanation
In Adobe Experience Platform (AEP), schemas are composed of reusable field groups - shared building blocks that can be included in multiple schemas. When a data usage label is applied to a specific field inside a field group, every schema that includes that field group automatically inherits the label on that field, which explains the behavior the data architect observed.
Why the distractors are wrong:
- A is misleading because fields don't exist independently in XDM - they live inside field groups. Saying "field level" without the field group context misrepresents where the label actually lives.
- B is close but wrong in scope - labels are not applied to the entire field group, but to a specific field within it. The distinction matters because you can label some fields (e.g., email) without labeling all fields in a group.
- D reverses the inheritance direction - datasets inherit labels from schemas/field groups, not the other way around. Applying labels at the dataset level is a separate mechanism (data governance labels on datasets), not ABAC schema-level control.
Memory tip: Think of a field group as a shared cookie cutter used across multiple schema "cookies." If you stamp a label onto a slot in that cutter, every cookie made with it comes out with that stamp - you only label once, but all schemas using that field group are automatically covered.
Topics
Community Discussion
No community discussion yet for this question.