What are key elements of a governance strategy for Adobe Target? (Select two)

Question

Options

• ADefining user roles and permissions
• BConfiguring advanced mbox parameters
• CDocumenting activity workflows
• DAutomating profile updates

• A
  76% (29)
• B
  16% (6)
• D
  8% (3)

Explanation

Governance in Adobe Target is about people and process, not technical configuration. Defining user roles and permissions (A) establishes who can create, approve, and launch activities - a foundational control that prevents unauthorized changes. Documenting activity workflows (C) creates the procedural guardrails (approval chains, naming conventions, QA steps) that keep teams aligned and auditable.

Why the distractors are wrong:

• B (Advanced mbox parameters) is a technical implementation detail, not a governance concern - it controls data collection, not organizational oversight.
• D (Automating profile updates) is a personalization/data strategy task, unrelated to how an organization governs access and processes.

Memory tip: Think of governance as answering two questions - "Who can do what?" (roles/permissions) and "How does work get done?" (documented workflows). Anything about configuring or automating features belongs to implementation, not governance.

No community discussion yet for this question.