What are some disadvantages of a Composite Role? Note: There are 2 correct answers to this question.

Question

Options

• AChanges to the included roles are not immediately visible in the composite role menu, requiring a
• BMenus from the included roles cannot be mixed.
• CChanges to the authorizations can only be made using the included roles.
• DTransactions that are deleted from the Composite Role menu are also removed from the included

• A
  79% (56)
• B
  7% (5)
• D
  14% (10)

Explanation

In SAP, a Composite Role is a container that groups single (included) roles together, but it does not hold its own authorization data - only the included roles do. This means authorization changes must be made at the single role level (C), since the composite role has no independent authorization profile to edit. Additionally, when an included role's menu is updated, that change is not immediately reflected in the composite role's menu - the composite role must be regenerated/refreshed for the update to appear (A).

B is wrong because mixing menus from included roles is actually a feature of composite roles, not a limitation.

D is wrong because the relationship is one-directional: changes in included roles affect the composite role, but deleting items from the composite role menu does not cascade back to the included roles.

Memory tip: Think of a Composite Role as a "read-only wrapper" - it reads from its included roles but cannot write back to them, and it doesn't always reflect updates instantly. When in doubt, ask: "Where does the real data live?" - always in the included roles, never in the composite itself.

No community discussion yet for this question.