What are some of the rules for SAP-developed roles in SAP S/4HANA Cloud Public Edition? Note: There are 3 correct answers to this question.

Question

Options

• ARole maintenance reads applications from a catalog.
• BRole maintenance reads applications from role menus.
• CManual role authorizations are supported in custom catalogs.
• DAuthorization defaults define role authorizations.
• ECatalogs are assigned to role menus.

• A
  75% (39)
• B
  8% (4)
• C
  17% (9)

Explanation

In SAP S/4HANA Cloud Public Edition, SAP-developed business roles follow a strict, structured hierarchy: catalogs are the source of applications (A), catalogs are assigned to role menus which bundle them together (E), and the authorizations within those roles are governed by authorization defaults - not manual entries (D). This locked-down model ensures system integrity and simplifies upgrades in the cloud environment.

Why B is wrong: Role maintenance reads applications from catalogs, not from role menus. Role menus reference catalogs, but the catalog is the authoritative source - menus are just an organizational layer above them.

Why C is wrong: Manual role authorizations are not supported, even in custom catalogs. Authorization defaults are the mechanism for defining what access a role grants. This restriction is intentional in the Public Edition to prevent inconsistent or insecure manual configurations.

Memory tip: Think of the flow as a hierarchy - Catalogs → Role Menus → Business Roles - and remember that in the cloud public edition, SAP controls the "how" (authorization defaults, catalog-driven apps), leaving you only the "what" (which catalogs/menus to assign). If an answer implies manual control over authorizations or says menus are the source of apps, it's wrong.

No community discussion yet for this question.