5V0-35.21 Exam Dumps - VMware vRealize Operations Specialist

Cost calculation in vRealize Operations is the process of computing the cost of resources and services for your monitored environment. Cost calculation by default occurs daily and whenever there is a change in the inventory or cost drivers values. You can also trigger the cost calculation manually from the Administration > Cost Calculation page1. The default cost calculation interval is every 24 hours, which means that vRealize Operations will update the cost data once a day at the specified time. You can change the cost calculation interval from the Administration > Management > Global Settings > Cost Calculation page2. References: 1: Cost Calculation Status Overview 2: Change the Cost Calculation Interval

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

 According to the vRealize Operations Sizing Guidelines, the supported node configurations during installation are Large, Very Large, and Medium. These are the default configurations that VMware offers based on the number of objects and metrics to be monitoredby vRealize Operations. Each configuration has a different amount of vCPU, memory, disk space, and network requirements. The administrator can choose the configuration that best suits the existing infrastructure and the expected growth of the environment1.

The other options are not supported node configurations during installation. Tiny and Small are not valid configurations for vRealize Operations 8.x and later versions. These configurations were available for vRealize Operations 6.x and 7.x versions, but they are not recommended for production environments due to their limited capacity and performance2. No limit is not a configuration option, but a statement that indicates that there is no upper limit on the number of nodes that can be added to a vRealize Operations cluster. However, the number of nodes depends on the node configuration, the network latency, and the data source type3.

References: 1: vRealize Operations 8.0.x Sizing Guidelines (75162) - VMware 2: vRealize Operations Manager 7.5 Sizing Guidelines (67752) 3: vRealize Operations 8 - VMware Docs

According to the VMware vRealize Operations Reference Materials, the Wait Cycle and the Cancel Cycle are the settings that determine how long a symptom condition must be true or false before the symptom is triggered or cancelled. The default cycle for both settings is 5 minutes, which means that each cycle corresponds to one collection interval of 5 minutes. Therefore, if a symptom has a Wait Cycle of 3 and a Cancel Cycle of 2, it will take 15 minutes (3 cycles x 5 minutes) for the symptom to be triggered after the condition becomes true, and 10 minutes (2 cycles x 5 minutes) for the symptom to be cancelled after the condition becomes false. The other options are incorrect because they do not match the calculation based on the given settings and the default cycle. References: Symptom Definition Settings; Alert Definition Best Practices

 To estimate the monthly cost of running workloads in IBM Cloud, the administrator can use the What-If Analysis feature of vRealize Operations, which allows forecasting the impact of migrating a workload to a public cloud instance such as AWS, IBM Cloud, Microsoft Azure, Google Cloud or to VMware Cloud on AWS1. The administrator can select the Migration Planning option and choose IBM Cloud as the target cloud provider. Then, the administrator can import the existing VMs that support the business-critical applicationfrom the custom group in vRealize Operations and select all machines to be included in the scenario. Finally, the administrator can run the scenario and get the vRealize Operations analysis and assessment of the plan, which includes the cost and capacity information for the IBM Cloud region2. References: 1: What-If Analysis - Migration Planning: Public Cloud 2: Migration Planning

Custom groups are collections of objects that you define based on criteria that you specify. You can use custom groups to assign different vRealize Operations policies to a particular set of objects that share common characteristics or belong to a specific business unit1. Custom groups allow you to override the default policy settings for the objects in the group and apply a different policy that suits your requirements2. For example, you can create a custom group of ESXi clusters that run database servers and assign a different capacity policy to them than the rest of the clusters in your environment2. References: = 1 Managing Custom Object Groups in vRealize Operations - VMware Docs, 2 Policies - VMware Docs

According to the vRealize Operations Cloud Getting Started guide1, the initial step that the administrator must take to use vRealize Operations Cloud to monitor an on-premises deployment is to deploy a Cloud Proxy on-premises, and pair it with vRealize Operations Cloud. 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. The other options are not correct because:

• Initiating a Cloud Proxy deployment on the cloud console, and pairing it with vRealize Operations Cloud is not a valid step, as there is no such option in the vRealize Operations Cloud user interface. The Cloud Proxy must be deployed on-premises, not on the cloud console1.
• Opening firewall ports to vRealize Operations Cloud from the on-premises vCenter, and then adding the on-premises deployment is not a sufficient step, as it does not establish a secure and reliable connection between the on-premises vCenter instance and the vRealize Operations Cloud instance. The Cloud Proxy is required to facilitate the data collection and communication between the two instances1.
• Deploying a vRealize Operations node on-premises, and pairing it with vRealize Operations Cloud is not a recommended step, as it will introduce additional complexity and overhead in managing the on-premises vRealize Operations node. The Cloud Proxy is a lightweightand easy-to-deploy appliance that does not require any additional licenses or configuration1. References: 1: vRealize Operations Cloud Getting Started guide, pages 9-13.

 Alert recommendations are the remediation options that you provide to your users toresolve the problems that the generated alert indicates. When you add an alert definition that indicates a problem with objects in your monitored environment, add a relevant recommendation. Recommendations can be instructions to your users, links to other information or instruction sources, or vRealize Operations actions that run on the target systems1. Alert recommendations are not always linked to a Knowledge Base article, and they can be created or modified by the user2. References: 1: Defining Alerts in vRealize Operations 2: User Scenario: Monitor and Process Alerts in vRealize Operations Manager