5V0-35.21 VMware vRealize Operations Specialist Questions and Answers

 The advanced sizing guide should be used instead of the basic sizing guide in the vRealize Operations Manager (vROps) online Sizing tool when additional management packs are going to be implemented. The basic sizing guide provides the default sizing recommendations based on the number of objects and metrics collected from the vSphere environment. However, if the monitored environment includes other types of objects and metrics from different sources, such as management packs, the basic sizing guide may not be accurate.  The advanced sizing guide allows the user to specify the number of objects and metrics for each management pack and get a more precise sizing recommendation 1 2 .  References :  1 :  vRealize Operations Sizing Guidelines   2 :  vRealize Operations 8 - VMware Docs

Cost calculation in vRealize Operations is the process of computing the cost of resources and services for your monitored environment. Cost calculation by default occurs daily and whenever there is a change in the inventory or cost drivers values.  You can also trigger the cost calculation manually from the Administration > Cost Calculation page 1 . The default cost calculation interval is every 24 hours, which means that vRealize Operations will update the cost data once a day at the specified time.  You can change the cost calculation interval from the Administration > Management > Global Settings > Cost Calculation page 2 .  References :  1 :  Cost Calculation Status Overview   2 :  Change the Cost Calculation Interval

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 scores 1 2 .

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 resources 3 4 .

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 scores 5  .

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]

 The alert action that the administrator should take to stop the alert from triggering again, unless the problem occurs in the future, is to cancel the alert. Canceling the alert removes the alert from the active alerts list and stops the alert from affecting the state of the object. However, canceling the alert does not resolve the underlying conditions that triggered the alert. Therefore, the administrator should only cancel the alert after investigating and resolving the problem. If the problem occurs again in the future, the alert will be triggered again. To cancel an alert, the administrator can select the alert in the alerts list, click Actions, and click Cancel Alert. Alternatively, the administrator can open the alert details, click Actions, and click Cancel Alert.  References :  Monitoring Alerts in vRealize Operations Manager ;  User Scenario: Respond to an Alert in the Health Alert List

According to the VMware vRealize Operations Install and Configure Guide 1 , 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

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.

 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 features 1 2 .  References :  1 :  Configuring Cloud Proxies in vRealize Operations   2 :  Managing Cloud Proxies in vRealize Operations

https://docs.vmware.com/en/VMware-Aria-Operations/8.12/Configuring-Operations/GUID-5B6169B5-CBB8-4B0F-BAF6-3BF5C2708304.html

References:

1 :  Dashboards in VMware vRealize Operations   2 :  Create a Dashboard   3 :  Widgets in VMware vRealize Operations   4 : [Add a Widget to a Dashboard]  5 : [Top-N Widget] : [Metric Chart Widget] : [Interaction Widget] :  vRealize Operations Manager User Guide  :  vRealize Opera tions 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 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 into the cluster 1 .  References :  1 :  Expand an Existing Installation to Add a Data Node

  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 monitored by 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 environment 1 .

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 performance 2 . 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 type 3 .

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

When creating an alert definition that has multiple symptoms, the triggered symptom that sets the criticality is the most critical symptom. The criticality of an alert definition is the level of severity or urgency that the alert indicates, such as Critical, Immediate, Warning, or Informational.  The criticality of an alert definition is determined by the highest criticality of the symptoms that are included in the alert definition 1 . When an alert is generated, the criticality of the alert is set by the most critical symptom that triggered the alert. For example, if an alert definition has two symptoms, one with a criticality of Critical and one with a criticality of Warning, and both symptoms are triggered, the alert will have a criticality of Critical.  However, if only the symptom with a criticality of Warning is triggered, the alert will have a criticality of Warning 2 .  References :  1 :  Policy Alert Definitions   2 :  Alert Definition Best Practices

To enable High Availability (HA) on a vRealize Operations cluster, the following two options are requirements:

The cluster must have at least one Primary node : The primary node is the first node that is deployed in the cluster and it is responsible for managing the cluster configuration, user interface, and administration functions. The primary node also stores data and performs analytics like any other data node.  Without a primary node, the cluster cannot function properly 1 .

The cluster must have at least one Data node : A data node is a node that collects data from various sources, stores data in its local file system, and performs analytics and alerting functions. A data node also participates in the cluster load balancing and data replication. To activate HA, you must have at least one data node deployed, in addition to the primary node.  This allows the creation of a replica node that can take over the primary node functions in case of a failure 2 .  References :  1 :  About vRealize Operations High Availability   2 :  High Availability (HA)

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

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 achieve the goal of automated remediation, the administrator needs to include two alert components in the alert definitions: recommendations and actions. Recommendations are the remediation options that are provided to the users to resolve the problems that the generated alert indicates. Actions are the vRealize Operations tasks that can be executed on the target systems to automate the remediation process.  The administrator can associate one or more actions with a recommendation, and configure the action to run automatically or manually when the alert is triggered 1 .  References :

Defining Alerts in vRealize Operations

What’s Your Issue? How to Use vRealize Operations Alerts

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 of vRealize Operations that allows the administrator to plan and optimize the workload placement and capacity of the vSphere resources in the environment 1 . 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 compliance 2 .  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 workloads 3 . 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 budget 4 . 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 requirements 5 . 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.

Management packs in VMware vRealize Operations provide capability for expanding the monitoring, troubleshooting, and remediation functionality of SDDC and third party solutions. Administrators can install and configure management packs in a vRealize Operations instance.  You can download Management Packs and End Point Operations Plug-Ins for vRealize Operations from VMware Marketplace 1 .  For detailed information on installing and configuring the Management Pack, refer to the related user guide 2 .  References :  1 :  Management Packs for vRealize Operations Documentation   2 :  List of Management Packs

Data nodes are the type of node in a vRealize Operations (vROps) design that allow an administrator to scale out vROps to monitor very large environments. Data nodes are additional nodes that have all the vROps services installed, such as UI, Controller, Analytics, Collector, and Persistence. Data nodes perform data collection and analysis, and increase the capacity and performance of the vROps cluster. Data nodes can be added or removed as needed to adjust to the changing workload and environment size. Remote collectors are not a type of node in a vROps design, but a separate component that can be deployed to collect data from remote sources and send it to the vROps cluster. Remote collectors do not store data or perform analysis, and do not increase the capacity or performance of the vROps cluster. Replica Primary nodes and Primary nodes are not the type of node that allow an administrator to scale out vROps to monitor very large environments, but the type of node that provide high availability and continuous availability for the vROps cluster. Replica Primary nodes and Primary nodes contain critical services that cannot be replicated across all cluster nodes, such as Global xDB, NTP server, and GemFire locator. Replica Primary nodes and Primary nodes do not perform data collection and analysis, and do not increase the capacity or performance of the vROps cluster.  References :  About vRealize Operations Cluster Nodes , section “About vRealize Operations Cluster Nodes”.  vRealize Operations Manager User Guide , section “Create and Configure Dashboards”.

To discover custom application services running on virtual machines, the administrator needs to install the vRealize Operations Service Discovery Management Pack 1 .  This management pack enables service and application discovery using the Service Discovery adapter, which leverages the Telegraf agent to collect data from the end point VMs 2 .  The administrator can configure the Service Discovery adapter to discover predefined and custom applications and services, and view their relationships and metrics in vRealize Operations 3 . The administrator can also create custom application definitions based on object names, tags, or properties, and import them as XML files.  Configuring a white list is not a valid option, as it is used to filter out unwanted services from discovery.  References :  1 : vRealize Operations Service Discovery Management Pack - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.6/com.vmware.vcom.core.doc/GUID-B9095E9B-7F10-4B2F-95A9-3D54CF5038FF.html)  2 : Service and Application Discovery - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.core.doc/GUID-CC683117-D936-432C-B30B-CCCA08E863FB.html)  3 : Configure Service and Application Discovery - VMware Docs(https://developer.vmware.com/apis/579/vra-advanced-designer/) : Create Application Definition - VMware Docs : Configure White List - VMware Docs

VMware Cloud Services is a platform that provides a unified and consistent way to access and manage VMware Cloud products and services across multiple clouds and regions.  VMware Cloud Services allows you to create and manage Organizations, which are logical units that group users, services, and resources under a common identity and billing account 1 2 .

An Organization Owner is a user role that has full administrative privileges and control over the Organization and its services. An Organization Owner can invite other users to join the Organization and assign them different roles and permissions.  An Organization Owner can also remove users from the Organization or revoke their invitations 3 4 .

An invitation is a request that an Organization Owner sends to a user to join the Organization and access the services. An invitation contains a link that the user can click to accept the invitation and onboard the Organization.  An invitation also specifies the roles and permissions that the user will have in the Organization and its services 5  .

An invitation is valid for 7 days before it is revoked. This means that the user has 7 days to accept the invitation and onboard the Organization, otherwise the invitation will expire and the user will not be able to join the Organization. The Organization Owner can resend the invitation if the user did not accept it within 7 days, or cancel the invitation if the user is no longer needed in the Organization .

References:

1 :  VMware Cloud Services - VMware   2 :  VMware Cloud Services Overview - VMware Docs   3 :  User Roles in VMware Cloud Services - VMware Docs   4 :  Manage Users in VMware Cloud Services - VMware Docs   5 :  Accept an Account Invitation - VMware Docs  : [Invite Users to an Organization - VMware Docs] : [VMware Cloud Services Console User Guide] : [Getting Started with VMware Cloud Services] : [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]

In an out-of-box vRealize Operations (vROps) deployment, the internal components' health status can be checked through the Product UI. Specifically, by navigating to the Dashboards section and accessing the vRealize Operations dashboards, an administrator can view various metrics and statuses related to the health and performance of the vROps components. These dashboards are designed to provide a comprehensive overview of the system's health and are a key feature of vROps for monitoring and managing the VMware environment efficiently.

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 EMC 1 .  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 machines 2 .  NSX-T and NSX-V are not cloud account types, but network and security solutions that can be integrated with vRealize Operations 3  .  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]

According to the vRealize Operations Cluster Management guide 1 , 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 versions 1 .  References :  1 : vRealize Operations Cluster Management guide, pages 3-4.

According to the VMware vRealize Operations Install and Configure Guide 1 , 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

A vRealize Operations support bundle is a collection of log and configuration files that help troubleshoot a vRealize Operations issue.  You can create a support bundle from the vRealize Operations UI or from the command line interface (CLI) of the vRealize Operations nodes 1 2 .

If the vRealize Operations UI is inaccessible, you cannot create a support bundle from the UI. Therefore, option C is not a valid process.  You need to use the CLI method to create a support bundle from an on-premises deployment 3  .

To create a support bundle from the CLI, you need to log in to the vRealize Operations nodes using SSH and run the generateSupportBundle.py script. This script collects the log and configuration files from the nodes and creates a support bundle in ZIP format. You can then download the support bundle from the /storage/vcops/support directory of the nodes .

However, you do not need to log in to each vRealize Operations node and run the script separately. You only need to log in to the Primary node and run the script once. The script will automatically collect the files from all the nodes in the cluster and create a single support bundle. Therefore, option A is not a necessary process. You only need to log in to the Primary node and run the script .

Option B is not a correct process, as it does not use the generateSupportBundle.py script. The /var/log/messages file is not sufficient to gather the correct information for troubleshooting a vRealize Operations issue. You need to use the script to collect all the relevant log and configuration files from the nodes .

Therefore, the process that will gather the correct information successfully is to log in to the vRealize Operations Primary node using SSH, and then run the generateSupportBundle.py script. This is option D.

References:

1 :  vRealize Operations Support Bundles - VMware Docs   2 :  Create a vRealize Operations Support Bundle - VMware Docs   3 :  Create a Support Bundle from the Command Line Interface - VMware Docs  :  Create a Support Bundle from the Command Line Interface - VMware Docs  :  Create a Support Bundle from the Command Line Interface - VMware Docs  :  Create a Support Bundle from the Command Line Interface - VMware Docs  : [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]

 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 Event 1 .  Metric / Property symptoms compare the values of metrics or properties of an object to a static or dynamic threshold 2 .  Fault symptoms detect faults or errors on an object based on the fault events collected by the adapter 3 .  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 symptoms 4 .  References :

Symptom Definitions

Create a Symptom Definition Based on Metrics or Properties

Create a Symptom Definition Based on Fault Events

Alert Definitions

 The option within the What-If Analysis feature that should be used to obtain the information is Workload Planning: Traditional. This option allows the administrator to define scenarios that can potentially add or remove workloads to or from actual data centers or custom data centers.  vRealize Operations models the scenario and calculates whether the desired workload can fit in the targeted data center or custom data center, and how it affects the capacity and performance of the cluster 1 .  The administrator can also specify the profile of the workload, the start and end date of the scenario, and the annual projected growth of the workload 2 .

The other options are not correct, because they do not match the use case of adding virtual machines to a non-hyperconverged cluster.  Cluster Planning: Traditional allows the administrator to define scenarios that can potentially add or remove hosts to or from clusters, and evaluate the impact on the cluster capacity and performance 3 . Virtual Machine Planning: Traditional allows the administrator to define scenarios that can potentially add or remove virtual machines to or from hosts, and evaluate the impact on the host capacity and performance. Infrastructure Planning: Traditional allows the administrator to define scenarios that can potentially add or remove infrastructure components, such as datastores, networks, or adapters, and evaluate the impact on the infrastructure capacity and performance.

References :

What-If Analysis - Workload Planning: Traditional - VMware Docs

What-If Analysis with vRealize Operations 8.0 - VMware Blogs

What-If Analysis - Cluster Planning: Traditional - VMware Docs

[What-If Analysis - Virtual Machine Planning: Traditional - VMware Docs]

[What-If Analysis - Infrastructure Planning: Traditional - VMware Docs]

 To add a custom metric configuration file to a scoreboard widget in a dashboard, the correct process is to create a metric file in XML format, set the scoreboard widget Self Provider to Off, and create a widget interaction with a provider widget. A custom metric configuration file is a file that defines the metrics that the scoreboard widget displays for different object types. The file must be in XML format and follow a specific schema. The file must be uploaded to the vRealize Operations server and selected in the Metric Configuration option of the scoreboard widget. The Self Provider option determines whether the widget shows metrics of the objects selected during editing of the widget or selected on another widget. When the Self Provider option is set to Off, the widget shows metrics of the objects selected on another widget. The widget interaction is a mechanism that allows widgets to communicate with each other and pass data. A provider widget is a widget that provides data to another widget. A receiving widget is a widget that receives data from another widget. To create a widget interaction, the administrator must edit the dashboard and select the provider widget and the receiving widget, and then configure the interaction type and the data to pass. By creating a widget interaction with a provider widget, the administrator can enable the scoreboard widget to display the custom metrics for the objects selected on the provider widget.  References :  How the Scoreboard Widget and Configuration Options Work ;  Question on How to Scoreboard Dashboard - Metric Configuration XML - Max & Avg Metric Values ;  Dashboard widget can set default metric key

According to the VMware vRealize Operations Cloud Cost Management Guide 1 , 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

According to the VMware vRealize Operations Reference Materials, the cloud services console is a unified interface that allows you to access and manage your VMware Cloud services. The Identity & Access Management capability is available in the cloud services console regardless of the subscribed cloud services, as it enables you to manage users, groups, roles, and permissions for your organization. The other capabilities, such as Organization Access Management, Settings, and Cost Insights, are specific to certain cloud services and may not be available for all subscriptions.  References :

Cloud Services Console Overview

Identity & Access Management Overview

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 services 1 .  High Availability can be enabled or disabled in the Admin UI of vRealize Operations, and it requires at least two nodes in the cluster 2 .  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 monitored 3 . 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 resources 4 . 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 services 5 . 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.

 The vSphere Solution’s Default Policy is a policy that is automatically created when you add a vCenter Cloud Account to vROps. This policy applies to all the objects that are discovered and collected by the vSphere adapter. The origin of the settings in this policy is the base settings that are provided by the data adapters and solutions installed in vROps. The base settings are a collective group of rules that apply to all objects, regardless of their type or source. The vSphere Solution’s Default Policy inherits all the base settings by default, and you can modify them to suit your specific needs. The default policy setting is not defined by another administrator, nor is it added during the installation of the vROps management pack for vSphere. The settings of this policy are also not defined during the vROps OVF deployment, as they are determined by the data adapters and solutions.  References :  Default Policy in vRealize Operations ,  Configure VMware SDDC Benchmarks

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 sources 1 2 .  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 ms 3 .

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 node 1 . 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 ms 1 . 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 ms 1 .

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 …

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”.

A metric configuration in vRealize Operations is a collection of metrics that you can apply to one or more widgets in a dashboard. A metric configuration allows you to customize the metrics that you want to display on the widgets, and also to define the color, label, unit, and aggregation type for each metric.  You can create, edit, or delete metric configurations from the Metric Configuration page in the Administration menu 1 .  A metric configuration is not the same as a metric group, which is a predefined set of metrics that you can select from the widget configuration panel 2 . A dashboard navigation is a feature that allows you to link one or more widgets or views in a dashboard to another dashboard, and pass the selected object as a filter to the destination dashboard.  When a dashboard navigation is created, the destination widgets or views are filtered by the selected object from the source dashboard 3 . An alert can be created from the Alert list widget, which displays the alerts for the selected object or group of objects in a dashboard.  You can create an alert by clicking the Add Alert icon on the widget toolbar, and then selecting the alert definition, the object, and the alert properties 4 . Dashboards can be added by installing management packs, which are extensions that provide additional monitoring and management capabilities for various solutions and platforms.  However, dashboards can also be added by creating custom dashboards, importing dashboards from the VMware Marketplace, or cloning existing dashboards.  References :  1 :  Manage Metric Configurations   2 :  Select Metrics for Widgets   3 :  Create Dashboard Navigation   4 :  Create an Alert from the Alert List Widget  : [Create and Configure Dashboards]

 A published catalog is a catalog that is made available for access by organizations outside the VMware Cloud Director installation.  A published catalog can be consumed by a different VMware Cloud Director instance in a different country, as long as the system administrator has enabled external catalog publishing for the organization that owns the catalog, and the remote organization has subscribed to the catalog 1 .  A published catalog can contain vApp templates and media files that are synchronized between the publisher and the subscriber, and can be used to deploy vApps and VMs in the remote organization 2 .

The other options are not correct. A subscribed catalog is a catalog that is created by subscribing to a published catalog from another organization.  A subscribed catalog cannot be shared across VMware Cloud Director instances, as it is dependent on the published catalog 1 . A content library catalog is a catalog that is synchronized with a vSphere content library, which is a container for VM templates, vApp templates, and other types of files.  A content library catalog cannot be shared across VMware Cloud Director instances, as it is specific to a vCenter Server instance 3 . A shared catalog is a catalog that is shared with other users or organizations within the same VMware Cloud Director installation. A shared catalog cannot be shared across VMware Cloud Director instances, as it is limited to the local installation.

References :  1 :  Configure the Catalog Synchronization Settings for VMware Cloud …   2 :  Working with Catalogs - VMware Docs   3 :  Create a Content Library Catalog  : [Share a Catalog]

 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 domain 1 2 . 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 Support 3 .

The administration User Interface - > Architecture - > Configure Availability option does not exist.  The administration User Interface does not have an Architecture tab 3 .

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 Alerts 4 .  References :  1 :  Enable Continuous Availability in vRealize Operations   2 :  About vRealize Operations Continuous Availability   3 : [vRealize Operations Manager Administration Interface]  4 : [Support]

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”.

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 services 1 .  The management pack can be downloaded from the VMware Marketplace 2  or the Site Recovery Manager download page 3 .  After downloading the management pack, the administrator must install it by using the vRealize Operations interface and upload the PAK file 4 .  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 adapters 5 . 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]

According to the vRealize Operations User Guide 1 , the two statements that accurately characterize reports in vRealize Operations are:

A report layout can contain table of contents, cover page, and footer.  The report layout defines the appearance and structure of the report, and can include these optional elements to enhance the readability and presentation of the report 1 .

Scheduling of reports can be done hourly, daily, weekly, and monthly.  The report schedule defines the frequency and time of the report generation, and can be set to run at regular intervals, such as hourly, daily, weekly, or monthly, or at a specific date and time 1 .

The other statements are not accurate because:

Views and Dashboards are not the only data types available for a report.  A report can also include other data types, such as alerts, events, metrics, properties, and super metrics 1 .

Only PDF type reports cannot be used to schedule a report generation.  A report can be generated in different formats, such as PDF, CSV, or XML, and any of these formats can be used to schedule a report generation 1 .

Reports scheduled for generation can be shared out via email or FTP.  A report can be configured to send the generated output to one or more email recipients, or to upload the output to an FTP server 1 .

References :  1 : vRealize Operations User Guide, pages 81-87.

 According to the VMware vRealize Operations User Guide 1 , 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 a list 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

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