5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

The alternative that is offered by default when Workload Planning returns that an existing cluster does not have the capacity to accommodate the selected virtual machines is cost comparisons for running in hybrid/private/public cloud. Workload Planning is a feature ofvRealize Operations that allows the administrator to plan and optimize the workload placement and capacity of the vSphere resources in the environment1. Workload Planning can be performed using two scenarios: Workload Optimization and What-If Analysis. Workload Optimization is a scenario that automatically balances the workload across the clusters and datastores based on the business and operational intents, such as performance, consolidation, or compliance2. What-If Analysis is a scenario that simulates the impact of adding or removing workloads, hosts, or datastores, or changing the demand or configuration of the existing workloads3. When Workload Planning is performed using the What-If Analysis scenario, and it returns that an existing cluster does not have the capacity to accommodate the selected virtual machines, the alternative that is offered by default is cost comparisons for running in hybrid/private/public cloud. This alternative allows the administrator to compare the estimated costs of running the selected virtual machines in different cloud platforms, such as VMware Cloud on AWS, Microsoft Azure, or Amazon Web Services, and to choose the best option for the business needs and budget4. Cost options for increasing cluster capacity with additional hosts (option B) is not the alternative that is offered by default, but it is another option that can be selected by the administrator. This option allows the administrator to estimate the costs of adding new hosts to the existing cluster, and to choose the best host model and quantity for the capacity and performance requirements5. Modifications to virtual machine configuration (option C) and modifications to host configurations (option D) are not alternatives that are offered by Workload Planning, as they are not related to the workload placement and capacity planning. These modifications can be performed using other features of vRealize Operations, such as Reclaimable Waste, Oversized Virtual Machines, or Configuration and Compliance. References:

• 1: VMware vRealize Operations Specialist Exam 2023 (5V0-35.21) Exam Guide, VMware, 2021, p. 14.
• 2: vRealize Operations Manager User Guide, VMware, 2021, p. 167.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 179.
• 4: vRealize Operations Manager User Guide, VMware, 2021, p. 187.
• 5: vRealize Operations Manager User Guide, VMware, 2021, p. 186.
• [6]: vRealize Operations Manager User Guide, VMware, 2021, pp. 77-78, 83-84, 229-230.

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

Data nodes are the type of node in a vRealize Operations (vROps) design that allow an administrator to scale out vROps to monitor very large environments. Data nodes are additional nodes that have all the vROps services installed, such as UI, Controller, Analytics, Collector, and Persistence. Data nodes perform data collection and analysis, and increase the capacity and performance of the vROps cluster. Data nodes can be added or removed as needed to adjust to the changing workload and environment size. Remote collectors are not a type of node in a vROps design, but a separate component that can be deployed to collect data from remote sources and send it to the vROps cluster. Remote collectors do not store data or perform analysis, and do not increase the capacity or performance of the vROps cluster. Replica Primary nodes and Primary nodes are not the type of node that allow an administrator to scale out vROps to monitor very large environments, but the type of node that provide high availability and continuous availability for the vROps cluster. Replica Primary nodes and Primary nodes contain critical services that cannot be replicated across all cluster nodes, such as Global xDB, NTP server, and GemFire locator. Replica Primary nodes and Primary nodes do not perform data collection and analysis, and do not increase the capacity or performance of the vROps cluster. References: About vRealize Operations Cluster Nodes, section “About vRealize Operations Cluster Nodes”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.