5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

According to the vRealize Operations Cloud Getting Started guide1, the two steps that are needed to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance are:

• Deploy and configure a cloud proxy. A cloud proxy is a virtual appliance that acts as a bridge between the on-premises vCenter instance and the vRealize Operations Cloud instance. It collects data from the vCenter instance and sends it securely to the vRealize Operations Cloud instance. It also enables actions and remote console access from the vRealize Operations Cloud instance to the on-premises vCenter instance. The guide provides the steps to download, deploy, and configure the cloud proxy using the vRealize Operations Cloud user interface1.
• Add a vCenter cloud account. A vCenter cloud account is a configuration that defines the connection details and credentials of the on-premises vCenter instance. It also specifies the cloud proxy that is associated with the vCenter instance. The guide provides the steps to add a vCenter cloud account using the vRealize Operations Cloud user interface1.

The other options are not correct because:

• Deploying and configuring a Data node is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A Data node is a component of the vRealize Operations Cloud cluster that stores and processes data. It is managed by the vRealize Operations Cloud service provider and does not need to be deployed or configured by the customer2.
• Deploying and configuring a Primary node is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A Primary node is a component of the vRealize Operations Cloud cluster that provides the user interfaceand administration functions. It is managed by the vRealize Operations Cloud service provider and does not need to be deployed or configured by the customer2.
• Adding a vRealize Operations Cloud account is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A vRealize Operations Cloud account is a configuration that defines the connection details and credentials of the vRealize Operations Cloud instance. It is used to integrate vRealize Operations Cloud with other VMware Cloud services, such as VMware Cloud on AWS or VMware Cloud Director. It is not related to the on-premises vCenter instance3. References: 1: vRealize Operations Cloud Getting Started guide, pages 9-132: vRealize Operations Cloud Concepts guide, pages 5-63: vRealize Operations Cloud User Guide, pages 17-18.

According to the vRealize Operations User Guide1, Business Intent is a feature that allows the administrator to define the performance, efficiency, and consolidation goals for the clusters and hosts in the SDDC, and to specify the maximum amount of cluster resources to be reserved for burst capacity. Business Intent is applied to objects in vRealize Operations using vCenter Server tags, which are key:value labels that allow operators to add meta-data to vCenter Server objects. By tagging VMs, hosts, and/or clusters with specific tags, the administrator can create business-related placement constraints, such as VMs can only be placed on hosts/clusters with matching tags. For example, the tag OS: Linux can indicate a cluster or VM that is assigned to the category OS with a tag name of Linux. vRealize Operations then uses these tags to optimize the placement and balance of the workloads, and to perform automated remediation actions in the event of an issue. The other options are not correct because:

• Groups are not used to apply Business Intent to objects in vRealize Operations. Groups are collections of objects that share common characteristics, such as type, name, location, or relationship. Groups are used to organize objects for monitoring, analysis, alerting, or policy assignment, but not for workload placement or balance1.
• Policies are not used to apply Business Intent to objects in vRealize Operations. Policies are sets of configuration settings that define how vRealize Operations monitors and manages the objects in the SDDC. Policies are used to enable or disable alerts, metrics, properties, symptoms, recommendations, or actions for different types of objects, but not for workload placement or balance1.
• Roles are not used to apply Business Intent to objects in vRealize Operations. Roles are collections of permissions that define what actions a user can perform on the objects in the SDDC. Roles are used to control the access and visibility of the objects for different users, but not for workload placement or balance1. References: 1: vRealize Operations User Guide, pages 57-59, 62-63, 66-67, 70-71.

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”.