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

To achieve the lowest cost in Workload Optimization, the administrator should select the Consolidate option, which will place VMs into as few clusters as possible, but allows for less responsive capacity.This is good for populations with steady demand and may reduce licensing and hardware costs, such as power and cooling1.The Consolidate option is one of the three operational intents that can be selected for Workload Optimization, along with Balance and Moderate2. The Balance option will spread VMs evenly over the available resources, but may move VMs more often.The Moderate option will minimize VM contention, but will not attempt to move VMs to achieve better balance or consolidation1.References:1:Optimize Performance with VMware vRealize Operations2:Self-Driving Operations by VMware vRealize Operations Datasheet

A custom script is a way to collect data from an application that is not supported by the default Telegraf plugins1.A custom script can be written in any language that can run on the end point VM, such as Python, PowerShell, or Bash2.The custom script must output the data in a specific format that can be parsed by the Telegraf agent and sent to vRealize Operations3.The custom script can be configured in the telegraf.conf file or in a separate file under the /etc/telegraf/telegraf.d/ directory4.References:1: Telegraf Agent - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.config.doc/GUID-0C121456-370C-467E-874B-38ACC93E3776.html)2: Custom Script - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.core.doc/GUID-9614C495-FAE0-4E95-8EE2-6FDA57355C0E.html)3: Custom Script Output Format - VMware Docs(https://www.funkycloudmedina.com/2022/06/how-to-install-vrealize-operations-telegraf-agent-using-vrealize-automation-and-saltstack-config/)4: Configure Telegraf Agent - VMware Docs(https://www.brockpeterson.com/post/windows-service-monitoring-with-vmware-vrealize-operations)

To automate an action for an alert, you must enable it in the object's associated policy. A policy defines the settings and rules that vRealize Operations applies to objects in your environment. You can activate actionable alerts in your policies by selecting the Automate option for the alert definition that is associated with the symptom, recommendation, and action that you want to automate. When an alert is triggered that is associated with the recommendation, it triggers the action without any user intervention. The other options are not correct because they do not enable the automation of the action. An object's associated recommendation is a suggestion for resolving the problem indicated by the alert, but it does not activate the action. An object in the default policy is not specific enough to enable the automation of the action. An object's associated symptom definition is a condition that indicates a potential problem, but it does not activate the action.References:Actions Supported for Automation,VMware vRealize Operations Actions

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 Overview2:Change the Cost Calculation Interval

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: =1Managing Custom Object Groups in vRealize Operations - VMware Docs,2Policies - VMware Docs

To allow the newly added group members to login quickly into vRealize Operations, the administrator needs to synchronize the user groups from the Active Directory source and check if the automatic synchronization option is enabled. Synchronizing the user groups imports the latest user group information from the source to vRealize Operations. Checking the automatic synchronization option ensures that the user group membership is updated periodically without manual intervention. Re-adding or deleting the authentication source are not necessary steps, as they would disrupt the existing user access control. Adding a SAML IdP as authentication source is not relevant, as the question is about Active Directory groups.References:Import User Groups From Source,Export and Import of User Groups,Synchronize the Active Directory Groups for VMware Aria Operations in Workspace ONE Access

Host-based placement is a feature of Business Intent that allows you to use vSphere tags to match VMs with hosts based on your business needs. For example, you can use host-based placement to enforce license compliance, security isolation, or performance optimization. When you create a host-based placement in a Business Intent, vRealize Operations automatically creates VM groups, host groups, and affinity rules for you to meet your objectives. These affinity rules are DRS 'must run on' rules that restrict the placement of VMs to hosts with matching tags. After you confirm the host-based placement, any existing DRS rules that conflict with the newly created affinity rules will be disabled. This is to ensure that the Business Intent is not violated by the DRS rules.You can view the disabled DRS rules in the vSphere Client under the Configure tab of the cluster123.References:1:Using Host Rules with Business Intent in vRealize Operations 7.02:Business Intent Workspace3:Self-Driving all the way to the Host? Oh yeah Host Based Placement ...

Suspending an alert is the action that allows the administrator to stop the alert from triggering again while investigating the problem.Suspending an alert also automatically assigns the alert to the user who performed the action1.Suspending an alert does not cancel or disable the alert, but rather pauses the alert evaluation until the user resumes or cancels the alert2.Taking ownership of an alert does not stop the alert from triggering again, but only indicates that the user is responsible for resolving the alert3.Disabling an alert prevents the alert from being generated for any object, which is not recommended unless the alert is no longer relevant or useful4.Canceling an alert removes the alert from the system, which is not appropriate if the alert is still valid and requires investigation.References:1: Suspend an Alert - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.user.doc/GUID-595146FB-93F7-4F34-A9D3-79144EA7A658.html)2: Alert Actions - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.core.doc/GUID-F9AF30F3-089B-43A8-8323-F266E51C05B8.html)3: Take Ownership of an Alert - VMware Docs(https://kb.vmware.com/s/article/2012021)4: Disable an Alert Definition - VMware Docs(https://www.brockpeterson.com/post/vmware-vrealize-operations-actions) : Cancel an Alert - VMware Docs

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