What are scopes in the context of SAP BTP XSUAA?

Question

Options

• ACollections of user credentials
• BValues that express authorizations or access rights
• CSAP BTP subaccounts
• DEntities that aggregate technical roles

• B
  90% (19)
• C
  5% (1)
• D
  5% (1)

Explanation

In SAP BTP's XSUAA (Extended Services for User Account and Authentication), scopes are atomic units of authorization - they represent specific access rights or permissions (e.g., read, write, admin) that can be granted to users or applications, making B correct.

Why the distractors are wrong:

• A (user credentials) - Scopes have nothing to do with storing credentials like passwords; that's handled by the identity provider.
• C (subaccounts) - Subaccounts are BTP organizational units for resource isolation, a completely separate concept.
• D (entities that aggregate technical roles) - This describes role collections, not scopes. Scopes are the granular building blocks inside roles; role collections aggregate roles, not the other way around.

Memory tip: Think of the OAuth 2.0 analogy - scopes are the same concept as OAuth scopes ("what is this token allowed to do?"). In BTP, the hierarchy flows upward: Scopes → Roles → Role Collections → Users.

No community discussion yet for this question.