5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

 vRealize Operations provides two types of pricing cards, cost-based and rate-based, to calculate the price associated with your virtual infrastructure. You can assign pricing cards to vCenters or Clusters, depending on the pricing strategy determined by vRealize Operations administrator. The pricing cards help you to set the price for each resource present in your virtual environment. You can customize the pricing card as per your requirement.

• Cost-based pricing card: A cost-based pricing card calculates the price based on the cost of the resources defined in vRealize Operations. You can specify a multiplication factor for each resource type, such as CPU, memory, storage, etc., to adjust the price according to your business needs. The price equation using cost is:  x = Price
• Rate-based pricing card: A rate-based pricing card calculates the price based on the rate of the resources defined by you. You can specify a rate for each resource type, such as CPU, memory, storage, etc., in terms of units, such as MHz, GB, etc. You can also specify the charging period and the power state for each resource type.The price equation using rate is:  x = Price

References: Pricing Overview; Add New Pricing Card

 According to the vRealize Operations User Guide1, one of the best ways to quickly identify the underlying problem of slow application VMs is to use the out-of-the-box Performance dashboards that display contention on both VMs and ESXi hosts. These dashboards show the key performance indicators (KPIs) of CPU, memory, disk, and network for the selected objects, and highlight any contention or saturation issues that may affect the performance. The administrator can use these dashboards to drill down into the details of the metrics, alerts, events, and properties of the objects, and isolate the root cause of the problem. The other options are not correct because:

• Under Inventory, selecting Manage Agent, then selecting the VMs, and running Remote Checks on ICMP, HTTP checks is not a helpful action, as it only verifies the connectivity and availability of the VMs, but does not provide any information about the performance or contention of the VMs or the ESXi hosts2.
• Under Report, using Configuration Report - Virtual Machines to list down possible changes that have occurred is not a helpful action, as it only shows the configuration details of the VMs, such as name, UUID, power state, guest OS, CPU, memory, disk, and network, but does not show any performance or contention metrics or alerts of the VMs or the ESXi hosts3.
• Under Administration, choosing Configuration, selecting Object Relationships, and then identifying the VMs and ESXi hosts relationship to generate a correlation of the metric, and finally, isolate the issue is not a helpful action, as it only shows the hierarchical and logical relationships between the objects, such as parent, child, sibling, and peer, but does not show any performance or contention metrics or alerts of the objects4. References: 1: vRealize Operations User Guide, pages 57-59, 62-632: vRealize Operations User Guide, pages 69-703: vRealize Operations User Guide, pages 81-824: vRealize Operations User Guide, pages 84-85.

To generate a daily email report of a list of VMs that have been provisioned from vRA, you need to follow these steps:

• Create a custom view that displays the VM name, owner, and creation date for the deployments in the defined cluster. You can use the vRealize Automation Reporting - vRA8 deployment resources and statuses sample as a reference1.
• Create a report that uses the custom view as the template and select the output format as CSV or JSON.
• Schedule the report to run daily and set the start date and recurrence to daily (option A).
• In the Email addresses text box, enter the email addresses that must receive the report, and select an outbound rule (option B). You also need to configure an email server in vRealize Automation Service Broker to send notifications2.
• Click on Schedule, select vSphere Hosts and Clusters, expand vSphere World, and select the specific cluster (option E). This will filter the report data to only include the VMs provisioned to the defined cluster.
• Save the report and verify that it is sent to the email recipients as expected.

Option C is not required because the report is sent via email and does not need to be stored in an external location. Option D is redundant because the start date and recurrence are already set in option A. Option F is incorrect because it will include all the VMs in the vCenter, not just the ones in the defined cluster. References:

• Create and Configure Reports
• Send email notifications to Service Broker users
• vRealize Automation Reporting - vRA8 deployment resources and statuses