Which element is needed to build a Web application that authenticates Webex users and can post messages under the user's identity?

Question

Options

• AOAuth integration configured with the `messages_write' scope
• Bbot access token
• CGuest Issuer application
• Dself-signed certificate that is created from a public authority

• A
  75% (39)
• B
  8% (4)
• C
  2% (1)
• D
  15% (8)

Explanation

OAuth integration with the messages:write scope is correct because OAuth is the standard protocol for delegated authorization - it allows a web application to act on behalf of a specific Webex user, so messages appear under that user's identity rather than a service account. The messages:write scope explicitly grants the app permission to post messages through the Webex API.

Why the distractors are wrong:

• B (bot access token): A bot token authenticates the bot itself, not a human user - messages would post from the bot's identity, not the user's.
• C (Guest Issuer application): Guest Issuer creates temporary/anonymous guest identities (typically for meeting access), not for authenticating existing Webex users in a web app.
• D (self-signed certificate from a public authority): This option is self-contradictory (self-signed ≠ public authority), and certificates handle transport-layer security (TLS/mTLS), not user identity authorization for API calls.

Memory tip: Think of OAuth as "On behalf of" - whenever a question asks about acting as or under the identity of a real user, OAuth with the appropriate scope is the answer. If it said "post as a bot," you'd pick the bot token instead.

No community discussion yet for this question.