An administrator needs to provide limited monitoring capabilities in vRealize Operations Manager for vSphere objects. Which source of the user groups automatically ensures the access to vSphere object

Question

Options

• AVMware Identity Manager
• BSingle sign-on (SSO)
• CLDAP server
• DLocal users

• B
  93% (26)
• C
  4% (1)
• D
  4% (1)

Explanation

Single Sign-On (SSO) user groups are sourced directly from the vCenter SSO domain, which is natively integrated with the vSphere object hierarchy - meaning when these groups are imported into vROps, their scope is automatically restricted to vSphere objects without additional manual configuration, making them ideal for limited monitoring roles.

VMware Identity Manager (A) is a broader enterprise identity platform spanning many services beyond vSphere, so access is not automatically scoped to vSphere objects and requires extra policy work. LDAP (C) is a generic directory service with no inherent awareness of vSphere objects - admins must manually define scope after importing groups. Local users (D) are created within vROps itself and always require explicit role and object scope assignments; nothing is automatic.

Memory tip: Associate SSO with the letter "S" for Sphere-native - because SSO is the vSphere authentication layer, any group you pull from it already "lives in the vSphere world," so vSphere object scope comes for free.

No community discussion yet for this question.