What is a key guardrail when activating data to destinations?

Question

Options

• AData must always be batch processed before activation.
• BOnly static segments can be activated.
• CData governance policies must be enforced during activation.
• DActivation can only occur during predefined time slots.

• A
  10% (3)
• B
  3% (1)
• C
  83% (25)
• D
  3% (1)

Explanation

Data governance policies must be enforced during activation (C) because activating data to destinations means moving potentially sensitive, personal, or regulated information out of your controlled environment - at that point, governance controls (consent enforcement, data usage labels, access restrictions, privacy rules) are what prevent misuse or compliance violations downstream.

Why the distractors are wrong:

• A is wrong because activation can be streaming/real-time, not exclusively batch.
• B is wrong because dynamic/computed segments can absolutely be activated - static-only is an artificial and incorrect restriction.
• D is wrong because activation timing is driven by business logic and platform capability, not mandatory time-slot constraints.

Memory tip: Think of governance as the gatekeeper at the door - data can't leave the house (your platform) unless it has the right clearance. "Destination = data leaving control = governance must travel with it."

No community discussion yet for this question.