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

According to the VMware vRealize Operations Reference Materials, primary nodes are responsible for managing the cluster configuration and synchronizing data across the cluster. They can also function as NTP servers for the cluster, ensuring that all nodes have the same time settings. Remote collector nodes, replica nodes, and data nodes rely on the primary nodes for NTP settings and cannot act as NTP servers themselves.References:

vRealize Operations Manager Cluster Node Types

Configuring NTP Settings

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 application from 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 Cloud2:Migration Planning

According to the vRealize Operations documentation, the Administrator role includes privileges to all features, objects, and actions in vRealize Operations, including creating and managing dashboards1. Therefore, if a user has been granted the Administrator role, they can create dashboards regardless of any other roles they may have.The ReadOnly role does not prevent the user from creating dashboards, as it only limits their access to read operations1.The ContentUser and DashboardManager roles are not required for creating dashboards, as they only provide privileges to manage specific content types1.References:1: Roles and Privileges in vRealize Operations - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.core.doc/GUID-9F316466-FACA-4DA0-8F3E-51BC73793990.html)

The possible reason for this situation is that only rate-based pricing cards are applied with VMC resources. A rate-based pricing card is a pricing card that defines the rates for each resource type, such as CPU, memory, disk, and network. A cost-based pricing card is a pricing card that defines the basic charges for each object type, such as host, cluster, datastore, and virtual machine.vRealize Operations supports both types of pricing cards for vSphere resources, but only supports rate-based pricing cards for VMC resources1.When a cost-based pricing card is assigned to a VMC resource, the price calculated for the policy is reported as zero2. To avoid this situation, the administrator should create and assign a rate-based pricing card for the VMC resource.

The other options are not correct, because they are not the possible reasons for this situation. Option A is not correct, because a zero value for one of the basic charges in the cost-based pricing card would not result in a zero price for the VM.The price of the VM would be calculated based on the sum of the basic charges for the VM object type and its parent object types, such as datastore, cluster, and host3. Option C is not correct, because the cost calculation does not need to run twice when using VMC.The cost calculation runs every 24 hours for all the pricing cards, regardless of the cloud provider4.Option D is not correct, because pricing cards are supported with VMC resources, as long as they are rate-based pricing cards1.

References:

Pricing for vRealize Automation 8.x Components in vRealize Operations - VMware Docs

Pricing Overview - VMware Docs

Add New Pricing Card - VMware Docs

Cost Calculation - VMware Docs

A cloud account in vRealize Operations is a configuration that enables data collection from a cloud platform or service.vRealize Operations supports various cloud account types, such as vCenter Server, AWS, Azure, Google Cloud Platform, VMware Cloud on AWS, and VMware Cloud on Dell EMC1.VMware Cloud on AWS is a cloud account type that allows you to monitor and manage your VMware Cloud on AWS SDDC resources, such as hosts, clusters, datastores, and virtual machines2.NSX-T and NSX-V are not cloud account types, but network and security solutions that can be integrated with vRealize Operations3.References:1:Cloud Accounts in vRealize Operations2:Configure a VMware Cloud on AWS Cloud Account in vRealize Operations3:Configure an NSX-T Cloud Account in vRealize Operations: [Configure an NSX-V Cloud Account in vRealize Operations]

To create a capacity policy for a custom group of ESXi clusters with a different CPU allocation model than the default policy, the following steps are required:

Create a new policy ''Database Servers'', and then inherit it from the current default policy.This will create a copy of the default policy that can be customized for the custom group1.

Edit the new policy under section Groups and Objects, and then select Custom Group ''Database Servers''.This will apply the new policy to the custom group and override the default policy for the objects in the group1.

Edit the new policy under section Capacity, filter object type by custom group ''Database Servers'', and then modify Allocation model to 2:1.This will change the CPU allocation model for the custom group to match the requirements2.

References: =2Capacity Optimization for Your Managed Environment - VMware Docs,1Policies - VMware Docs

The Troubleshooting Workbench is a feature in vRealize Operations that helps you perform advanced troubleshooting tasks on an alert or an object. You can look for potential evidences of a problem within a specific scope and time range. The potential evidences are based on three types of data: Alerts, Events, and Property Changes. Alerts show the active and inactive alerts that are related to the object or its peers. Events show the events that are based on a change in the metrics, such as spikes, drops, or anomalies. Property Changes show the changes in the configuration or properties of the object or its peers, such as CPU, memory, or disk allocation. These types of data help you identify the root cause of the issue and take corrective actions. Symptoms and Anomalous Metrics are not considered as potential evidence in the Troubleshooting Workbench, although they may be used to trigger alerts or events. Logs are not displayed in the Troubleshooting Workbench, but they can be accessed from the Logs tab of the object.References:Discovering Potential Evidences Using the Troubleshooting Workbench,Solving Real Problems with vRealize Operations Troubleshooting Workbench,Troubleshooting Workbench Home Page,vROps 8.0 Troubleshooting Workbench and Blue Medora

Cost drivers are the expense types used by vRealize Operations to calculate the cost of your private cloud. The total private cloud cost is the sum of cost drivers.Changes that are made to cost drivers are reflected only after the next run of the cost engine1.Cost drivers cover server hardware, storage, licenses, application, maintenance, labor, network, facilities, and additional costs configured within vRealize Operations2. When calculating the monthly cluster costs, vRealize Operations considers the following two types of cost drivers:

VMware software per socket: This is the cost of VMware licenses based on the number of sockets in the cluster.You can assign different license costs to different clusters depending on the edition and features you use3.

Storage maintenance as a percentage of hardware costs: This is the cost of maintaining the storage hardware used by the cluster. You can specify the percentage of the storage hardware cost that goes into maintenance.For example, if the storage hardware cost is $10,000 and the maintenance percentage is 10%, the storage maintenance cost is $1,0004.References:1:Overview of Cost Drivers2:VM Pricing with vRealize Automation 8.1 and vRealize Operations 8.13:License Cost Driver4:Storage Cost Driver

To view the status of all objects in vRealize Operations, you can create a dashboard by adding widgets or views. You can create and modify dashboards and configure them to meet your environment needs. Widgets are graphical elements that display data and analysis from vRealize Operations. Views are predefined or custom presentations of object data that you can use in dashboards, reports, or alerts. Alerts, recommendations, and reports are not objects that can be used to create dashboards, but they can be displayed or accessed from dashboards.References:

Create and Configure Dashboards

Dashboards

vROPS Dashboards Overview