5V0-35.21 Exam Dumps - VMware vRealize Operations - Cloud Management Automation 2023 Questions and Answers

Continuous Availability (CA) is a feature of vROps that separates the analytics cluster into two fault domains, stretching across vSphere clusters, and protects the analytics cluster against the loss of an entire fault domain. CA requires a witness node to be deployed in the cluster, which acts as a tiebreaker in case of a network partition between the two fault domains. CA ensures that the data stored in the primary node and data nodes in one fault domain is always 100% synced to the replica node and data nodes in the other fault domain. CA is not a disaster recovery solution, but it provides a higher level of availability and data protection than High Availability (HA), which only protects against the loss of a single node. HA creates a replica for the primary node, but does not replicate the data nodes. Therefore, if a whole rack fails, HA may not be able to prevent data loss. Deploying an additional vROps deployment as a standby or configuring remote collector groups are not options that address the requirement of ensuring no monitoring data is lost in the event of a whole rack failure. These options may provide some redundancy or scalability, but they do not guarantee data consistency or availability across fault domains. References: 1: About vRealize Operations Continuous Availability 2: Continuous Availability Considerations 3: About vRealize Operations High Availability 4: High Availability Considerations

To view the status of all objects in vRealize Operations, you can create a dashboard by adding widgets or views. You can create and modify dashboards and configure them to meet your environment needs. Widgets are graphical elements that display data and analysis from vRealize Operations. Views are predefined or custom presentations of object data that you can use in dashboards, reports, or alerts. Alerts, recommendations, and reports are not objects that can be used to create dashboards, but they can be displayed or accessed from dashboards. References:

• Create and Configure Dashboards
• Dashboards
• vROPS Dashboards Overview

vRealize Operations Manager supports various notification methods out of the box, including email notifications and integration with third-party systems. Microsoft Teams is one of the platforms supported for notifications, allowing for alerts and updates fromvRealize Operations Manager to be directly sent to a Microsoft Teams channel. This integration facilitates real-time alerting and collaboration within IT teams. However, options like SMS and Slack might require additional third-party plugins or integrations and are not natively supported as out-of-the-box notification types. Remedy, being an IT service management tool, can be integrated but is not a direct notification type.

 According to the VMware vRealize Operations User Guide1, vRealize Operations allows the user to perform various actions on vSphere virtual machines from the product UI. These actions can help to manage, optimize, and troubleshoot the virtual machines and their resources. Some of the actions that can be performed on vSphere virtual machines from vRealize Operations product UI are:

• Create virtual machine snapshot: This action creates a snapshot of the virtual machine, which is a point-in-time copy of the virtual machine state and data. A snapshot can be used to revert the virtual machine to a previous state, or to clone or migrate the virtual machine. The user can specify the name, description, and memory options for the snapshot.
• Delete virtual machine snapshot: This action deletes a snapshot of the virtual machine, which frees up the disk space used by the snapshot. The user can select the snapshot to delete from a list of available snapshots for the virtual machine.
• Move virtual machine: This action moves the virtual machine to a different host or cluster within the same vCenter Server. The user can select the destination host or cluster from alist of compatible and available options. The move action can help to balance the workload or improve the performance of the virtual machine.

Therefore, the correct answers are A. Create virtual machine snapshot, B. Delete virtual machine snapshot, and C. Move virtual machine, as these are three of the actions that can be performed on vSphere virtual machines from vRealize Operations product UI. References:

• 1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 31-32, 34-35, 37-38

A cloud proxy is an appliance that enables vRealize Operations Cloud to collect and monitor data from the on-premises environment. A cloud proxy is deployed as an OVA template on a vCenter Server instance that manages the on-premises resources. A cloud proxy creates a one-way communication between the on-premises environment and vRealize Operations Cloud by uploading data from the remote collectors to the cloud service. A cloud proxy can support multiple vCenter Server accounts and other data sources that are configured in vRealize Operations Cloud1.

The other options are not appliances that are needed to achieve this goal. A reverse proxy is a server that receives requests from clients and forwards them to the origin server. A reverse proxy can provide security, load balancing, caching, and compression functions. A reverse proxy is not used to create a one-way communication between the on-premises environment and vRealize Operations Cloud2. A web proxy is a server that acts as an intermediary between a web browser and the internet. A web proxy can provide anonymity, filtering, caching, and security functions. A web proxy is not used to create a one-way communication between the on-premises environment and vRealize Operations Cloud3. A VMware proxy is not a valid appliance in vRealize Operations.

References: 1: Configuring Cloud Proxies in vRealize Operations 2: What is a Reverse Proxy Server? | NGINX 3: What is a Web Proxy? | Proxy Server | Cloudflare

 According to the VMware vRealize Operations Reference Materials, Service Discovery is a feature that allows you to automatically discover and monitor the services running on your virtual machines. Service Discovery can use two methods: credential-based and credential-less. Credential-based Service Discovery requires you to provide guest credentials for each virtual machine, while credential-less Service Discovery uses VMware Tools to run scripts on the guest operating system without requiring credentials.

For Linux virtual machines, credential-less Service Discovery requires the installation of Telegraf agent, which is a data collection and reporting agent that communicates with VMware Tools. If the Telegraf agent is not installed on the Linux virtual machines, Service Discovery will fail to authenticate and collect data from them. Therefore, option A is correct.

Another requirement for Linux virtual machines is to enable the open-vm-tools-sdmg package, which is a service discovery management pack that allows VMware Tools to runscripts for Service Discovery. If the open-vm-tools-sdmg package is not enabled on the Linux virtual machines, Service Discovery will also fail to authenticate and collect data from them. Therefore, option D is correct.

The other options are not correct because they are not related to the authentication status of Service Discovery. Option B is not correct because the required network ports are not specific to Linux virtual machines, and they are only needed for credential-based Service Discovery. Option C is not correct because the version of VMware Tools does not affect the authentication status of Service Discovery, as long as it supports the credential-less method. Option E is not correct because the Endpoint Operations agent is not required for Service Discovery, and it is used for a different purpose of collecting metrics and properties from the guest operating system and applications. References:

• Service Discovery Overview
• Credential-Less Service Discovery with vRealize Operations
• Install Telegraf Agent on Linux Virtual Machines
• [Enable open-vm-tools-sdmg Package on Linux Virtual Machines]

vRealize Operations allows for different node sizes when deploying a cluster to suit various environments and scalability needs. The sizes typically include Small, Medium, and Large, and these sizes determine the capacity and performance of each node in a High Availability configuration.

References:

• About vRealize Operations Cluster Nodes
• High Availability (HA)
• vRealize Operations 8.6.0, 8.6.1, and 8.6.2 Sizing Guidelines

According to the VMware vRealize Operations Reference Materials, a vRealize Operations cluster consists of three types of nodes: primary, data, and remote collector. The primary node is the initial and required node that manages the cluster configuration and data synchronization. The data nodes are optional nodes that have adapters installed and perform data collection and analysis. The remote collector nodes are also optional nodes that can navigate firewalls, interface with remote data sources, reduce bandwidth consumption, and reduce the load on the analytics cluster. They only gather objects for the inventory, without storing data or performing analysis. Therefore, options A, C, and E are correct.

The other options are not correct because they are not types of nodes that make up the vRealize Operations cluster. Option B is not correct because the cloud connector is not a node, but a service that connects vRealize Operations to VMware Cloud services. Option D is not correct because the worker node is not a term used in vRealize Operations, but in vRealize Automation. Option F is not correct because the secondary node is also not a term used in vRealize Operations, but in vSphere Replication. References:

• About vRealize Operations Cluster Nodes
• vRealize Operations Manager Cluster Node Types
• Service Discovery Overview

To get application-related data (metrics) from the VM that vRealize Operations doesn’t collect, the administrator can use the custom script feature of the End Point Operations Management agent. The custom script feature allows the administrator to run custom scripts in the end point VM and collect custom data which can then be consumed as a metric. The administrator needs to install the End Point Operations Management agent on the VM, place the appropriate script to the VM, and then configure the agent to call the script from the Manage Agent location for the VM in vRealize Operations. The script metrics are created under an object called Custom Script which is a single object per end point VM. The administrator can view the output for the specific metric in the All Metrics tab1. The Telegraf agent is not used for custom script monitoring, but for application monitoring using predefined plugins2. The script should not be placed in the vRealize Operation Manager, but in the end point VM. References: 1: Custom Script 2: Application Monitoring

The two required components of an alert definition are symptom and action. An alert definition is a configuration that defines the conditions and actions for generating an alert1. An alert is a notification that indicates a potential or existing issue with an object in the environment2. An alert definition consists of the following components3:

• Symptom: A symptom is a condition that indicates a deviation from the normal or expected behavior of an object. A symptom can be based on metrics, properties, events, or messages. A symptom can have a severity level and a wait cycle. A symptom is a required component of an alert definition, as it triggers the alert when it is met.
• Recommendation: A recommendation is a suggestion or a guidance that provides a possible solution or a mitigation for the issue that caused the alert. A recommendation can include a link to a relevant document or a workflow. A recommendation is an optional component of an alert definition, as it helps the user to resolve the alert, but it does not affect the alert generation.
• Action: An action is a task or a workflow that can be executed automatically or manually to resolve the issue that caused the alert. An action can be based on vRealize Orchestrator workflows or vRealize Operations Manager tasks. An action is a required component of an alert definition, as it defines the response for the alert when it is generated.
• Version: A version is a number that indicates the release or the update of the alert definition. A version is an optional component of an alert definition, as it helps the user to track the changes and the compatibility of the alert definition, but it does not affect the alert generation.
• Node: A node is a vRealize Operations Manager instance that is part of a cluster. A node is an optional component of an alert definition, as it helps the user to specify the scope and the source of the alert definition, but it does not affect the alert generation.

Therefore, the two required components of an alert definition are symptom and action, while the other components are optional. References:

• 1: vRealize Operations Manager User Guide, VMware, 2021, p. 93.
• 2: vRealize Operations Manager User Guide, VMware, 2021, p. 91.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 94.