What is the purpose of system governance in Adobe Target?

Question

Options

• ATo restrict the number of mboxes on a page
• BTo maintain control over activity workflows and user access
• CTo automate reporting and analytics integration
• DTo define customer segments based on usage history

• A
  15% (6)
• B
  74% (29)
• C
  8% (3)
• D
  3% (1)

Explanation

System governance in Adobe Target centers on maintaining organizational control - specifically managing who can do what (user access/permissions) and how activities move through approval and publication workflows. This makes B correct: governance is fundamentally about oversight, accountability, and controlled access to prevent unauthorized changes in a production environment.

Why the distractors are wrong:

• A is incorrect because mbox limits are a technical implementation detail, not a governance concern.
• C is incorrect because reporting and analytics integration is a feature/configuration task, not a governance function.
• D is incorrect because customer segmentation based on usage history describes audience building or Recommendations logic - unrelated to governance.

Memory tip: Think of "governance" as the guardrails of an organization - it's always about who has power and how decisions get approved, not about technical features or data outputs. If an answer choice describes control, permissions, or workflows, that's your governance signal.

No community discussion yet for this question.