5V0-35.21 VMware vRealize Operations Specialist Questions and Answers

According to the VMware vRealize Operations Reference Materials, the Custom Script option in vRealize Operations is able to calculate measurements on a Guest OS. The Custom Script option allows the administrator to run a script on the Guest OS of a virtual machine and collect the output as a metric. The script can be written in any language that is supported by the Guest OS, such as PowerShell, Bash, or Python. The script can perform any calculation or operation that is required by the administrator, such as checking the CPU load, memory usage, disk space, or application status. The script output can be numeric or text, and it can be displayed in a dashboard, alert, or report. The other options, such as HTTP Check, UDP Check, or TCP Check, are not able to calculate measurements on a Guest OS. They are used to monitor the availability and response time of a web service, a UDP port, or a TCP port, respectively. They do not run any script on the Guest OS, nor do they collect any metric from the Guest OS. References: Custom Script; How to build a per-guest filesystem report in vRealize Operations using the ‘Breakdown By’ feature; How to Get In-Guest Metrics in vRealize Operations for Horizon 6

 The two actions that are possible to manage a vRealize Operations cluster using the Admin UI are uploading and installing vRealize Operations PAK files, and enabling or disabling high availability for the vRealize Operations cluster. Uploading and installing vRealize Operations PAK files is an action that allows the administrator to update the vRealize Operations software, add new features, or install management packs1. Enabling or disabling high availability for the vRealize Operations cluster is an action that allows the administrator to configure the cluster to tolerate the failure of one or more nodes, and to ensure the continuity and availability of the vRealize Operations services2. Deploying a new vRealize Operations node OVA (option A) is not an action that can be performed using the Admin UI, as it requires the use of the vSphere Client or the vSphere Web Client to deploy the OVA file to the vCenter Server3. Activating a vRealize Operations native management pack (option C) is not an action that can be performed using the Admin UI, as it requires the use of the vRealize Operations Manager UI to access the Solutions page and activate the management pack4. Configuring a DNS server on the vRealize Operations nodes (option E) is not an action that can be performed using the Admin UI, as it requires the use of the command-line interface (CLI) to access the node settings and configure the DNS server5. References:

• 1: VMware vRealize Operations Specialist Exam 2023 (5V0-35.21) Exam Guide, VMware, 2021, p. 11.
• 2: VMware vRealize Operations Specialist Exam 2023 (5V0-35.21) Exam Guide, VMware, 2021, p. 12.
• 3: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 17.
• 4: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 31.
• 5: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 25.

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

• Workload Management is a feature of VMware vRealize Operations that enables self-driving operations management for hybrid and multi-cloud environments. It uses artificial intelligence and machine learning to monitor, analyze, and automate the performance, capacity, cost, and configuration of applications, infrastructure, and services12.
• Workload Management allows administrators to set a goal for workload optimization, which defines how vRealize Operations balances the resource utilization across clusters and data centers. The goal can be one of the following options34:
• Workload Management relies on VMware Distributed Resource Scheduler (DRS) and VMware Storage DRS to perform the workload optimization actions. DRS is a feature that automatically balances the compute resources and power consumption across the hosts in a cluster. Storage DRS is a feature that automatically balances the storage resources and I/O load across the datastores in a datastore cluster .
• To enable Workload Management to move a storage resource, such as a virtual disk or a virtual machine, Storage DRS must be enabled for the cluster that contains the storage resource. Storage DRS can be enabled or disabled at the cluster level, and can be configured with different automation levels, such as manual, fully automated, or partially automated .
• If Storage DRS is not enabled for the cluster, Workload Management cannot move the storage resource, as it does not have the permission or the mechanism to do so. This is the underlying reason for the problem. The other options are not relevant for moving a storage resource. DRS is only responsible for moving the compute resources, such as CPU and memory, not the storage resources. Storage DRS can be configured for both intra-datacenter and cross-datacenter migrations, not only for cross-datacenter migrations. The automation level of DRS does not affect the ability of Workload Management to move the storage resource, as long as Storage DRS is enabled.

References:

1: vRealize Operations - VMware 2: vRealize Operations Manager User Guide 3: Workload Optimization Details - VMware Docs 4: Workload Optimization in vRealize Operations Manager : [Distributed Resource Scheduler - VMware Docs] : [Storage DRS - VMware Docs] : [Enable or Disable Storage DRS for a Datastore Cluster - VMware Docs] : [Set the Automation Level for Storage DRS - VMware Docs] : [vRealize Operations Manager Installation and Configuration Guide] : [vRealize Operations Manager Concepts Guide] : [vRealize Operations Manager Administration Guide] : [vRealize Operations Manager Customization and Extensibility Guide] : [vRealize Operations Manager Troubleshooting Guide] : [vRealize Operations Manager API Programming Guide] : [vRealize Operations Manager Certification Exam Guide]

To compare the cost of running workloads hosted with two different custom cloud providers, the administrator needs to create two new pricing cards in vRealize Operations. A pricing card is a template that defines the cost of cloud resources, such as compute, storage, network, and services. By creating two pricing cards, one for each custom cloud provider, the administrator can specify the prices for each resource type and apply discounts or markups as needed. The administrator can then use the pricing cards to run a what-if analysis and compare the cost of migrating or scaling workloads to the custom cloud providers. The other options are not correct for comparing the cost of running workloads hosted with two different custom cloud providers. Adding custom cloud providers as cloud accounts is not possible, as vRealize Operations only supports adding public cloud accounts, such as AWS, Azure, or Google Cloud. Inputting prices manually when running a what-if analysis is not efficient, as it would require entering the prices for each resource type and workload every time. Adding two custom cloud providers is not a valid option, as it is not clear how the administrator would define the cost of the cloud resources without using pricing cards. References: Create a Pricing Card, Compare the Cost of Running Workloads on Different Cloud Providers, What-If Analysis

 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

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.

 The vRealize Operations sizing tool is a web-based tool that helps you estimate the resources required for deploying and running vRealize Operations in your environment. The tool has two modes: Basic and Advanced. In the basic mode, you only need to enter information about vCenter objects, such as the number of clusters, hosts, virtual machines, and datastores. The tool also asks for the projected growth rate and data retention period for your environment. Based on these inputs, the tool provides recommendations for the node size, cluster size, and disk space for vRealize Operations. The tool also shows the maximum number of objects and metrics that can be collected by the recommendedconfiguration123. Therefore, the attribute that is required for using the vROps sizing tool in basic mode is the number of clusters. The other attributes, such as the number of virtual machine disks, vSwitches, and port groups, are not required in the basic mode. However, they can be entered in the advanced mode, along with other data sources, such as management packs, vRealize Automation, vRealize Log Insight, etc., to get a more accurate and customized sizing recommendation123. References: 1: Introducing the vRealize Operations Sizing Tool 2: vRealize Operations 8.6.0, 8.6.1, and 8.6.2 Sizing Guidelines 3: Everything You Need To Know About vRealize Operations Manager Sizing Tool

The impact setting of an alert definition determines which badge of an object is affected when the alert is triggered. The impact setting can be one of the following: Health, Risk, or Efficiency. The Health impact indicates that the alert affects the current state of the object and requires immediate attention. The Risk impact indicates that the alert affects the future state of the object and requires proactive action. The Efficiency impact indicates that the alert affects the optimal use of resources by the object and requires optimization. Therefore, to achieve the goal of affecting the Risk badge of an object when the alert is triggered, the administrator should configure the impact setting of the alert definition to Risk. References: Defining Alerts in vRealize Operations; Policy Alert Definitions

 According to the vRealize Operations User Guide1, the action that the administrator should take to accomplish the goal of making sure that the existing vRealize Operations Manager instance can monitor a newly deployed vSAN cluster within an existing vCenter Server is to enable vSAN monitoring under the existing vCenter Server Cloud Account. A vCenter Server Cloud Account is a configuration that defines the connection details and credentials of the vCenter Server instance that manages the vSphere components, such as clusters, hosts, datastores, and virtual machines. By enabling vSAN monitoring under the vCenter Server Cloud Account, the administrator can allow vRealize Operations Manager to collect data from the vSAN cluster and monitor the health, performance, capacity, and configuration of the vSAN components, such as disk groups, disks, fault domains, and storage policies. The guide provides the steps to enable vSAN monitoring under the vCenter Server Cloud Account using the vRealize Operations Manager user interface1. The other options are not correct because:

• Adding vSAN cluster under Other Accounts is not a valid action, as there is no such option in the vRealize Operations Manager user interface. The Other Accounts option under Administration is used to add accounts for other types of cloud services, such as AWS, Azure, Google Cloud, or Kubernetes, but not for vSAN cluster1.
• Downloading and installing vRealize Operations Management Pack for vSAN is not a required action, as vRealize Operations Manager already supports vSAN monitoring natively without the need of any additional management pack. The vRealize Operations Management Pack for vSAN is an optional extension that provides additional dashboards, alerts, and reports for vSAN monitoring, but it is not necessary to accomplish the goal2.
• Adding vSAN cluster under Cloud Accounts is not a valid action, as there is no such option in the vRealize Operations Manager user interface. The Cloud Accounts option under Administration is used to add accounts for VMware Cloud services, such as VMware Cloud on AWS, VMware Cloud Director, or NSX-T, but not for vSAN cluster1. References: 1: vRealize Operations User Guide, pages 17-18, 21-222: vRealize Operations Management Pack for vSAN, Overview section.

 vRealize Operations provides out-of-the-box compliance packs for various regulatory and standards-based benchmarks, such as PCI, HIPAA, DISA, CIS, and more1. These compliance packs help you assess and report the compliance status of your environment against the best practices and requirements defined by these benchmarks. You can also customize the compliance packs to suit your specific needs or create your own compliance packs2. Among the options given, PCI and HIPAA are the valid out-of-the-box compliance packs available in vRealize Operations. PCI is a compliance pack that helps you ensure the security of cardholder data in your environment3. HIPAA is a compliance pack that helps you protect the privacy and security of health information in your environment. The other options, GDPR, ISO 27017, and FedRAMP, are not out-of-the-box compliance packs in vRealize Operations, although you can create your own compliance packs for them ifneeded. References: 1: Compliance Overview - VMware Docs(https://docs.vmware.com/en/Management-Packs-for-vRealize-Operations/index.html)  2: Compliance Pack Management - VMware Docs(https://docs.vmware.com/en/Management-Packs-for-vRealize-Operations/1.0/Compliance-Pack-for-VMware-Sovereign-Cloud/GUID-3DF17387-8399-444F-BD4B-0F2EA9161532.html)  3: PCI Compliance Pack - VMware Docs(https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vmware-vrealize-operations-8.2-datasheet.pdf) : HIPAA Compliance Pack - VMware Docs

According to the vRealize Operations Cluster Management guide1, the Association Member Status indicates the state of the association between the remote collector nodes and the master node in a multisite deployment. The valid statuses are:

• Active: The remote collector node is connected to the master node and is sending data.
• Inactive: The remote collector node is not connected to the master node and is not sending data.
• Unreachable: The master node cannot reach the remote collector node due to network issues or node failure.

The Asymmetric status is not a valid status for the Association Member Status. It is a valid status for the Cluster Status, which indicates the state of the cluster nodes in a single site deployment. The Asymmetric status means that the cluster nodes are not in sync and have different configurations or versions1. References: 1: vRealize Operations Cluster Management guide, pages 3-4.

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.

 According to the VMware vRealize Operations Reference Materials, the allocation model is a capacity model that allows you to define the overcommit ratios for CPU and memory resources for your clusters. The allocation model helps you to avoid overcommitment for business-critical workloads and to comply with contractual obligations or SLAs. The allocation model calculates the capacity based on the configured overcommit ratios and the reserved capacity for the clusters. In this case, the company policy states that the clusters should never have greater than a 4:1 virtual to physical CPU ratio and a 1:1 virtual to physical memory ratio. Therefore, the allocation model should be configured for those clusters in vRealize Operations with the same overcommit ratios. This way, the capacity analytics will reflect the company policy and help to plan for infrastructure procurement or migrations based on the projection and avoid the risk of capacity shortage and high infrastructure costs. Therefore, option A is correct.

The other options are not correct because they are not capacity models that can be configured for the clusters in vRealize Operations. Option B is not correct because the demand model is a capacity model that calculates the capacity based on the actual demand for resources in the clusters. The demand model does not consider the overcommit ratios or the reserved capacity for the clusters. The demand model aims to drive towards the most efficient utilization of the clusters based on the historical utilization and the projected utilization. Option C is not correct because the limit model is not a term used in vRealize Operations, but in vSphere. The limit model is a setting that specifies the upper limit of resources that can be consumed by a virtual machine. Option D is not correct because the reservation model is not a term used in vRealize Operations, but in vSphere. The reservation model is a setting that specifies the minimum amount of resources that are guaranteed to a virtual machine. References:

• Allocation Model for Capacity Management in vRealize Operations 7.5
• Capacity Analytics
• Configuring Policies

 A vRealize Operations cluster in a Continuous Availability configuration consists of three node types: primary node, primary replica node, and witness node. These node types are deployed across two fault domains, which are separate physical locations that can tolerate failures of an entire rack or site. The witness node is deployed in a third location to monitor the network connectivity between the two fault domains and prevent split-brain scenarios1.

The primary node is the first node that is deployed in the cluster and acts as the master node. It is responsible for managing the cluster configuration, user interface, alerting, and reporting. The primary node is deployed in fault domain 11.

The primary replica node is the second node that is deployed in the cluster and acts as the backup node for the primary node. It is responsible for replicating and synchronizing the data and configuration from the primary node. The primary replica node can take over the functions of the primary node in case of a failure. The primary replica node is deployed in fault domain 21.

The witness node is the third node that is deployed in the cluster and acts as the arbitrator node. It is responsible for monitoring the network connectivity and availability of the primary node and the primary replica node. The witness node can detect a split-brain situation, which occurs when the network connection between the two fault domains is lost and both nodes assume the role of the master node. The witness node can resolve the split-brain situation by making one of the nodes offline to avoid data inconsistency. The witness node is deployed in a third location that is independent of the two fault domains1.

The other options are not node types that are configured in a Continuous Availability configuration. A secondary node is a node that is added to the cluster to increase the capacity and performance of the cluster. A secondary node can be deployed in either fault domain, but it is not required for Continuous Availability1. A remote collector node is a node that is deployed outside the cluster to collect data from remote or isolated data sources. A remote collector node can be deployed in any location, but it is not part of the Continuous Availability configuration2. A secondary replica node is not a valid node type in vRealize Operations.

References: 1: About vRealize Operations Continuous Availability 2: Remote Collector Nodes

The generate passphrase option allows the vRealize Operations administrator to create a one-time passphrase that can be used instead of the administrator credentials to add a node to the cluster. This option is useful when the administrator wants to delegate the task of adding a node to another user without exposing the administrator password. The passphrase is valid for 24 hours and can be used only once. The trainee administrator can use the passphrase to authenticate into the vRealize Operations Manager administration interface and then select the Expand an Existing Installation option to add a new node intothe cluster1. References: 1: Expand an Existing Installation to Add a Data Node

A vROps cluster in a Continuous Availability configuration consists of two fault domains, which are separate physical locations that can tolerate failures of an entire rack or site. The fault domains contain the primary node, the primary replica node, and the data nodes that store and replicate the data and configuration of the cluster. The witness node is deployed in a third location to monitor the network connectivity between the two fault domains and prevent split-brain scenarios, which occur when both fault domains assume the role of the master node due to network isolation1.

When a network outage occurs between the two fault domains, the witness node detects the situation and makes one of the fault domains offline to avoid data inconsistency. The fault domain that can still contact the witness node remains online and continues to function as the master node. The fault domain that cannot contact the witness node goes offline and stops serving requests. The VMs on the offline fault domain are restarted on the online fault domain by the vSphere HA feature1.

When the network outage is resolved and the connectivity between the two fault domains is restored, the vROps cluster will bring the offline fault domain back automatically. The offline fault domain will resync the data and configuration from the online fault domain and resume its normal operations. The administrator does not need to bring the offline fault domain online manually or restart and resync the vROps cluster1.

Therefore, the two events that will occur as a result of the outage are A. The vROps cluster will bring the fault domain back automatically once the network has been restored and D. One fault domain will go offline.

References: 1: About vRealize Operations Continuous Availability

The impact setting of an alert definition determines which badge of an object is affected when the alert is triggered. The impact setting can be one of the following: Health, Risk, orEfficiency. The Health impact indicates that the alert affects the current state of the object and requires immediate attention. The Risk impact indicates that the alert affects the future state of the object and requires proactive action. The Efficiency impact indicates that the alert affects the optimal use of resources by the object and requires optimization. Therefore, to achieve the goal of affecting the Risk badge of an object when the alert is triggered, the administrator should configure the impact setting of the alert definition to Risk. References: Defining Alerts in vRealize Operations; Policy Alert Definitions

vRealize Operations is a self-driving IT operations management platform that delivers continuous performance optimization, efficient capacity and cost management, and intelligent remediation for the VMware SDDC and hybrid cloud environments1. The use cases for vRealize Operations are aligned with these three key outcomes, as follows:

Option B is a valid use case, as Intelligent Remediation enables vRealize Operations to proactively detect and resolve issues across applications, infrastructure, and cloud services. It provides full-stack visibility, integrated compliance, and automated workflows for faster troubleshooting and remediation2.

Option D is also a valid use case, as Efficient Capacity and Cost Management enables vRealize Operations to optimize resource utilization, reduce costs, and plan for future demand. It provides real-time capacity analytics, what-if scenarios, cost transparency, and budget planning3.

Option E is also a valid use case, as Continuous Performance Optimization enables vRealize Operations to balance and optimize performance and efficiency across the SDDC and hybrid cloud. It provides automated workload placement, resource reclamation, and proactive configuration management.

Option A is not a valid use case, as Implement Zero Trust is not a core outcome of vRealize Operations. Zero Trust is a security model that requires strict verification of identity and access for every request and transaction, regardless of the location or device. While vRealize Operations can help monitor and enforce compliance policies, it is not designed to implement Zero Trust on its own.

Option C is not a valid use case, as Self-Service Catalog is not a core outcome of vRealize Operations. Self-Service Catalog is a feature of VMware vRealize® Automation™, which is a cloud automation platform that allows users to request and provision IT services from a catalog of predefined items. vRealize Operations can integrate with vRealize Automation to provide visibility and control over the cloud resources, but it does not provide the catalog functionality itself.

Option F is not a valid use case, as Infrastructure Pipelining is not a core outcome of vRealize Operations. Infrastructure Pipelining is a concept of applying DevOps principles and practices to the provisioning and management of infrastructure resources. It involves using code, automation, and continuous integration and delivery tools to streamline and standardize the infrastructure lifecycle. vRealize Operations can support Infrastructure Pipelining by providing insights and recommendations for the infrastructure performance and capacity, but it does not provide the pipelining functionality itself.

References:

• vRealize Operations - VMware Docs
• Intelligent Remediation - VMware Docs
• Efficient Capacity and Cost Management - VMware Docs
• [Continuous Performance Optimization - VMware Docs]
• [Zero Trust Security - VMware Docs]
• [vRealize Automation - VMware Docs]
• [Infrastructure Pipelining - VMware Blogs]

 According to the VMware vRealize Operations Reference Materials, interactions between widgets allow you to display data that shows dependencies between objects in your environment. For example, you can configure a widget to act as a provider or a receiver of data from another widget. When you select an object in the provider widget, the receiver widget updates to show the data related to that object. In this case, the list view widget should be configured as a provider, and the other widgets on the dashboard should be configured as receivers. This way, when the operator clicks on a virtual machine in the list view, the other widgets will show the relevant data for that virtual machine. Therefore, option D is correct.

The other options are not correct because they are not related to the problem of updating the widgets based on the selection in the list view. Option A is not correct because dashboard sharing is a feature that allows you to share a dashboard or a dashboard template with one or more user groups, but it does not affect the widget interactions. Option B is not correct because the Refresh Content option is a setting that allows you to refresh the data in a widget manually or automatically, but it does not affect the widget interactions. Option C is not correct because the object relationship widgets are a type of widgets that show the relationships between objects in your environment, such as parent-child, sibling, or peer relationships, but they are not related to the widget interactions. References:

• Create and Configure Dashboards
• Dashboards
• vRealize Operations Dashboards Made Easy - Part 3-5 Creating Dashboards
• Build great dashboards with vRealize Operations Cloud – Part 1

 According to the vRealize Operations Cloud Getting Started guide1 and the VMware Cloud Services documentation2, the invitation that an organization’s owner sends to a new user to consume VMware Cloud Services is valid for up to seven days before it is revoked. If the user does not accept the invitation within this period, the invitation expires and the user cannot join the organization. The organization’s owner can resend the invitation or revoke it if needed. The other options are not correct because they do not match the actual validity period of the invitation. References: 1: vRealize Operations Cloud Getting Started guide, page 92: VMware Cloud Services documentation, Add Users to Your Organization section.

These two prerequisites are required for integrating vRealize Operations Cloud and vRealize Log Insight Cloud to manage on-premises vSphere environments. vRealize Operations Cloud and vRealize Log Insight Cloud must be enabled in the same organizations, as this is a requirement for the integration to work properly. Organizations are logical entities that group users, projects, and resources in VMware Cloud Services. Users can belong to multiple organizations, but they can only access one organization at a time. To integrate vRealize Operations Cloud and vRealize Log Insight Cloud, users must select the same organization in both services. Deploying a cloud proxy, and then configuring vCenter and ESXi hosts syslog to forward logs to the cloud proxy is another prerequisite for the integration. A cloud proxy is a virtual appliance that collects data from on-premises sources and sends it securely to vRealize Operations Cloud and vRealize Log Insight Cloud. A cloud proxy is required to monitor on-premises vSphere environments, as it acts as a bridge between the on-premises and cloud services. Deploying the vRealize Operations Cloud Content pack, and configuring the adapter to connect to the on-premises vCenter is not a valid option, as this is not a prerequisite for the integration, but a step that can be performed after the integration is established. The vRealize Operations Cloud Content pack is a collection of dashboards, alerts, and reports that provide insights into the vRealize Operations Cloud environment. The adapter is a component that collects data from a specific source, such as vCenter, and sends it to vRealize Operations Cloud. vRealize Operations Cloud and vRealize Log Insight Cloud must be enabled in separate organizations is not a feasible option, as this is the opposite of what is required for the integration. Enabling the services in separate organizations would prevent the users from accessing both services at the same time, and would break the integration. Deploying an on-premises vRealize Log Insight instance, and configuring the integration directly with vRealize Operations Cloud is not a possible option, as this is not supported by the services. vRealize Log Insight Cloud is a cloud-based log analytics service that cannot be integrated with an on-premises vRealize Log Insight instance. vRealize Operations Cloud can only be integrated with vRealize Log Insight Cloud, not with an on-premises vRealize Log Insight instance. References: Integrating vRealize Log Insight and vRealize Operations, section “Integrating vRealize Log Insight and vRealize Operations”. Cloud Proxy Overview, section “Cloud Proxy Overview”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.

 vRealize Operations provides two types of pricing cards, cost-based and rate-based, to calculate the price associated with your virtual infrastructure. You can assign pricing cards to vCenters or Clusters, depending on the pricing strategy determined by vRealize Operations administrator. The pricing cards help you to set the price for each resource present in your virtual environment. You can customize the pricing card as per your requirement.

• Cost-based pricing card: A cost-based pricing card calculates the price based on the cost of the resources defined in vRealize Operations. You can specify a multiplication factor for each resource type, such as CPU, memory, storage, etc., to adjust the price according to your business needs. The price equation using cost is:  x = Price
• Rate-based pricing card: A rate-based pricing card calculates the price based on the rate of the resources defined by you. You can specify a rate for each resource type, such as CPU, memory, storage, etc., in terms of units, such as MHz, GB, etc. You can also specify the charging period and the power state for each resource type.The price equation using rate is:  x = Price

References: Pricing Overview; Add New Pricing Card

 According to the VMware vRealize Operations Reference Materials, the cloud provider that needs to be added as a custom cloud provider when running a What-If Analysis is Oracle Cloud. The What-If Analysis feature allows the administrator to compare the cost and performance of running workloads in different public cloud providers, such as AWS, IBM Cloud, Microsoft Azure, Google Cloud, and Alibaba Cloud. These public cloud providers are supported out-of-the-box in vRealize Operations, and the administrator can select them from the predefined list when creating a migration scenario. However, if the administrator wants to compare the cost and performance of running workloads in Oracle Cloud, they need to add it as a custom cloud provider, and upload a rate card that contains the pricing information for Oracle Cloud services. The other options are incorrect because they are supported out-of-the-box in vRealize Operations, and they do not need to be added as a custom cloud provider when running a What-If Analysis. References: What-If-Analysis - Migration Planning: Public Cloud; VMware vRealize Operations What-If Analysis; VMware vRealize Operations for Public Cloud

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 Operations 2: Configure a VMware Cloud on AWS Cloud Account in vRealize Operations 3: Configure an NSX-T Cloud Account in vRealize Operations : [Configure an NSX-V Cloud Account in vRealize Operations]

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

 Cloud Proxies are special types of remote collectors that enable vRealize Operations Cloud to collect and monitor data from on-premises data centers. Cloud Proxies establish a one-way communication channel from the on-premises environment to the vRealize Operations Cloud, and they securely upload data to the cloud instance without requiring any inbound ports to be opened on the firewall. Cloud Proxies can support multiple vCenter Server accounts and other management packs, and they provide data persistence and high availability features12. References: 1: Configuring Cloud Proxies in vRealize Operations 2: Managing Cloud Proxies in vRealize Operations

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

 The reason why vRealize Operations reports that the cluster has 0 days remaining when the actual CPU overcommit ratio is less than the 4:1 configured value is that the CPU demand in the cluster is greater than the total CPU capacity. The allocation model is a method of calculating the capacity and utilization of resources based on the amount of resources that are allocated to the objects, such as virtual machines, clusters, or datastores. The allocation model allows the administrator to set the overcommit ratio for CPU, memory, or disk space, which is the ratio of the allocated resources to the available resources. The overcommit ratio determines how much the resources can be overcommitted without affecting the performance or availability of the objects1.

When the administrator enables the allocation model in a policy and sets the CPU overcommit ratio to 4:1 for all vSphere clusters in a vSphere datacenter, it means that the administrator allows the CPU resources to be allocated four times more than the availableCPU resources in the clusters. For example, if a cluster has 100 GHz of CPU capacity, the administrator can allocate up to 400 GHz of CPU resources to the virtual machines in the cluster. However, this does not mean that the virtual machines can consume up to 400 GHz of CPU resources without any impact. The actual CPU consumption of the virtual machines depends on the CPU demand, which is the amount of CPU resources that the virtual machines require to run their workloads. The CPU demand can vary depending on the workload type, intensity, and pattern2.

If the CPU demand in the cluster is greater than the total CPU capacity, it means that the virtual machines are requesting more CPU resources than the cluster can provide. This can result in CPU contention, performance degradation, and SLA violations. In this case, vRealize Operations reports that the cluster has 0 days remaining, which means that the cluster has reached its maximum capacity and cannot accommodate any more CPU demand. The cluster has 0 days remaining even if the actual CPU overcommit ratio is less than the 4:1 configured value, because the overcommit ratio only reflects the allocated resources, not the consumed resources. The overcommit ratio does not guarantee that the cluster can support the CPU demand of the virtual machines, but only indicates the potential capacity of the cluster based on the allocation model1.

References: 1: Allocation Model - VMware Docs 2: Demand Model - VMware Docs

 The frequency at which new services are discovered when using Service Discovery in vRealize Operations is every 5 minutes. Service Discovery is a feature of vRealize Operations that allows the administrator to discover and monitor the applications and services running on the virtual machines in the environment1. Service Discovery can be performed using two methods: credential-less and credential-based. Credential-less Service Discovery uses VMware Tools to query the guest operating system for the list of running processes, and then matches them with a predefined set of signatures to identify the applications andservices2. Credential-based Service Discovery uses the credentials provided by the administrator to log in to the guest operating system and run commands or scripts to discover the applications and services3. Credential-less Service Discovery collects the information about the services running inside the guest every five minutes4. Credential-based Service Discovery collects the information about the services running inside the guest every 24 hours5. Therefore, the frequency at which new services are discovered when using Service Discovery in vRealize Operations depends on the method used, but the most frequent one is every 5 minutes for credential-less Service Discovery. References:

• 1: vRealize Operations Manager User Guide, VMware, 2021, p. 237.
• 2: vRealize Operations Manager User Guide, VMware, 2021, p. 238.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 239.
• 4: Credential-Less Service Discovery with vRealize Operations, VMware, 2020, 4.
• 5: Service Discovery with VMware vRealize Operations, Brock Peterson, 2021, 5.

 To configure vRealize Operations to operate in Continuous Availability mode, you need to use the product User Interface -> Administration -> Cluster Management -> Configure Availability option. This option allows you to enable or disable Continuous Availability for the vRealize Operations cluster, as well as to view and edit the fault domains and node pairs. You can also monitor the status and synchronization of the nodes in each fault domain12. The other options are not correct because:

• The administration User Interface --> System Status --> Configure Availability option does not exist. The administration User Interface only has the following tabs: System Status, Cluster Management, Software Update, and Support3.
• The administration User Interface -> Architecture -> Configure Availability option does not exist. The administration User Interface does not have an Architecture tab3.
• The product User Interface -> Administration -> Support -> Configure Availability option does not exist. The Support tab under the Administration menu only has the following options: Logs, Support Bundles, and Support Alerts4. References: 1: Enable Continuous Availability in vRealize Operations 2: About vRealize Operations Continuous Availability 3: [vRealize Operations Manager Administration Interface] 4: [Support]

Expected Utilization is the workload option that should be included in the scenario to simulate 25% utilization of the resources. Expected Utilization is a percentage value that indicates how much of the allocated resources (CPU, memory, and storage) are expected to be used by the workload. By setting the Expected Utilization to 25%, the administrator can model the impact of adding or removing a workload that consumes 25% of the resources in the datacenter. Memory, Annual Projected Growth, and CPU are not workload options, but workload attributes. Memory and CPU are the amount of resources allocated to the workload, and Annual Projected Growth is the percentage by which the workload is expected to grow each year. These attributes do not directly specify the utilization of the resources by the workload. References: What-If Analysis - Workload Planning: Traditional, section “How What-If Analysis - Workload Planning: Traditional Works”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.

 Symptom types are the categories of conditions that can trigger symptoms and alerts in vRealize Operations. There are six symptom types available: Metric / Property, Message, Fault, Smart Early Warning, External Event, and Metric Event1. Metric / Property symptoms compare the values of metrics or properties of an object to a static or dynamic threshold2. Fault symptoms detect faults or errors on an object based on the fault events collected by the adapter3. Alert, Action, and Recommendation are not symptom types, but they are components of alert definitions that provide information and guidance on how to resolve the problems identified by the symptoms4. References:

• Symptom Definitions
• Create a Symptom Definition Based on Metrics or Properties
• Create a Symptom Definition Based on Fault Events
• Alert Definitions

 According to the VMware vRealize Operations User Guide1, vRealize Operations allows the user to perform various actions on vSphere virtual machines from the product UI. These actions can help to manage, optimize, and troubleshoot the virtual machines and their resources. Some of the actions that can be performed on vSphere virtual machines from vRealize Operations product UI are:

• Create virtual machine snapshot: This action creates a snapshot of the virtual machine, which is a point-in-time copy of the virtual machine state and data. A snapshot can be used to revert the virtual machine to a previous state, or to clone or migrate the virtual machine. The user can specify the name, description, and memory options for the snapshot.
• Delete virtual machine snapshot: This action deletes a snapshot of the virtual machine, which frees up the disk space used by the snapshot. The user can select the snapshot to delete from a list of available snapshots for the virtual machine.
• Move virtual machine: This action moves the virtual machine to a different host or cluster within the same vCenter Server. The user can select the destination host or cluster from alist of compatible and available options. The move action can help to balance the workload or improve the performance of the virtual machine.

Therefore, the correct answers are A. Create virtual machine snapshot, B. Delete virtual machine snapshot, and C. Move virtual machine, as these are three of the actions that can be performed on vSphere virtual machines from vRealize Operations product UI. References:

• 1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 31-32, 34-35, 37-38

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 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 Operations 2: Self-Driving Operations by VMware vRealize Operations Datasheet

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

To apply a super metric to other vRealize Operations instances, you need to export the super metric from the source instance and import it to the destination instance. Exporting a super metric creates a JSON file that contains the super metric definition and attributes. Importing a super metric allows you to upload the JSON file and add the super metric to the destination instance. You can also choose to overwrite or skip an existing super metric with the same name. Adding or updating a super metric are not the correct steps, as they are used to create or modify a super metric within the sameinstance. References: Exporting and Importing a Super Metric

The type of node that should be deployed to monitor a remote datacenter using an existing vRealize Operations Manager cluster is a Remote Collector node. A Remote Collector node is a node that is deployed in a remote datacenter location across a firewall, and collects data from the remote objects without performing analysis or storing data. A Remote Collector node can reduce the bandwidth consumption and the load on the vRealize Operations analytics cluster, and can also navigate firewalls and interface with remote data sources12. A Remote Collector node can be deployed on a different operating system than the rest of the cluster, and can support a round-trip time (RTT) of up to 200 ms3.

The other options are not correct, because they are not suitable for monitoring a remote datacenter with a high RTT. A Replica node is a node that is converted from a Data node to provide high availability (HA) or continuous availability (CA) for the vRealize Operations cluster. A Replica node is a copy of the Primary node, and must be deployed in the same datacenter as the Primary node1. A Data node is a node that performs data collection and analysis for the vRealize Operations cluster, and can be added to scale out the cluster capacity and performance. A Data node must be deployed in the same datacenter as the Primary node, and can support a RTT of up to 10 ms1. A Witness node is a node that is required for continuous availability (CA) of the vRealize Operations cluster, and acts as a decision maker in case of a network partition between two fault domains. A Witness node must be deployed in a third datacenter that is separate from the two fault domains, and can support a RTT of up to 100 ms1.

References:

• About vRealize Operations Cluster Nodes - VMware Docs
• vRealize Operations Manager: Design Introduction - VMware Blogs
• Mastering vRealize Operations Manager - Second Edition - Packt Subscription
• vRealize Operations node types - Mastering vRealize Operations Manager …

The regulatory, standards-based compliance pack that is available in vRealize Operations is the CIS Security Standards. The CIS Security Standards are a set of best practices and recommendations for securing IT systems and data against cyberattacks. The CIS Security Standards are developed and maintained by the Center for Internet Security (CIS), a nonprofit organization that provides cybersecurity resources and guidance to organizations and individuals1. The vRealize Operations Compliance Pack for CIS provides alerts, policies,and reports to validate the vSphere resources against the CIS hardening guide. The following resources are being validated using this content: ESXi Host, Virtual Machine, vCenter Server, Distributed Switch, Distributed Port Group, and Distributed Firewall2. The vRealize Operations Compliance Pack for CIS can be downloaded and installed from the VMware Marketplace3. The Sarbanes-Oxley Act (SOX) (option A) is not a regulatory, standards-based compliance pack that is available in vRealize Operations. SOX is a federal law that regulates the financial reporting and auditing of public companies in the United States. SOX does not provide specific technical guidelines or benchmarks for securing IT systems and data4. The Common Vulnerabilities and Exposures (CVE) (option B) is not a regulatory, standards-based compliance pack that is available in vRealize Operations. CVE is a list of publicly known cybersecurity vulnerabilities and exposures that are assigned unique identifiers and descriptions. CVE does not provide specific security standards or recommendations for securing IT systems and data5. The General Data Protection Regulation (GDPR) (option D) is not a regulatory, standards-based compliance pack that is available in vRealize Operations. GDPR is a legal framework that regulates the collection, processing, and transfer of personal data of individuals in the European Union and the European Economic Area. GDPR does not provide specific technical guidelines or benchmarks for securing IT systems and data. References:

• 1: CIS Security Standards - cisecurity.org, CIS, 2021, [7].
• 2: vRealize Operations Compliance Pack for CIS - VMware Marketplace, VMware, 2021, 1.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 237.
• 4: Sarbanes-Oxley Act (SOX) - investopedia.com, Investopedia, 2021, [8].
• 5: Common Vulnerabilities and Exposures (CVE) - cve.mitre.org, MITRE, 2021, [9].
• [6]: General Data Protection Regulation (GDPR) - ec.europa.eu, European Commission, 2021, [10].
• [7]: CIS Security Standards - cisecurity.org, CIS, 2021, [7].
• [8]: Sarbanes-Oxley Act (SOX) - investopedia.com, Investopedia, 2021, [8].
• [9]: Common Vulnerabilities and Exposures (CVE) - cve.mitre.org, MITRE, 2021, [9].
• [10]: General Data Protection Regulation (GDPR) - ec.europa.eu, European Commission, 2021, [10].

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

Implementing vRealize Operations Cloud involves accessing the service, which is typically done by signing up or logging in through a web interface. Additionally, deploying and configuring a cloud proxy is essential as it acts as a bridge between your on-premises environment and the vRealize Operations Cloud. This proxy collects data from your environment and sends it securely to the cloud instance.