VMware 5V0-35.21 Practice Test - Questions Answers, Page 7

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.

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.

What-If Analysis is a feature of vRealize Operations that allows you to plan for an increase or decrease in workload or capacity requirements in your virtual infrastructure. You can use What-If Analysis to evaluate the demand and supply for capacity on your resources, and to assess the potential risk to your current capacity.You can create scenarios for adding and removing workloads, hosts, clusters, or datastores, and see the impact on the time remaining and capacity remaining scores12.

Time remaining and capacity remaining are two metrics that measure the available capacity in your environment. Time remaining is the estimated time until a resource runs out of capacity based on the current utilization and growth trends. Capacity remaining is the percentage of unused capacity that is available for future growth.Both metrics are calculated for CPU, memory, disk space, and network bandwidth resources34.

By using What-If Analysis, you can accomplish the goal of determining how many more ESXi servers are needed to increase the time remaining and capacity remaining scores. You can create a scenario for adding ESXi servers to a cluster or a datacenter, and specify the number, type, and configuration of the servers. You can then see the projected time remaining and capacity remaining scores for the cluster or the datacenter after adding the servers. You can also compare the results with the current scores and the recommended scores.You can adjust the number of servers until you reach the desired scores5.

References:

1:What-If Analysis: Modeling Workload, Capacity, or Migration Planning2:Create a What-If Scenario3: [Capacity Overview - VMware Docs]4: [Time Remaining and Capacity Remaining Metrics]5: [Add Hosts to a Cluster or Datacenter Scenario] : [View the Results of a What-If Scenario] :vRealize Operations Manager User Guide:vRealize Operations Manager Installation and Configuration Guide: [vRealize Operations Manager Concepts Guide] : [vRealize Operations Manager Administration Guide] : [vRealize Operations Manager Customization and Extensibility Guide] : [vRealize Operations Manager Troubleshooting Guide] : [vRealize Operations Manager API Programming Guide] : [vRealize Operations Manager Certification Exam Guide]

According to the vRealize Operations User Guide1, the action that the administrator should take to accomplish the goal of making sure that the existing vRealize Operations Manager instance can monitor a newly deployed vSAN cluster within an existing vCenter Server is to enable vSAN monitoring under the existing vCenter Server Cloud Account. A vCenter Server Cloud Account is a configuration that defines the connection details and credentials of the vCenter Server instance that manages the vSphere components, such as clusters, hosts, datastores, and virtual machines. By enabling vSAN monitoring under the vCenter Server Cloud Account, the administrator can allow vRealize Operations Manager to collect data from the vSAN cluster and monitor the health, performance, capacity, and configuration of the vSAN components, such as disk groups, disks, fault domains, and storage policies.The guide provides the steps to enable vSAN monitoring under the vCenter Server Cloud Account using the vRealize Operations Manager user interface1. The other options are not correct because:

Adding vSAN cluster under Other Accounts is not a valid action, as there is no such option in the vRealize Operations Manager user interface.The Other Accounts option under Administration is used to add accounts for other types of cloud services, such as AWS, Azure, Google Cloud, or Kubernetes, but not for vSAN cluster1.

Downloading and installing vRealize Operations Management Pack for vSAN is not a required action, as vRealize Operations Manager already supports vSAN monitoring natively without the need of any additional management pack.The vRealize Operations Management Pack for vSAN is an optional extension that provides additional dashboards, alerts, and reports for vSAN monitoring, but it is not necessary to accomplish the goal2.

Adding vSAN cluster under Cloud Accounts is not a valid action, as there is no such option in the vRealize Operations Manager user interface.The Cloud Accounts option under Administration is used to add accounts for VMware Cloud services, such as VMware Cloud on AWS, VMware Cloud Director, or NSX-T, but not for vSAN cluster1.References:1: vRealize Operations User Guide, pages 17-18, 21-222: vRealize Operations Management Pack for vSAN,Overviewsection.

These two methods will meet the goal of creating a trust relationship between the cluster and each of these new nodes. Generating passphrases in the administration User Interface of an existing node, and entering them when prompted in each new node is a method that allows the administrator to securely authenticate the new nodes to the cluster. The passphrase is a one-time password that is valid for 24 hours and can be used to add multiple nodes to the cluster. Clicking the Add New Nodes button on the System Status page in the administration User Interface of an existing node is another method that allows the administrator to initiate the process of adding new nodes to the cluster. The administrator can enter the FQDN or IP address of the new node, and then validate the certificate and accept the trust relationship. Clicking the Add New Nodes button on the Cluster Management page in the product User Interface of an existing node is not a valid option, as this button does not exist on that page. Using any local or directory user with the Administrator role in vRealize Operations when prompted in each new node is not a feasible option, as the new node does not have any local or directory users configured yet. Using the vRealize Operations root user name and password when prompted in each new node is not a reliable option, as the root user name and password may not be the same for all the nodes, and may not be known by the administrator.References:Expand an Existing Installation to Add a Data Node, section ''Expand an Existing Installation to Add a Data Node''.Add a Node to a vRealize Operations Analytics Cluster, section ''Add a Node to a vRealize Operations Analytics Cluster''.vRealize Operations Manager User Guide, section ''Create and Configure Dashboards''.

The scoreboard widget configuration option that possibly caused this problem is Self Provider set to On. The Self Provider option determines whether the widget shows metrics of the objects selected during editing of the widget or selected on another widget. When the Self Provider option is set to On, the widget shows metrics of the objects selected during editing of the widget. When the Self Provider option is set to Off, the widget shows metrics of the objects selected on another widget. Therefore, if the administrator wants to enable a custom metric configuration file to a scoreboard widget in a dashboard, and the custom metrics are defined for a specific object type, the administrator should set the Self Provider option to Off and select the appropriate object type on another widget. Otherwise, the scoreboard widget will not show the new metrics at all, because the custom metric configuration file will not match the object type selected during editing of the widget.References:How the Scoreboard Widget and Configuration Options Work;Solved: How to configure Generic Scoreboard widget to interact with...

An alert notification is a message that vRealize Operations sends to an external system or user when an alert is generated that meets certain criteria. An alert notification can help the administrator to identify and troubleshoot problems immediately after they occur. To enable alert notifications, the administrator must configure an outbound alert plug-in, which is a component that connects vRealize Operations to the external alert notification system, such as email, REST, SNMP, or log file.The administrator can also create notification rules, which are filters that specify which alerts are sent out for the supported outbound alert plug-ins1.

The other options are not accurate descriptions of the characteristics of an alert notification. Option A is incorrect because notifications are not configured out-of-the-box, but require the administrator to configure the outbound alert plug-in and the notification rules.Notifications also do not need to be explicitly enabled for each object discovered by vRealize Operations, but can be applied to multiple objects based on the notification rules1.Option B is incorrect because a SMTP Management pack is not required to enable email notifications, but the Standard Email plug-in, which is a built-in outbound alert plug-in that sends notifications to one or more email addresses2. Option C is incorrect because notifications are not configured as part of an alert's symptom definition, but as a separate configuration that applies to one or more alerts.A symptom definition is a condition that indicates a potential problem with an object, and is used to trigger an alert, not a notification3.

References:1:Creating and Managing vRealize Operations Alert Notifications - VMware Docs2:Configure a Standard Email Notification in vRealize Operations3:Symptom Definitions - VMware Docs

According to the VMware vRealize Operations User Guide1, tags are labels that can be assigned to objects in vRealize Operations to group them based on common attributes or criteria. Tags can be used to filter, search, and organize objects in vRealize Operations, as well as to define policies, alerts, dashboards, and reports. Tags can also be used to configure tiers, which are logical groups of objects that represent different levels of service or performance in the environment. For example, the administrator can create tiers such as Gold, Silver, and Bronze, and assign tags to the objects that belong to each tier. Then, the administrator can use the tags to apply different policies, alerts, or dashboards to each tier.

One of the grouping options in vRealize Operations that allows the configuration of tiers is Tags. This option allows the administrator to create custom groups based on the tags assigned to the objects. The administrator can select one or more tags to define the membership criteria for the custom group. The administrator can also specify the object type and the adapter type for the custom group. The custom group can then be used to configure tiers in vRealize Operations.

Therefore, the correct answer is A. Tags, as this is the grouping option in vRealize Operations that allows the configuration of tiers.References:

1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 59-60, 63-64

Learn more

1docs.vmware.com2vmware.com3vmware.com

According to the VMware vRealize Operations Reference Materials, the cloud provider that needs to be added as a custom cloud provider when running a What-If Analysis is Oracle Cloud. The What-If Analysis feature allows the administrator to compare the cost and performance of running workloads in different public cloud providers, such as AWS, IBM Cloud, Microsoft Azure, Google Cloud, and Alibaba Cloud. These public cloud providers are supported out-of-the-box in vRealize Operations, and the administrator can select them from the predefined list when creating a migration scenario. However, if the administrator wants to compare the cost and performance of running workloads in Oracle Cloud, they need to add it as a custom cloud provider, and upload a rate card that contains the pricing information for Oracle Cloud services. The other options are incorrect because they are supported out-of-the-box in vRealize Operations, and they do not need to be added as a custom cloud provider when running a What-If Analysis.References:What-If-Analysis - Migration Planning: Public Cloud;VMware vRealize Operations What-If Analysis;VMware vRealize Operations for Public Cloud

The configuration that was sized using the vROps sizing tool is High Availability.High Availability is a feature of vRealize Operations that allows the cluster to tolerate the failure of one or more nodes, and to ensure the continuity and availability of the vRealize Operations services1.High Availability can be enabled or disabled in the Admin UI of vRealize Operations, and it requires at least two nodes in the cluster2.The vROps sizing tool is a web-based tool that helps the administrator to estimate the size and the resources needed for a vRealize Operations deployment, based on the number and the type of the objects to be monitored3. The vROps sizing tool provides different sizing options, such as Extra Large, Large, Medium, Small, and Extra Small, and shows the specifications and the costs for each option.The vROps sizing tool also allows the administrator to select the configuration mode, such as High Availability, Continuous Availability, Stretched Cluster, or Fault Tolerance, and shows the impact of the mode on the sizing and the resources4. The image that was sent with the question shows the output of the vROps sizing tool, with the configuration mode set to High Availability. The image shows the recommended size as Medium, with 2 nodes, 5564 metrics, and 980812 properties. The image also shows the other sizing options, such as Extra Large, Large, Small, and Extra Small, with their respective specifications and costs. Therefore, the configuration that was sized using the vROps sizing tool is High Availability.Continuous Availability (option B) is not the correct answer, as it is a different configuration mode that allows the cluster to tolerate the failure of an entire site, and to ensure the zero data loss and the near-zero downtime of the vRealize Operations services5. Continuous Availability requires at least four nodes in the cluster, and it uses synchronous replication between the sites. The image does not show the configuration mode as Continuous Availability, nor the number of nodes as four. Stretched Cluster (option C) is not the correct answer, as it is a different configuration mode that allows the cluster to span across two sites, and to ensure the load balancing and the disaster recovery of the vRealize Operations services. Stretched Cluster requires at least four nodes in the cluster, and it uses asynchronous replication between the sites. The image does not show the configuration mode as Stretched Cluster, nor the number of nodes as four. Fault Tolerance (option D) is not the correct answer, as it is not a configuration mode that is supported by vRealize Operations. Fault Tolerance is a feature of vSphere that provides continuous availability for a virtual machine by creating and maintaining a secondary virtual machine that is identical to the primary virtual machine. Fault Tolerance is not applicable to vRealize Operations, as it does not support the clustering and the scalability of the vRealize Operations nodes.References:

1: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 12.

2: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 13.

3: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 15.

4: vRealize Operations Manager Sizing - VMware, VMware, 2021,1.

5: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 14.

[6]: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 16.

[7]: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 14.

[8]: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 17.

[9]: vSphere Availability, VMware, 2021, p. 9.