An existing vRealize Operations user has been granted the Administrator role. The previous ReadOnly role has not been removed for the user. What is the expected behavior when the user attempts to crea

Question

Options

• AThe user will need ContentUser role before the user is able to create dashboards.
• BThe user will need DashboardManager role before the user is able to create dashboards.
• CThe user can create dashboard without changing any roles or permissions.
• DThe user cannot create dashboards until the ReadOnly role is removed.

• A
  4% (1)
• B
  4% (1)
• C
  85% (23)
• D
  7% (2)

Explanation

In vRealize Operations, when a user is assigned multiple roles, permissions are additive - the most permissive role wins. Since the Administrator role includes full dashboard creation rights, the ReadOnly role is effectively superseded, and the user can create dashboards immediately without any role changes.

Why the distractors are wrong:

• A (ContentUser) and B (DashboardManager) are wrong because the Administrator role already encompasses all permissions those roles provide - there is no need to add lesser roles on top of it.
• D is wrong because vROps does not require removal of a less-permissive role before a more-permissive one takes effect; having conflicting roles resolves in favor of the higher privilege, not the lower one.

Memory tip: Think of vROps roles like a stack of access cards - security always honors the highest clearance card in your wallet, not the lowest. "More roles = more access, never less."

No community discussion yet for this question.