What can be assigned directly to a user when using the SAP Launchpad service in SAP BTP?

Question

Options

• ASpaces
• BLaunchpad roles
• CCatalogs
• DRole collections

• A
  2% (1)
• B
  2% (1)
• C
  4% (2)
• D
  92% (47)

Explanation

In SAP BTP, role collections are the authorization objects that can be assigned directly to users, groups, or identity provider attributes. Role collections bundle together individual roles, and assigning them to a user grants that user the permissions defined within - including access to Launchpad content and functionality.

Why the distractors are wrong:

• A. Spaces - Spaces are organizational units within Cloud Foundry environments, not authorization objects assigned to users in the Launchpad service.
• B. Launchpad roles - Individual roles (like Launchpad_Admin) exist, but they cannot be assigned directly to users; they must first be bundled into a role collection.
• C. Catalogs - Catalogs group apps/tiles for content management purposes and are assigned to roles, not directly to users.

Memory tip: Think of role collections as a "permission bundle." In SAP BTP identity and access management, the rule is consistent everywhere - you always assign role collections to users, never raw roles or platform constructs like spaces or catalogs. If the question asks "what goes directly to a user," the answer is always role collections.

No community discussion yet for this question.