5V0-35.21 Questions and Answers

 To configure vRealize Operations cost drivers to assign a different cost per GB for different storage tiers, the administrator should use a vSphere tag category, assign different tag values for that category to the different tiers in the vSphere client, and then assign different costs per GB for each tag value. This is because vRealize Operations uses vSphere tags to identify the storage tiers and apply the corresponding cost drivers. vSphere tags are metadata that can be attached to objects in the vSphere inventory, such as datastores, clusters, hosts, VMs, etc. A vSphere tag category is a logical grouping of tags that share a common characteristic, such as storage tier, license type, backup policy, etc. A vSphere tag value is a specific label within a category that can be assigned to one or more objects, such as Tier 1, Tier 2, Tier 3, etc. By using a vSphere tag category and tag values for storage tiers, the administrator can easily classify the datastores into different tiers based on their performance, availability, or other criteria. Then, the administrator can assign different costs per GB for each tag value in vRealize Operations, which will reflect the different storagebase rates for each tier. This way, the administrator can achieve a granular and accurate cost visibility and analysis for the storage resources in vRealize Operations. References: Overview of Cost Drivers; VM Cost with VMware vRealize Operations; Using Tags to Organize Your Inventory

According to the VMware vRealize Operations Reference Materials, the three details that can be configured when creating a custom view are presentation, format, and data. The presentation option allows the administrator to select the view type, such as list, summary, trend, distribution, or text, and the visualization, such as table, chart, or heatmap. The presentation option also allows the administrator to configure the display settings, such as title, legend, labels, colors, and filters. The format option allows the administrator to select the output format, such as PDF, CSV, or XML, and the orientation, such as portrait or landscape. The format option also allows the administrator to configure the header and footer, such as logo, title, date, and page number. The data option allows the administrator to select the subject, which is the object type that applies to the view, and the data, which are the metrics, properties, or tags that are displayed in the view. The data option also allows the administrator to configure the data settings, such as aggregation, transformation, sorting, and grouping. The other options are incorrect because they are either not available or not relevant when creating a custom view. The custom view tag option is not available in the view configuration, but it can be used to filter the views in theview library. The input transformation option is not available in the view configuration, but it can be used to modify the input data for a widget in a dashboard. The subject option is not a separate detail, but a part of the data option in the view configuration. References: Create a View; View Configuration; View Types

According to the VMware vRealize Operations Reference Materials, the Wait Cycle and the Cancel Cycle are the settings that determine how long a symptom condition must be true or false before the symptom is triggered or cancelled. The default cycle for both settings is 5 minutes, which means that each cycle corresponds to one collection interval of 5 minutes. Therefore, if a symptom has a Wait Cycle of 3 and a Cancel Cycle of 2, it will take 15 minutes (3 cycles x 5 minutes) for the symptom to be triggered after the condition becomes true, and 10 minutes (2 cycles x 5 minutes) for the symptom to be cancelled after the condition becomes false. The other options are incorrect because they do not match the calculation based on the given settings and the default cycle. References: Symptom Definition Settings; Alert Definition Best Practices

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

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

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

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

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

References: 1: About vRealize Operations Continuous Availability

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

• 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 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]

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

vRealize Operations Manager supports various notification methods out of the box, including email notifications and integration with third-party systems. Microsoft Teams is one of the platforms supported for notifications, allowing for alerts and updates fromvRealize Operations Manager to be directly sent to a Microsoft Teams channel. This integration facilitates real-time alerting and collaboration within IT teams. However, options like SMS and Slack might require additional third-party plugins or integrations and are not natively supported as out-of-the-box notification types. Remedy, being an IT service management tool, can be integrated but is not a direct notification type.

Suspending an alert is the action that allows the administrator to stop the alert from triggering again while investigating the problem. Suspending an alert also automatically assigns the alert to the user who performed the action1. Suspending an alert does not cancel or disable the alert, but rather pauses the alert evaluation until the user resumes or cancels the alert2. Taking ownership of an alert does not stop the alert from triggering again, but only indicates that the user is responsible for resolving the alert3. Disabling an alert prevents the alert from being generated for any object, which is not recommended unless the alert is no longer relevant or useful4. Canceling an alert removes the alert from the system, which is not appropriate if the alert is still valid and requires investigation. References: 1: Suspend an Alert - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.user.doc/GUID-595146FB-93F7-4F34-A9D3-79144EA7A658.html)  2: Alert Actions - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.core.doc/GUID-F9AF30F3-089B-43A8-8323-F266E51C05B8.html)  3: Take Ownership of an Alert - VMware Docs(https://kb.vmware.com/s/article/2012021)  4: Disable an Alert Definition - VMware Docs(https://www.brockpeterson.com/post/vmware-vrealize-operations-actions) : Cancel an Alert - VMware Docs

The two required components of an alert definition are symptom and action. An alert definition is a configuration that defines the conditions and actions for generating an alert1. An alert is a notification that indicates a potential or existing issue with an object in the environment2. An alert definition consists of the following components3:

• Symptom: A symptom is a condition that indicates a deviation from the normal or expected behavior of an object. A symptom can be based on metrics, properties, events, or messages. A symptom can have a severity level and a wait cycle. A symptom is a required component of an alert definition, as it triggers the alert when it is met.
• Recommendation: A recommendation is a suggestion or a guidance that provides a possible solution or a mitigation for the issue that caused the alert. A recommendation can include a link to a relevant document or a workflow. A recommendation is an optional component of an alert definition, as it helps the user to resolve the alert, but it does not affect the alert generation.
• Action: An action is a task or a workflow that can be executed automatically or manually to resolve the issue that caused the alert. An action can be based on vRealize Orchestrator workflows or vRealize Operations Manager tasks. An action is a required component of an alert definition, as it defines the response for the alert when it is generated.
• Version: A version is a number that indicates the release or the update of the alert definition. A version is an optional component of an alert definition, as it helps the user to track the changes and the compatibility of the alert definition, but it does not affect the alert generation.
• Node: A node is a vRealize Operations Manager instance that is part of a cluster. A node is an optional component of an alert definition, as it helps the user to specify the scope and the source of the alert definition, but it does not affect the alert generation.

Therefore, the two required components of an alert definition are symptom and action, while the other components are optional. References:

• 1: vRealize Operations Manager User Guide, VMware, 2021, p. 93.
• 2: vRealize Operations Manager User Guide, VMware, 2021, p. 91.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 94.

 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

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

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

References:

• Pricing for vRealize Automation 8.x Components in vRealize Operations - VMware Docs
• Pricing Overview - VMware Docs
• Add New Pricing Card - VMware Docs
• Cost Calculation - VMware Docs

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

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

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

 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 catalog1. 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 organization2.

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 catalog1. 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 instance3. 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]

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

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 menu1. 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 panel2. 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 dashboard3. 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 properties4. 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]

• 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]

 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

 These two methods will meet the goal of creating a trust relationship between the cluster and each of these new nodes. Generating passphrases in the administration User Interface of an existing node, and entering them when prompted in each new node is a method that allows the administrator to securely authenticate the new nodes to the cluster. The passphrase is a one-time password that is valid for 24 hours and can be used to add multiple nodes to the cluster. Clicking the Add New Nodes button on the System Status page in the administration User Interface of an existing node is another method that allows the administrator to initiate the process of adding new nodes to the cluster. The administrator can enter the FQDN or IP address of the new node, and then validate the certificate and accept the trust relationship. Clicking the Add New Nodes button on the Cluster Management page in the product User Interface of an existing node is not a valid option, as this button does not exist on that page. Using any local or directory user with the Administrator role in vRealize Operations when prompted in each new node is not afeasible option, as the new node does not have any local or directory users configured yet. Using the vRealize Operations root user name and password when prompted in each new node is not a reliable option, as the root user name and password may not be the same for all the nodes, and may not be known by the administrator. References: Expand an Existing Installation to Add a Data Node, section “Expand an Existing Installation to Add a Data Node”. Add a Node to a vRealize Operations Analytics Cluster, section “Add a Node to a vRealize Operations Analytics Cluster”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.

 According to the VMware vRealize Operations Reference Materials, Service Discovery is a feature that allows you to automatically discover and monitor the services running on your virtual machines. Service Discovery can use two methods: credential-based and credential-less. Credential-based Service Discovery requires you to provide guest credentials for each virtual machine, while credential-less Service Discovery uses VMware Tools to run scripts on the guest operating system without requiring credentials.

For Linux virtual machines, credential-less Service Discovery requires the installation of Telegraf agent, which is a data collection and reporting agent that communicates with VMware Tools. If the Telegraf agent is not installed on the Linux virtual machines, Service Discovery will fail to authenticate and collect data from them. Therefore, option A is correct.

Another requirement for Linux virtual machines is to enable the open-vm-tools-sdmg package, which is a service discovery management pack that allows VMware Tools to runscripts for Service Discovery. If the open-vm-tools-sdmg package is not enabled on the Linux virtual machines, Service Discovery will also fail to authenticate and collect data from them. Therefore, option D is correct.

The other options are not correct because they are not related to the authentication status of Service Discovery. Option B is not correct because the required network ports are not specific to Linux virtual machines, and they are only needed for credential-based Service Discovery. Option C is not correct because the version of VMware Tools does not affect the authentication status of Service Discovery, as long as it supports the credential-less method. Option E is not correct because the Endpoint Operations agent is not required for Service Discovery, and it is used for a different purpose of collecting metrics and properties from the guest operating system and applications. References:

• Service Discovery Overview
• Credential-Less Service Discovery with vRealize Operations
• Install Telegraf Agent on Linux Virtual Machines
• [Enable open-vm-tools-sdmg Package on Linux Virtual Machines]

 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

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

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 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]

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

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

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

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

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 definition1. 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 Warning2. References: 1: Policy Alert Definitions 2: Alert Definition Best Practices

vRealize Operations continuous availability (CA) separates the vRealize Operations cluster into two fault domains, stretching across vSphere clusters, and protects the analytics cluster against the loss of an entire fault domain. A fault domain consists of one or more analytics nodes grouped according to their physical location in the data center. To activate CA, you must have at least one data node deployed, in addition to the primary node and the witness node. The primary node and the data node must reside in different fault domains, and the witness node must reside in a third location. Therefore, the minimum number of fault domains required to achieve vRealize Operations continuous availability with a primary node, data node, and witness node is two. References: About vRealize Operations Continuous Availability; Continuous Availability Considerations

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 canassociate one or more actions with a recommendation, and configure the action to run automatically or manually when the alert is triggered1. References:

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

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

According to the vRealize Operations User Guide1, Business Intent is a feature that allows the administrator to define the performance, efficiency, and consolidation goals for the clusters and hosts in the SDDC, and to specify the maximum amount of cluster resources to be reserved for burst capacity. Business Intent is applied to objects in vRealize Operations using vCenter Server tags, which are key:value labels that allow operators to add meta-data to vCenter Server objects. By tagging VMs, hosts, and/or clusters with specific tags, the administrator can create business-related placement constraints, such as VMs can only be placed on hosts/clusters with matching tags. For example, the tag OS: Linux can indicate a cluster or VM that is assigned to the category OS with a tag name of Linux. vRealize Operations then uses these tags to optimize the placement and balance of the workloads, and to perform automated remediation actions in the event of an issue. The other options are not correct because:

• Groups are not used to apply Business Intent to objects in vRealize Operations. Groups are collections of objects that share common characteristics, such as type, name, location, or relationship. Groups are used to organize objects for monitoring, analysis, alerting, or policy assignment, but not for workload placement or balance1.
• Policies are not used to apply Business Intent to objects in vRealize Operations. Policies are sets of configuration settings that define how vRealize Operations monitors and manages the objects in the SDDC. Policies are used to enable or disable alerts, metrics, properties, symptoms, recommendations, or actions for different types of objects, but not for workload placement or balance1.
• Roles are not used to apply Business Intent to objects in vRealize Operations. Roles are collections of permissions that define what actions a user can perform on the objects in the SDDC. Roles are used to control the access and visibility of the objects for different users, but not for workload placement or balance1. References: 1: vRealize Operations User Guide, pages 57-59, 62-63, 66-67, 70-71.

 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

 Alert recommendations are the remediation options that you provide to your users toresolve the problems that the generated alert indicates. When you add an alert definition that indicates a problem with objects in your monitored environment, add a relevant recommendation. Recommendations can be instructions to your users, links to other information or instruction sources, or vRealize Operations actions that run on the target systems1. Alert recommendations are not always linked to a Knowledge Base article, and they can be created or modified by the user2. References: 1: Defining Alerts in vRealize Operations 2: User Scenario: Monitor and Process Alerts in vRealize Operations Manager

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.

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

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

According to the vRealize Operations Cloud Getting Started guide1, the initial step that the administrator must take to use vRealize Operations Cloud to monitor an on-premises deployment is to deploy a Cloud Proxy on-premises, and pair it with vRealize Operations Cloud. A Cloud Proxy is a virtual appliance that acts as a bridge between the on-premises vCenter instance and the vRealize Operations Cloud instance. It collects data from the vCenter instance and sends it securely to the vRealize Operations Cloud instance. It also enables actions and remote console access from the vRealize Operations Cloud instance to the on-premises vCenter instance. The guide provides the steps to download, deploy, and configure the Cloud Proxy using the vRealize Operations Cloud user interface1. The other options are not correct because:

• Initiating a Cloud Proxy deployment on the cloud console, and pairing it with vRealize Operations Cloud is not a valid step, as there is no such option in the vRealize Operations Cloud user interface. The Cloud Proxy must be deployed on-premises, not on the cloud console1.
• Opening firewall ports to vRealize Operations Cloud from the on-premises vCenter, and then adding the on-premises deployment is not a sufficient step, as it does not establish a secure and reliable connection between the on-premises vCenter instance and the vRealize Operations Cloud instance. The Cloud Proxy is required to facilitate the data collection and communication between the two instances1.
• Deploying a vRealize Operations node on-premises, and pairing it with vRealize Operations Cloud is not a recommended step, as it will introduce additional complexity and overhead in managing the on-premises vRealize Operations node. The Cloud Proxy is a lightweightand easy-to-deploy appliance that does not require any additional licenses or configuration1. References: 1: vRealize Operations Cloud Getting Started guide, pages 9-13.