What should be defined to ensure that group members can access vRealize Operations objects when importing a group from Active Directory into vRealize Operations?

What should be defined to ensure that group members can access vRealize Operations objects when importing a group from Active Directory into vRealize Operations?
A . Description
B . Role
C . Group Members
D . Type

View Answer

Answer: B

Explanation:

: Role is the attribute that should be defined to ensure that group members can access vRealize Operations objects when importing a group from Active Directory into vRealize Operations. Role is a set of permissions that defines what actions a user or a group can perform on vRealize Operations objects, such as dashboards, alerts, reports, and policies. By assigning a role to a group, the administrator can grant or restrict access to vRealize Operations objects for all the group members. Description, Group Members, and Type are not attributes that ensure that group members can access vRealize Operations objects when importing a group from Active Directory into vRealize Operations. Description is an optional field that provides additional information about the group. Group Members is a list of users that belong to the group. Type is a classification of the group based on the source, such as Local, LDAP, or Active Directory.

References: Import User Groups From Source, section “Import User Groups From Source”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.