A data engineer is working on defining a data usage policy via automatic enforcement and has configured dataset labels C1 and C2 to enforce the restriction. The data engineer has set up the marketing

Question

Options

• AInclude the labels C1 and C2 in separate audiences upon activation
• BInclude the labels C1 and C2 in the same audience upon activation
• CExclude the labels C1 and C2 from any audience upon activation
• DAssign labels C1 and C2 to the schema rather than to the dataset during activation

• A
  5% (1)
• B
  75% (15)
• C
  15% (3)
• D
  5% (1)

Explanation

Option B is correct because Adobe Experience Platform's automatic data governance enforcement evaluates the combined set of labels present within a single audience at activation time - if both C1 and C2 are required to trigger the policy violation, they must coexist in the same audience for the enforcement engine to detect the conflict and block or warn appropriately.

Option A is wrong because placing C1 and C2 in separate audiences means each audience is evaluated in isolation; since neither audience contains both labels, the policy condition is never fully met and no violation fires. Option C is wrong because excluding the labels from audiences entirely removes the signal the enforcement engine relies on - enforcement only works when labeled data is actually present. Option D is wrong because the problem is not label placement (dataset vs. schema) but rather that the labels must appear together in the same activation context; AEP supports labels at both levels, and shifting them to the schema doesn't resolve the co-occurrence requirement.

Memory tip: Think of C1 + C2 as two halves of a trigger - the policy "alarm" only sounds when both halves are wired into the same circuit (audience). Split the wires and the alarm stays silent.

No community discussion yet for this question.