After an initial deployment of vRealize Operations (vROps) and configuration of the vCenter Cloud Account, an administrator notices that a vSphere Solution's Default Policy was created. What is the origin of the settings in this policy?
Correct Answer: C
The vSphere Solution's Default Policy is a policy that is automatically created when you add a vCenter Cloud Account to vROps. This policy applies to all the objects that are discovered and collected by the vSphere adapter. The origin of the settings in this policy is the base settings that are provided by the data adapters and solutions installed in vROps. The base settings are a collective group of rules that apply to all objects, regardless of their type or source. The vSphere Solution's Default Policy inherits all the base settings by default, and you can modify them to suit your specific needs. The default policy setting is not defined by another administrator, nor is it added during the installation of the vROps management pack for vSphere. The settings of this policy are also not defined during the vROps OVF deployment, as they are determined by the data adapters and solutions. References: Default Policy in vRealize Operations, Configure VMware SDDC Benchmarks
Question 7
An administrator is creating a new alert definition. It was decided that this new alert should affect the Risk badge of an object when triggered. Which setting should be configured by the administrator to achieve this goal?
Correct Answer: A
Question 8
Which step is required before a Super Metric's data collection may begin?
Correct Answer: D
According to the VMware vRealize Operations User Guide1, a Super Metric is a custom metric that is derived from one or more existing metrics. A Super Metric can be used to calculate complex formulas, aggregate data across multiple objects, or create new metrics that are not available by default. A Super Metric can be created using the Super Metric Editor in vRealize Operations. However, before a Super Metric's data collection may begin, the Super Metric must be enabled in a policy. A policy is a set of rules and settings that determine how vRealize Operations analyzes and manages the objects in the environment. A policy can be applied to one or more object types or groups. To enable a Super Metric in a policy, the administrator must edit the policy, select the Collect Metrics and Properties option, and then select the Super Metric from the list of available metrics. The administrator can also specify the collection level, collection interval, and retention period for the Super Metric. The other options are not required before a Super Metric's data collection may begin. Enabling in Alerts, Object Types, or Objects are not necessary steps for collecting Super Metric data. These options are used for different purposes, such as creating alert definitions, defining object relationships, or assigning policies to individual objects. References: 1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 35-36, 39-40, 43-44
Question 9
Where can management packs for vRealize Operations be found and downloaded?
Correct Answer: B
Management packs in VMware vRealize Operations provide capability for expanding the monitoring, troubleshooting, and remediation functionality of SDDC and third party solutions. Administrators can install and configure management packs in a vRealize Operations instance. You can download Management Packs and End Point Operations Plug-Ins for vRealize Operations from VMware Marketplace1. For detailed information on installing and configuring the Management Pack, refer to the related user guide2. References: 1: Management Packs for vRealize Operations Documentation 2: List of Management Packs
Question 10
An administrator created a new cost-based pricing card and attached it to a VMware Cloud on AWS (VMC) resource. When the administrator checked the pricing of a VM after the cost calculation had successfully run, the pricing showed zero. What is the possible reason for this situation?
Correct Answer: B
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
