5V0-35.21 VMware vRealize Operations Specialist Questions and Answers

Cloud Accounts are the connections that allow vRealize Operations Manager to collect data from various cloud platforms and services. vRealize Operations Manager supports several types of Cloud Accounts, such as VMware Cloud, Amazon Web Services, Microsoft Azure, Google Cloud, and Kubernetes1. To monitor all supported environments, the administrator can use any combination of these Cloud Accounts, depending on the cloud services that the company is consuming. However, among the options given, only Amazon Web Services (AWS) and VMware Cloud on AWS are valid Cloud Accounts that can be used in vRealize Operations Manager. AWS is the leading public cloud provider that offers a wide range of compute, storage, networking, database, analytics, and other services2. VMware Cloud on AWS is a hybrid cloud service that delivers a consistent VMware environment on the AWS infrastructure, allowing customers to migrate, extend, and modernize their applications3. Both AWS and VMware Cloud on AWS can be integrated with vRealize Operations Manager by configuring the respective Cloud Accounts and providing the necessary credentials and regions45.

Google Cloud, Alibaba Cloud, and IBM Cloud are also popular public cloud providers that offer various cloud services, but they are not supported as Cloud Accounts in vRealize Operations Manager. Therefore, they cannot be used to monitor the environments in vRealize Operations Manager. To monitor these cloud platforms, the administrator might need to use other tools or methods, such as third-party management packs, custom integrations, or external APIs . References:

• Cloud Accounts
• Amazon Web Services
• VMware Cloud on AWS
• Configure an Amazon Web Services Cloud Account in vRealize Operations
• Configure a VMware Cloud on AWS Cloud Account in vRealize Operations
• [Google Cloud Platform Management Pack for vRealize Operations]
• [Alibaba Cloud Monitoring]
• [IBM Cloud Monitoring]

The nature of this change is that the administrator will now be able to complete tasks associated with remediation actions, such as executing actions on alerts, recommendations, or symptoms. This is because the PowerUser role includes all the privileges of the PowerUserMinusRemediation role, plus the privileges to perform remediation actions. The PowerUserMinusRemediation role is a predefined role that has all the privileges of the Administrator role except for user management, cluster management, and remediation actions. The PowerUser role is a predefined role that has all the privileges of the Administrator role except for user management and cluster management. Therefore, by adding the PowerUser role to the administrator’s user account, the helpdesk team has granted the administrator the additional privilege to perform remediation actions. The administrator will not be able to perform cluster management tasks or user management tasks, as these privileges are not included in the PowerUser role or the PowerUserMinusRemediation role. The administrator will not remain unable to complete tasks associated with remediation actions, as this privilege is included in the PowerUser role. References: Roles and Privileges in vRealize Operations, section “Roles and Privileges in vRealize Operations”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.

The administrator needs the Active Directory domain administrator account and password to configure service discovery to identify which virtual machines are running Active Directory services. 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 and services2. Credential-based service discovery uses the credentials provided by the administrator to log in to theguest operating system and run commands or scripts to discover the applications and services3. Credential-less service discovery can be used for most common applications and services, such as web servers, database servers, or file servers, but it has some limitations, such as not being able to discover clustered or distributed applications, or applications that run on non-standard ports4. Credential-based service discovery can be used for more complex and customized applications and services, such as Active Directory, Exchange, or SharePoint, but it requires the administrator to provide the appropriate credentials for each guest operating system. For Windows operating systems, the credentials must be either a local administrator account or a domain administrator account. For Active Directory services, the domain administrator account is preferred, as it has the necessary permissions to access the Active Directory information and configuration. Therefore, the administrator needs the Active Directory domain administrator account and password to configure service discovery to identify which virtual machines are running Active Directory services. No credentials are needed since credential-less service discovery can be used (option A) is not a correct answer, as credential-less service discovery cannot discover Active Directory services, which require credential-based service discovery. Local Windows administrator account and password (option B) is not a correct answer, as the local administrator account may not have the sufficient permissions to access the Active Directory information and configuration, which require the domain administrator account. Active Directory domain user account and password (option D) is not a correct answer, as the domain user account may not have the necessary permissions to access the Active Directory information and configuration, which require the domain administrator account. 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: vRealize Operations Manager User Guide, VMware, 2021, p. 240.
• [5]: vRealize Operations Manager User Guide, VMware, 2021, p. 241.
• [6]: vRealize Operations Manager User Guide, VMware, 2021, p. 242.
• [7]: vRealize Operations Manager User Guide, VMware, 2021, p. 244.

The function that is unavailable in the vRealize Operations Admin UI is viewing alerts, symptoms, and policies. The Admin UI is a separate interface from the Product UI that provides access to selected maintenance functions beyond what the Product UI supports. TheAdmin UI is used for platform administration tasks, such as upgrading vRealize Operations, enabling or disabling High Availability (HA), uploading and installing vRealize Operations PAK files, taking vRealize Operations Online/Offline, and managing certificates, passwords, and users1. The Admin UI does not provide access to the operational functions, such as viewing alerts, symptoms, and policies, which are available in the Product UI. The Product UI is used for monitoring and managing the objects, metrics, alerts, dashboards, reports, and policies in vRealize Operations2.

References: 1: About the vRealize Operations Administration Interface 2: About the vRealize Operations Product Interface

According to the VMware vRealize Operations Install and Configure Guide1, the sizing tool is a web-based application that helps to estimate the required resources and configuration for a vRealize Operations cluster. The sizing tool takes into account various parameters,such as the number and type of objects to be monitored, the number of metrics and properties to be collected, the number of alerts and dashboards to be displayed, the number of users and concurrent sessions, and the desired availability and performance of the cluster.

Two of the additional parameters that are taken into account when sizing a vRealize Operations cluster using the sizing tool are:

• Time Series Data Retention: This parameter specifies the duration for which the collected metrics and properties are stored in the vRealize Operations database. The longer the retention period, the more disk space is required for the cluster nodes. The sizing tool allows the user to select the retention period from 1 month to 12 months, or to enter a custom value.
• Projected Growth: This parameter specifies the expected increase in the number and type of objects to be monitored over time. The higher the projected growth, the more resources are required for the cluster nodes. The sizing tool allows the user to select the projected growth from 0% to 100%, or to enter a custom value.

Therefore, the correct answers are A. Time Series Data Retention and C. Projected Growth, as these are two of the additional parameters that are taken into account when sizing a vRealize Operations cluster using the sizing tool. References:

• 1: VMware vRealize Operations Install and Configure Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-installation-and-configuration-guide.pdf, page 11-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

According to the VMware vRealize Operations Reference Materials, the purpose of the self-provider option within the dashboard definition is to indicate whether objects appearing in the widget are defined in the widget or are provided by another widget source. The self-provider option is a checkbox that can be enabled or disabled for each widget in a dashboard. When the self-provider option is enabled, it means that the widget has its own object selector, and the user can choose the objects to display in the widget from the available inventory. When the self-provider option is disabled, it means that the widget does not have its own object selector, and the objects to display in the widget are provided by another widget in the same dashboard. For example, a widget that shows the metrics of a selected object can be configured as a non-self-provider, and it can receive the object selection from another widget that shows the list of objects. The other options are incorrect because they are either false or irrelevant. The self-provider option does not affect the refresh content setting, the custom set of metrics, or the automatic refreshing of the data in the widget display. These are separate settings that can be configured for each widget independently of the self-provider option. References: Create a Dashboard; Widget Configuration; Dashboard Interactions

 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 TroubleshootingWorkbench, Troubleshooting Workbench Home Page, vROps 8.0 Troubleshooting Workbench and Blue Medora

 To share the custom dashboard with the database admin group and meet the requirements, the administrator can use the options for sharing dashboards in vRealize Operations. The administrator can generate a custom URL of the dashboard, which will allow the database admin group to view the dashboard without authentication. The administrator can also set the expiry period for the link to one week, so that the access to the dashboard will be available only during the mentioned time period. The administrator can then send the database admin team an e-mail that includes the custom URL, so that they can access the dashboard from the e-mail. Alternatively, the administrator can copy the custom URL and share it with the database admin group through other means1. References: 1: Options for Sharing Dashboards - VMware Docs

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

vRealize Operations allows for different node sizes when deploying a cluster to suit various environments and scalability needs. The sizes typically include Small, Medium, and Large, and these sizes determine the capacity and performance of each node in a High Availability configuration.

References:

• About vRealize Operations Cluster Nodes
• High Availability (HA)
• vRealize Operations 8.6.0, 8.6.1, and 8.6.2 Sizing Guidelines

• What-If Analysis is a feature of vRealize Operations that allows you to plan for an increase or decrease in workload or capacity requirements in your virtual infrastructure. You can use What-If Analysis to evaluate the demand and supply for capacity on your resources, and to assess the potential risk to your current capacity. You can create scenarios for adding and removing workloads, hosts, clusters, or datastores, and see the impact on the time remaining and capacity remaining scores12.
• Time remaining and capacity remaining are two metrics that measure the available capacity in your environment. Time remaining is the estimated time until a resource runs out of capacity based on the current utilization and growth trends. Capacity remaining is the percentage of unused capacity that is available for future growth. Both metrics are calculated for CPU, memory, disk space, and network bandwidth resources34.
• By using What-If Analysis, you can accomplish the goal of determining how many more ESXi servers are needed to increase the time remaining and capacity remaining scores. You can create a scenario for adding ESXi servers to a cluster or a datacenter, and specify the number, type, and configuration of the servers. You can then see the projected time remaining and capacity remaining scores for the cluster or the datacenter after adding the servers. You can also compare the results with the current scores and the recommended scores. You can adjust the number of servers until you reach the desired scores5 .

References:

1: What-If Analysis: Modeling Workload, Capacity, or Migration Planning 2: Create a What-If Scenario 3: [Capacity Overview - VMware Docs] 4: [Time Remaining and Capacity Remaining Metrics] 5: [Add Hosts to a Cluster or Datacenter Scenario] : [View the Results of a What-If Scenario] : vRealize Operations Manager User Guide : 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]

VMware Tools is a base requirement of the virtual machine for non-credential based service discovery in a virtualization environment using vRealize Operations. Non-credential based service discovery leverages VMware Tools to discover services running on the virtual machines without requiring credentials. VMware Tools is a suite of utilities that enhances the performance and management of the virtual machines. It includes a service discovery plugin that enables vRealize Operations to collect information about the services and processes running on the virtual machines. The service discovery plugin uses netstat or ss commands to identify the services and their dependencies. VMware Tools also provides other benefits such as improved network and graphics performance, time synchronization, graceful power operations, and more. Therefore, VMware Tools is a base requirement of the virtual machine for non-credential based service discovery in vRealize Operations. References: Credential-Less Service Discovery with vRealize Operations; Service Discovery with VMware vRealize Operations; Service and Application Discovery

According to the VMware vRealize Operations Install and Configure Guide1, when upgrading the vRealize Operations cluster via the Administration UI, the cluster status should change from offline to online after the upgrade process is completed. However, if the cluster status remains offline or fails during the upgrade, the administrator can use the Finish Installation option to resume the upgrade process. The Finish Installation option attempts to bring the cluster online and complete the upgrade. The administrator can monitor the progress of the upgrade from the Administration UI or the Cluster Management page.

The other options are not suitable for managing this problem and continuing the installation process. The Rollback Installation option is used to revert the cluster to the previous version of vRealize Operations, not to resume the upgrade process. The Rollback Installation option is only available if the cluster is online and the upgrade has failed. The administrator should not manually take the cluster offline, as this would interrupt the upgrade process and cause data loss or corruption. References:

• 1: VMware vRealize Operations Install and Configure Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-installation-and-configuration-guide.pdf, page 54-55, 58-59

 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

• Workload Optimization 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 Optimization 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:
• Therefore, the configuration that proactively moves workloads so that the resource utilization ensures maximum headroom for all resources is Balance.

References:

1: vRealize Operations - VMware 2: vRealize Operations Manager User Guide 3: Workload Optimization Details - VMware Docs 4: Workload Optimization in vRealize Operations Manager : [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]

The configuration that was sized using the vROps sizing tool is High Availability. High Availability is a feature of vRealize Operations that allows the cluster to tolerate the failure of one or more nodes, and to ensure the continuity and availability of the vRealize Operations services1. High Availability can be enabled or disabled in the Admin UI of vRealize Operations, and it requires at least two nodes in the cluster2. The vROps sizing tool is a web-based tool that helps the administrator to estimate the size and the resources needed for a vRealize Operations deployment, based on the number and the type of the objects to be monitored3. The vROps sizing tool provides different sizing options, such as Extra Large, Large, Medium, Small, and Extra Small, and shows the specifications and the costs for each option. The vROps sizing tool also allows the administrator to select the configuration mode, such as High Availability, Continuous Availability, Stretched Cluster, or Fault Tolerance, and shows the impact of the mode on the sizing and the resources4. The image that was sent with the question shows the output of the vROps sizing tool, with the configuration mode set to High Availability. The image shows the recommended size as Medium, with 2 nodes, 5564 metrics, and 980812 properties. The image also shows the other sizing options, such as Extra Large, Large, Small, and Extra Small, with their respective specifications and costs. Therefore, the configuration that was sized using the vROps sizing tool is High Availability. Continuous Availability (option B) is not the correct answer, as it is a different configuration mode that allows the cluster to tolerate the failure of an entire site, and to ensure the zero data loss and the near-zero downtime of the vRealize Operations services5. Continuous Availability requires at least four nodes in the cluster, and it uses synchronous replication between the sites. The image does not show the configuration mode as Continuous Availability, nor the number of nodes as four. Stretched Cluster (option C) is not the correct answer, as it is a different configuration mode that allows the cluster to span across two sites, and to ensure the load balancing and the disaster recovery of the vRealize Operations services. Stretched Cluster requires at least four nodes in the cluster, and it uses asynchronous replication between the sites. The image does not show the configuration mode as Stretched Cluster, nor the number of nodes as four. Fault Tolerance (option D) is not the correct answer, as it is not a configuration mode that is supported by vRealize Operations. Fault Tolerance is a feature of vSphere that provides continuous availability for a virtual machine by creating and maintaining a secondary virtual machine that is identical to the primary virtual machine. Fault Tolerance is not applicable to vRealize Operations, as it does not support the clustering and the scalability of the vRealize Operations nodes. References:

• 1: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 12.
• 2: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 13.
• 3: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 15.
• 4: vRealize Operations Manager Sizing - VMware, VMware, 2021, 1.
• 5: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 14.
• [6]: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 16.
• [7]: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 14.
• [8]: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 17.
• [9]: vSphere Availability, VMware, 2021, p. 9.

 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

 The support bundle that the customer should send that fits the bandwidth constraints is the light-support bundle from all nodes. A support bundle is a collection of logs, configuration files, and diagnostic information that can be used by VMware support to troubleshoot and resolve issues with vRealize Operations1. A support bundle can be generated from the Admin UI of vRealize Operations, and it can include information from the primary nodes, the replica nodes, and the remote collectors2. A support bundle can be either full or light, depending on the amount and type of information that is included. A full-support bundle contains all the logs, configuration files, and diagnostic information that are available, and it is recommended for most cases. A light-support bundle contains only the essential logs, configuration files, and diagnostic information that are needed for basic troubleshooting, and it is recommended for cases where the bandwidth is limited or the issue is not complex3. A light-support bundle is smaller in size than a full-support bundle, and it can be generated faster and transferred easier. A light-support bundle from all nodes includes the information from the primary nodes, the replica nodes, and the remote collectors, and it can help VMware support to identify the cause of the erratic behavior and the role of the remote collectors. A full-support bundle from the primary nodes only (option A) or a light-support bundle from the primary nodes only (option B) are not the best choices, as they do not include the information from the replica nodes and the remote collectors, which may be relevant for the issue. A full-support bundle from all nodes (option C) is not the best choice, as it is larger in size than a light-support bundle, and it may exceed the bandwidth constraints or take longer to generate and transfer. References:

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

To monitor VMware Site Recovery Manager with vRealize Operations, the administrator must download and install the vRealize Operations Management Pack for VMware Site Recovery Manager, which is a software package that extends the functionality of vRealize Operations and provides dashboards, alerts, and metrics for Site Recovery Manager objects and services1. The management pack can be downloaded from the VMware Marketplace2 or the Site Recovery Manager download page3. After downloading the management pack, the administrator must install it by using the vRealize Operations interface and upload the PAK file4. Then, the administrator must configure the Site Recovery Manager appliance account in Integrations, which is the section where the administrator can add, edit, or delete accounts for various data sources and adapters5. The administrator must provide the Site Recovery Manager appliance IP address or FQDN, the username and password, and the SSL certificate thumbprint. After configuring the account, the administrator can view the Site Recovery Manager dashboards, alerts, and metrics in vRealize Operations. References: 1: vRealize Operations Management Pack for Site Recovery Manager - VMware 2: VMware Marketplace - View Solution 3: VMware Site Recovery Manager Downloads 4: Installing the Management Pack 5: [Integrations] : [Configuring the Site Recovery Manager Adapter Instance]

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 Cloud Cost Management Guide1, cost drivers are the factors that influence the cost of running a service or a resource. Cost drivers can be based on various parameters, such as hardware, software, labor, power, cooling, etc. Cost drivers can be configured in vRealize Operations to reflect the actual costs of the monitored environment and to generate accurate cost reports and analysis.

One of the types of cost drivers that can be configured in vRealize Operations is Server Hardware. This cost driver allows the administrator to specify the purchase price and date of the physical servers that host the virtual machines. The purchase price and date are used to calculate the depreciation and the residual value of the servers over time. The Server Hardware cost driver has three sub-types: Traditional, Hyper-Converged, and Cloud. Each sub-type has different options and calculations for the cost driver.

The Traditional sub-type is used for servers that have separate storage devices, such as SAN or NAS. The Hyper-Converged sub-type is used for servers that have integrated storage devices, such as vSAN. The Cloud sub-type is used for servers that are hosted by a cloud provider, such as AWS or Azure.

Therefore, the correct answer is A. Server Hardware: Hyper-Converged, as this is the type of cost driver that should be selected by the administrator to configure the cost of the nodes within the VMware vSAN cluster that are being monitored. References:

• 1: VMware vRealize Operations Cloud Cost Management Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-cloud-cost-management-guide.pdf, page 9-10, 15-16

• The troubleshooting workbench is a feature of vRealize Operations that provides a unified and interactive view of the alerts, metrics, events, and logs related to an object or a problem in your environment. You can use the troubleshooting workbench to quickly identify the root cause of an issue, analyze the impact and symptoms, and take corrective actions12.
• The troubleshooting workbench can show the data from other vRealize Suite products when the integration is configured. The integration enables vRealize Operations to collect and display the data from the other products as additional sources of information and context for troubleshooting purposes. The integration also enables vRealize Operations to launch the other products from the troubleshooting workbench to perform further analysis or actions34.
• The other vRealize Suite product that can show its data in the troubleshooting workbench when the integration is configured is vRealize Network Insight. vRealize Network Insight is a product that provides visibility and analytics for network and security across physical, virtual, and cloud environments. It helps you to plan, operate, troubleshoot, and optimize your network and security infrastructure, as well as ensure compliance and security posture56.
• When vRealize Operations is integrated with vRealize Network Insight, you can see the network and security data from vRealize Network Insight in the troubleshooting workbench. For example, you can see the network flows, firewall rules, network paths, and network health of the objects or problems that you are troubleshooting. You can also launch vRealize Network Insight from the troubleshooting workbench to perform deeper network and security analysis or actions .

References:

1: Troubleshooting Workbench - VMware Docs 2: Use the Troubleshooting Workbench 3: Integrate vRealize Operations with Other Products - VMware Docs 4: Launch Other Products from vRealize Operations Manager 5: vRealize Network Insight - VMware 6: vRealize Network Insight User Guide : [vRealize Network Insight Integration - VMware Docs] : [Use vRealize Network Insight Data in vRealize Operations Manager] : [vRealize Operations Manager User Guide] : [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]

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.0 2: Business Intent Workspace 3: Self-Driving all the way to the Host? Oh yeah Host Based Placement …

Single sign-on (SSO) is typically integrated with vSphere and vRealize Operations Manager to control user access and permissions. By using SSO, the administrator can leverage the existing vSphere permissions to automatically ensure users have appropriate access to vSphere objects within vRealize Operations Manager without having to manage separate permissions or access lists.

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

The Object List widget (A) is used to select objects. Once an object is selected, the Object Relationship widget (D, E) shows the relationship map of this selected object. To fulfill the requirement that the Alert List widget (F, G, H) should only show the active alerts for the selected object, the selection output of the Object List widget must be connected to both the Object Relationship and Alert List widgets.

Thus, you need to connect the output of the Object List widget (point B) to the input of the Object Relationship widget (point E), and also to the input of the Alert List widget (point G). This setup ensures that selecting an object in the Object List widget will update both the Object Relationship map and the Alert List with the relevant information for the selected object.

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

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: = 2 Capacity Optimization for Your Managed Environment - VMware Docs, 1 Policies - VMware Docs

A list view displays information about specific objects in a tabular format. You can select the object type, the metrics or properties to display, and the sorting and filtering options for the table. A list view is useful for comparing data across multiple objects or for exporting data to a CSV file. References:

• Create and Configure a View
• [List View]

 According to the vRealize Operations Sizing Guidelines, the supported node configurations during installation are Large, Very Large, and Medium. These are the default configurations that VMware offers based on the number of objects and metrics to be monitoredby vRealize Operations. Each configuration has a different amount of vCPU, memory, disk space, and network requirements. The administrator can choose the configuration that best suits the existing infrastructure and the expected growth of the environment1.

The other options are not supported node configurations during installation. Tiny and Small are not valid configurations for vRealize Operations 8.x and later versions. These configurations were available for vRealize Operations 6.x and 7.x versions, but they are not recommended for production environments due to their limited capacity and performance2. No limit is not a configuration option, but a statement that indicates that there is no upper limit on the number of nodes that can be added to a vRealize Operations cluster. However, the number of nodes depends on the node configuration, the network latency, and the data source type3.

References: 1: vRealize Operations 8.0.x Sizing Guidelines (75162) - VMware 2: vRealize Operations Manager 7.5 Sizing Guidelines (67752) 3: vRealize Operations 8 - VMware Docs

 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 Drivers 2: VM Pricing with vRealize Automation 8.1 and vRealize Operations 8.1 3: License Cost Driver 4: Storage Cost Driver

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

According to the VMware vRealize Operations User Guide1, an alert is a notification that indicates a potential or existing problem in the monitored environment. An alert consists of the following components:

• Threshold: A value that defines the normal range of a metric or property. When the value exceeds or falls below the threshold, a symptom is generated.
• Symptom: A condition that indicates a deviation from the normal behavior of an object. A symptom can be based on a metric, a property, a message, or a fault. A symptom can be associated with one or more alert definitions.
• Alert definition: A rule that defines the criteria and the severity for generating an alert. An alert definition specifies the symptoms, the impacted object types, the alert type, and the alert sub-type.
• Recommendation: A suggested action that can help to resolve or prevent the problem that triggered the alert. A recommendation can include a link to a related topic in the documentation or an external URL.An alert definition can have one or more recommendations.

Therefore, the correct answer is C. Recommendation, as this is the alert component that provides instructions that would resolve the triggered alert. References:

• 1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 19-21

• SSH enabled on an ESXi host (Option C) can be a security concern if not properly managed, as it can provide broad access to the host.
• A connected Floppy drive (Option D) can be a risk as it could be used to introduce unauthorized data or software into the VM.
• Allowing Promiscuous Mode (Option F) on a Distributed Port Group can be a security risk as it allows all virtual machines connected to the port group to see all network traffic, which is generally not recommended in secure environments.

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.

Remote Checks are a type of Telegraf plugin that allow you to monitor the availability and performance of remote services or endpoints from the Telegraf agent installed on a virtual machine. You can configure Remote Checks from the Manage Telegraf Agents page in vRealize Operations. There are two types of Remote Checks available: ICMP and TCP. ICMP (Internet Control Message Protocol) checks use ping commands to test the connectivity and response time of a target IP address or hostname. TCP (Transmission Control Protocol) checks use socket connections to test the connectivity and response time of a target IP address or hostname and port number. SMTP (Simple Mail Transfer Protocol), FTP (File Transfer Protocol), and RDP (Remote Desktop Protocol) are not Remote Checks, but they are Application Services that can be discovered and monitored by the Telegraf agent using other plugins. References:

• Additional Operations from the Manage Telegraf Agents Page
• Telegraf Agent Remote Check
• Checking SSL/TLS Certificate Validity Period using vRealize Operations Application Monitoring
• Automating App Monitoring
• vRealize-Automated-Install-of-Telegraf-Agent

To add an additional data node to the existing vRealize Operations cluster, you need to deploy a new data node from the Administration Ul. A data node is a node that collects, stores, processes, and analyzes data from your environment. You can expand an existing installation to add a data node by following these steps1:

• In a Web browser, navigate to the name or IP address of the node that will become the data node. The setup wizard appears, and you do not need to log in to vRealize Operations.
• Click Expand an Existing Installation.
• Click Next.
• Enter a name for the node (for example, Data-1).
• From the Node Type drop-down, select Data.
• Enter the FQDN or IP address of the primary node and click Validate.
• Select Accept this certificate and click Next.
• Verify the vRealize Operations administrator username of admin.
• Enter the vRealize Operations administrator password.
• Click Next, and click Finish.

The other options are not correct because they do not deploy a new data node from the Administration Ul. Option A is incorrect because cloning an existing data node is not supported and may cause data inconsistency. Option C is incorrect because deploying a new virtual appliance from an OVF file is not enough to add a data node to the cluster. You still need to configure the node type and join the cluster from the Administration Ul. Option D is incorrect because enabling High Availability in the Administration Ul does not add a data node to the cluster. It only creates a replica of the primary node for failover purposes. References: Expand an Existing Installation to Add a Data Node

 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 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 super metric is a mathematical formula that contains one or more metrics or properties for one or more objects. It can be used to create custom metrics that are specific to your environment and can help you gain deeper insights into the performance and health ofyour infrastructure1. Super metrics can be applied to any object type that contains the objects or metrics involved in the formula2.

Option A is a valid super metric, as it calculates the average CPU usage of VMs within a Datacenter, which is an object type that contains VMs as child objects. The formula for this super metric could be something like avg(${this, metric=cpu|usage_average, depth=1}), which means the average of the CPU usage average metric for all the child objects of the current object3.

Option D is also a valid super metric, as it counts the number of Non-Windows VMs in a vSphere cluster, which is an object type that contains VMs as child objects. The formula for this super metric could be something like count(${this, metric=guestfilesystem|osType, depth=1, where=not contains windows}), which means the count of the guest OS type metric for all the child objects of the current object, where the value does not contain the word windows3.

Option B is not a valid super metric, as it involves the difference of CPU utilization for each VM between two defined time stamps, which is not a metric or property that can be used in a super metric formula. Super metrics can only use metrics or properties that are collected by vRealize Operations, not arbitrary time stamps2.

Option C is not a valid super metric, as it involves string operators that are valid to be used with mathematical calculations in a function, which is not a metric or property that can be used in a super metric formula. Super metrics can only use numerical values, not string values, in mathematical calculations2.

Option E is not a valid super metric, as it involves the average SCSI count with disk size of VMs within an ESXi host, which is not a metric or property that can be used in a super metric formula. Super metrics can only use metrics or properties that are available for the object type that the super metric is assigned to, and the SCSI count and disk size are not available for the ESXi host object type2.

References:

• My Top 15 vRealize Operations Super Metrics - VMware Blogs
• Configuring Super Metrics - VMware Docs
• vRealize Operations 8.10 - Create Super Metric - Virtualization Blog

 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.