Which two items are needed to give a Webex user the ability to archive all Webex Teams messages for an organization? (Choose two.)

Question

Options

• AGive the user "Read-only administrator privileges" in the Webex Control Hub.
• BCreate an Integration app with all "spark_compliance" read scopes enabled.
• CUse the Webex Meetings XML API "SetUser" to update the user's "<roSiteAdmin>" value to
• DConfigure the user as a "Compliance Officer" in the Webex Control Hub.
• ECreate a Bot app with all "webex_compliance" read scopes enabled.

• A
  78% (36)
• B
  4% (2)
• C
  7% (3)
• E
  11% (5)

Explanation

Giving a Webex user organization-wide message archiving capability requires two things from Webex Control Hub: administrative access (A) and the specific compliance role (D). Read-only administrator privileges grant the user visibility into organization-wide resources, while the Compliance Officer role is the designated Control Hub role that explicitly unlocks the ability to access, monitor, and archive all Webex Teams messages across the organization. Both are required together - the admin privilege alone doesn't grant compliance access, and the Compliance Officer role without admin rights lacks the necessary organizational scope.

Why the distractors fail:

• B is wrong because creating an Integration app with spark_compliance scopes enables programmatic API-based compliance access, not direct user archiving ability - and it's not what's needed to empower a human user.
• C is wrong because the Webex Meetings XML API SetUser/<roSiteAdmin> element pertains to Meetings site administration, which is entirely separate from Teams messaging compliance.
• E is wrong on two counts: Bot apps are not user accounts and can't fulfill a user-level compliance role, and webex_compliance is a fabricated scope - the real one is spark_compliance.

Memory tip: Think of it as a two-key lock - Control Hub holds both keys: the admin key (read-only admin) to open the door, and the compliance key (Compliance Officer role) to access the archive room. Both live in Control Hub, not in APIs or XML calls.

No community discussion yet for this question.