How does SAP Fiori achieve the role-based design principle? Note: There are 2 correct answers to this question.

Question

Options

• ABy defining SAP Fiori apps that users can tailor exactly to their needs
• BBy giving end users exactly what they need for their work
• CBy separating transactional and analytical apps in different business roles
• DBy decomposing big transactions into several discrete apps suited to the user's role

• A
  7% (2)
• B
  77% (23)
• C
  17% (5)

Explanation

SAP Fiori's role-based principle centers on giving each user precisely what their job requires - nothing more, nothing less. B is correct because Fiori apps are purpose-built per role, stripping away irrelevant functionality so a purchasing approver, for example, sees only approval-related tasks. D is correct because Fiori achieves this by breaking traditional monolithic SAP transactions (e.g., a single enormous ME21N screen) into small, focused apps - each scoped to a specific task within a role, rather than forcing every user through the same complex interface.

A is wrong because role-based design is defined by administrators and role configurations, not by end users tailoring apps to personal preference - that describes personalization/extensibility, a different Fiori principle.

C is wrong because separating transactional from analytical apps describes Fiori's app type classification (transactional, analytical, fact sheet), not its role-based principle - conflating these two is a common trap.

Memory tip: Think "role = job, not preference." Role-based = B (right info for the job) + D (big transactions sliced into role-sized pieces). If an answer implies the user customizes anything, it's describing personalization, not role-based design.

No community discussion yet for this question.