5V0-35.21 Sample Questions Answers

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

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

To 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

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

A support bundle is a collection of log and configuration files that can help troubleshoot a vROps issue. To create a support bundle, the system administrator can use the vROps UI and select the option to create a light or full support bundle. A light support bundle includes 24 hours of logs, while a full support bundle includes all available logs and configuration files. For an intermittent issue that occurred in the last 12 hours, a light support bundle should be sufficient to collect the relevant information. The system administrator can also select the cluster nodes that need to be evaluated for support, and download the support bundle in ZIP format for analysis or sending to VMware Technical Support1. The other options are not recommended or efficient ways to collect the relevant information. Collecting the vCenter and vROps primary node logs using SSH and the vm-support utility would not include the logs from the other vROps nodes, and would require manual steps to gather and compress the files. Using the vROps UI to create a full support bundle for ESXi, vCenter, and primary vROps nodes would include unnecessary and excessive data that could slow down the process and consume more disk space. Using SSH to copy the log files from each of the vROps nodes from /var/log/warn & /var/log/messages locations would also require manual steps to gather and compress the files, and would not include the configuration files that could be useful for troubleshooting. References: 1: Create a vRealize Operations Support Bundle

A cloud account is a configuration that enables vRealize Operations to collect data from a cloud platform or service. vRealize Operations supports different types of cloud accounts, depending on the source of the data and the type of the adapter that is used to connect to the cloud platform or service1. Two of the supported cloud account types are Microsoft Azure and vCenter Server.

Microsoft Azure is a cloud platform that provides a range of services, such as compute, storage, networking, database, analytics, and security. vRealize Operations can connect to Microsoft Azure by using the Microsoft Azure Management Pack, which is an adapter that collects data from the Azure Monitor service. The Microsoft Azure cloud account requires the credentials and subscription ID of the Azure account, and the resource groups and regions that are monitored by vRealize Operations2.

vCenter Server is a platform that manages the VMware private cloud components, such as ESXi, NSX-T Data Center, vSAN, and HCX. vRealize Operations can connect to vCenter Server by using the vSphere solution, which is an adapter that collects data from the vCenter Server API. The vCenter Server cloud account requires the credentials and IP address or FQDN of the vCenter Server instance, and the advanced settings that determine the data collection and processing options3.

The other options are not supported cloud account types in vRealize Operations. Horizon Connection Server is a platform that manages the VMware Horizon virtual desktop infrastructure, but it is not a cloud account type. vRealize Operations can connect to Horizon Connection Server by using the Horizon Adapter, which is a separate adapter that does not require a cloud account configuration4. Google Cloud Platform is a cloud platform that provides a range of services, such as compute, storage, networking, database, analytics, and security, but it is not a cloud account type. vRealize Operations can connect to Google Cloud Platform by using the Google Cloud Platform Management Pack, which is an adapter that collects data from the Google Cloud Monitoring service. The Google Cloud Platform Management Pack does not use a cloud account configuration, but a service account configuration, which requires a service account key file and a project ID. vRealize Automation is a platform that automates the delivery and management of IT services across multiple clouds, but it is not a cloud account type. vRealize Operations can connect to vRealize Automation by using the vRealize Automation Management Pack, which is an adapter that collects data from the vRealize Automation API. The vRealize Automation Management Pack does not use a cloud account configuration, but a vRealize Automation instance configuration, which requires the credentials and IP address or FQDN of the vRealize Automation instance.

References: 1: Cloud Accounts 2: Configure a Microsoft Azure Cloud Account in vRealize Operations 3: Configure a vCenter Server Cloud Account in vRealize Operations 4: Horizon Adapter : [Configure a Service Account for Google Cloud Platform in vRealize Operations] : [Configure a vRealize Automation Instance in vRealize Operations]

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

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.

• A compliance alert is an alert that indicates that an object in the environment is not compliant with a predefined or custom compliance standard. A compliance standard is a collection of compliance alerts that are based on a specific security or regulatory guideline, such as the VMware vSphere Security Configuration Guide. A compliance alert is triggered when one or more symptoms that represent the compliance rules are violated by the object12.
• The VMware vSphere Security Configuration Guide is a document that provides prescriptive guidance and best practices for securing vSphere components, such as ESXi hosts, virtual machines, vCenter Server, and vSphere networking. The guide defines several security configuration baselines for different vSphere versions and environments, and provides recommendations and procedures for applying the security settings34.
• The following symptoms could have triggered a compliance alert based on the VMware vSphere Security Configuration Guide:
• The other options are not symptoms that could have triggered a compliance alert based on the VMware vSphere Security Configuration Guide. Transparent Page Sharing is a memory management technique that allows the hypervisor to identify and eliminate redundant memory pages across multiple virtual machines. The guide does not provide any recommendation on the Transparent Page Sharing setting for virtual machines, as it depends on the security and performance requirements of the environment . The SNMP service is a protocol that enables the monitoring and management of network devices. The guide does not provide any recommendation on the SNMP service setting for ESXi hosts, as it depends on the monitoring and management needs of the environment . The Enable 3D Support setting is a feature that allows the virtual machine to use the hardware-accelerated graphics capabilities of the ESXi host. The guide does not provide any recommendation on the Enable 3D Support setting for virtual machines, as it depends on the application and user experience requirements of the environment .

References:

1: Compliance Alerts - VMware Docs 2: Compliance Benchmarks - VMware Docs 3: VMware vSphere Security Configuration Guide 4: VMware vSphere Security Configuration Guide - VMware Docs 5: Lockdown Mode - VMware Docs : [Enable or Disable Lockdown Mode on an ESXi Host - VMware Docs] : [Disable Copy and Paste Operations Between the Guest Operating System and Remote Console - VMware Docs] : [Disable Copy and Paste Operations Between the Guest Operating System and Remote Console - VMware Docs] : [Security Policies for Virtual Switches - VMware Docs] : [Configure Security Policies for a Distributed Port Group - VMware Docs] : [Transparent Page Sharing - VMware Docs] : [Transparent Page Sharing - VMware Docs] : [SNMP Agent - VMware Docs] : [Configure SNMP for ESXi - VMware Docs] : [Hardware-Accelerated 3D Graphics - VMware Docs] : [Enable 3D Support for a Virtual Machine - 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]

According to the VMware vRealize Operations Reference Materials, the users who are imported from an LDAP authentication source can access vSphere and other objects including third-party objects in vRealize Operations, as long as they have the appropriate permissions and roles assigned to them. The LDAP users can use their LDAP credentials to log in to vRealize Operations, and they can view and manage the objects that are within their scope of access. The other options are incorrect because they are either false or irrelevant. The credentials for the LDAP users are not stored in the central Postgres database of vRealize Operations, but in the LDAP server. The LDAP users are allowed to perform any actions in vRealize Operations that are permitted by their roles and permissions. The LDAP user password policy is not set by vRealize Operations, but by the LDAP server. References: Managing Users and Access Control in vRealize Operations; Authentication Sources; Give Administrator Access to AD or LDAP Users

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

The three main categories for reclamation that are available to the administrator in the Reclaim view on the Home Screen navigation are orphaned disks, snapshots, and powered off VMs. The Reclaim view is a feature of vRealize Operations that allows the administrator to identify and reclaim the wasted or unused resources in the environment, such as storage, CPU, and memory1. The Reclaim view shows the potential savings and the actions that can be taken to reclaim the resources for each category. The orphaned disks category shows the virtual disks that are not associated with any virtual machine, and that can be deleted to free up storage space2. The snapshots category shows the snapshots that are older than a specified age, and that can be deleted to free up storage space and improve performance3. The powered off VMs category shows the virtual machines that are powered off for more than a specified period, and that can be deleted or archived to free up storage, CPU, and memory resources4. The unused datastores category (option A) is not a main category for reclamation that is available in the Reclaim view, as it is not a source of wasted or unused resources. The unused datastores are datastores that are not used by any virtual machine or host, and that can be removed from the inventory or assigned to other objects5. The VM disks utilized %10 or less category (option E) is not a main category for reclamation that is available in the Reclaim view, as it is not a source of wasted or unused resources. The VM disks utilized %10 or less are virtual disks that have low utilization, and that can be resized to reduce the allocated storage space6. The unused hosts category (option F) is not a main category for reclamation that is available in the Reclaim view, as it is not a source of wasted or unused resources. The unused hosts are hosts that are not used by any virtual machine or cluster, and that can be removed from the inventory or assigned to other objects. References:

• 1: vRealize Operations Manager User Guide, VMware, 2021, p. 77.
• 2: vRealize Operations Manager User Guide, VMware, 2021, p. 78.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 79.
• 4: vRealize Operations Manager User Guide, VMware, 2021, p. 80.
• 5: vRealize Operations Manager User Guide, VMware, 2021, p. 81.
• 6: vRealize Operations Manager User Guide, VMware, 2021, p. 82.
• [7]: vRealize Operations Manager User Guide, VMware, 2021, p. 83.

Making sure the NFS server allows read-write access to the shared location by the root system account on each cell is the correct way to enable the collection of log bundles from all cells at once. This is because VMware Cloud Director uses the vmware-vcd-support script to collect host log information as well as Cloud Director logs, and this script requires the NFS server to have read-write access to the shared location by the root system account on each cell1. Installing vRealize Log Insight agent on each cell to redirect logs to a centralized location is not a valid option, as vRealize Log Insight is a separate product that does not integrate with VMware Cloud Director. Configuring a syslog server on each of the cells, and requesting the logs from the syslog server is not a feasible option, as it would require manual intervention and coordination to collect the logs from multiple sources. Mapping the log location on the primary cell to a shared folder on each of the other cells in the server group, ensuring they all have read/write rights on the primary is not asufficient option, as it does not address the NFS server configuration that is required for the vmware-vcd-support script to work properly. References: Collecting diagnostic information for VMware Cloud Director (1026312). Preparing the Transfer Server Storage for VMware Cloud Director on Linux.

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

According to the VMware vRealize Operations Reference Materials, the High Availability feature in vRealize Operations cluster must be used for this requirement. The High Availability feature enables the cluster to tolerate one node failure without losing any data or functionality. The High Availability feature works by creating a replica node for each data node in the cluster, and synchronizing the data between them. The replica node acts as a standby node that can take over the role of the data node in case of a failure. The replica node can also serve as a load balancer to distribute the workload among the data nodes. The other options are incorrect because they do not meet the requirement or they are not supported by vRealize Operations. The Remote Collector option is not a cluster feature, but a type of node that can be used to collect data from remote sources and forward it to the cluster. The Remote Collector node does not store any data or perform any analysis, and it cannot replace a data node in case of a failure. The Continuous Availability option is a cluster feature that enables the cluster to tolerate multiple node failures without losing any data or functionality. However, the Continuous Availability feature requires at least two physical locations, and it is not supported for a single location. The Stretched Cluster option is not a cluster feature, but a configuration that allows a cluster to span across two physical locations. The Stretched Cluster option can provide high availability and disaster recovery, but it also requires additional network and storage configuration, and it is not supported for a single location. References: vRealize Operations Cluster and Node Maintenance; Adding High Availability to vRealize Operations; Adding Continuous Availability; Stretched Cluster

Removing the corrupted node, and then disabling and re-enabling vRealize Operations Manager High Availability to reassign the primary replica role to another existing node in the cluster is the correct way to resolve the availability issue within vRealize Operations Manager. This method ensures that the cluster can continue to operate with high availability and continuous availability, as the primary replica node is responsible for providing critical services that cannot be replicated across all cluster nodes, such as Global xDB, NTP server, and GemFire locator. By removing the corrupted node, the administrator can prevent any further issues or conflicts with the cluster configuration. By disabling and re-enabling vRealize Operations Manager High Availability, the administrator can trigger the cluster to select a new primary replica node from the existing data nodes, and synchronize the data and services with the primary node. Deploying a new vRealize Operations Manager node, and then adding it to the existing cluster is not a valid option, as it does not address the primary replica role assignment, and may cause additional problems with the cluster configuration. Cloning an existing primary vRealize Operations Manager node, and then adding it into the vRealize Operations Manager cluster is not a feasible option, as it may result in duplicate node IDs, IP addresses, and hostnames, and may cause conflicts with the cluster configuration. Asking the backup administrator to restore the corrupted primary replica node, and then refreshing the nodes from thevRealize Operations Manager administrator interface is not a reliable option, as it may take a long time to restore the node, and may not guarantee the consistency and integrity of the data and services on the node. References: Remove a Node from a Cluster, section “Remove a Node from a Cluster”. About vRealize Operations Cluster Nodes, section “About vRealize Operations Cluster Nodes”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.

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

According to the vRealize Operations User Guide1, the Business Intent option allows the administrator to configure vRealize Operations to ensure that workload performanceacross the VMware SDDC is the main priority. The Business Intent option enables 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. The vRealize Operations then uses these goals 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:

• The Reclamation option allows the administrator to configure vRealize Operations to identify and reclaim unused or overprovisioned resources in the SDDC, such as CPU, memory, disk space, and snapshots. This option does not directly affect the workload performance or remediation activities1.
• The Operational Intent option allows the administrator to configure vRealize Operations to monitor and alert on the operational health and risk of the SDDC components, such as clusters, hosts, datastores, and virtual machines. This option does not directly affect the workload placement, balance, or remediation activities1.
• The Rightsizing option allows the administrator to configure vRealize Operations to analyze and recommend the optimal CPU, memory, and disk size for the virtual machines in the SDDC, based on their actual utilization and demand. This option does not directly affect the workload performance or remediation activities1. References: 1: vRealize Operations User Guide, pages 63-66.

According to the VMware vRealize Operations User Guide1, tags are labels that can be assigned to objects in vRealize Operations to group them based on common attributes or criteria. Tags can be used to filter, search, and organize objects in vRealize Operations, as well as to define policies, alerts, dashboards, and reports. Tags can also be used to configure tiers, which are logical groups of objects that represent different levels of service or performance in the environment. For example, the administrator can create tiers such as Gold, Silver, and Bronze, and assign tags to the objects that belong to each tier. Then, the administrator can use the tags to apply different policies, alerts, or dashboards to each tier.

One of the grouping options in vRealize Operations that allows the configuration of tiers is Tags. This option allows the administrator to create custom groups based on the tags assigned to the objects. The administrator can select one or more tags to define the membership criteria for the custom group. The administrator can also specify the object type and the adapter type for the custom group. The custom group can then be used to configure tiers in vRealize Operations.

Therefore, the correct answer is A. Tags, as this is the grouping option in vRealize Operations that allows the configuration of tiers. References:

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

Learn more

1blob:https://www.bing.com/6c14f2a9-7cde-47dc-b7eb-396a752a7842 docs.vmware.com2blob:https://www.bing.com/8c146408-5292-4a8c-86cd-275665f6440f vmware.com3blob:https://www.bing.com/8c146408-5292-4a8c-86cd-275665f6440f vmware.com

According to the VMware vRealize Operations User Guide1, business intent is a feature that allows the administrator to define the desired state and behavior of the clusters and hosts in the environment based on business objectives and constraints. Business intent can be used to optimize the placement and balance of workloads across clusters and hosts, as well as to enforce license compliance and availability requirements.

One of the types of business intent that can be configured in vRealize Operations is Business Intent - Clusters. This type of business intent allows the administrator to assign tags to clusters and virtual machines, and then create rules that match the tags to ensure that the virtual machines are placed on the appropriate clusters. For example, the administrator can tag two clusters as Windows and two clusters as Linux, and then tag the virtual machines accordingly. Then, the administrator can create rules that match the Windows tag and the Linux tag, and set the enforcement mode to Mandatory. This will ensure that the Windows workloads only run on the Windows clusters, and the Linux workloads only run on the Linux clusters.

Therefore, the correct answer is B. Business Intent - Clusters, as this is the type of business intent that should be configured by the administrator to achieve the goal of ensuring the workloads only run on their assigned nodes. References:

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

The administrator can use the Reclaim feature in vRealize Operations Manager to identify and reclaim resources from underutilized or powered-off VMs. However, some VMs may have a valid reason to be powered-off or idle for a long period of time, such as SRV-A in this case. To prevent such VMs from being shown as candidates for reclamation, the administrator can exclude them from the Reclaim action. This can be done by selecting the VMs in the Reclaim screen and clicking the Exclude VM(s) button1. Alternatively, the administrator can also customize the Reclamation Settings to adjust the criteria for identifying powered-off, idle, snapshot, and orphaned disk VMs2. References: 1: Run a Reclaim Action 2: Reclamation Settings

vRealize Operations Cloud is the SaaS offering of vRealize Operations that provides the same features and capabilities as the on-premises version, but with the benefits of faster time to value, lower operational costs, and continuous innovation. vRealize Operations Cloud supports near real-time monitoring of your applications and infrastructure, with data collection intervals as low as 20 seconds1. Near real-time monitoring enables you to detect and troubleshoot performance issues, optimize resource utilization, and ensure SLA compliance more effectively. vRealize Operations Cloud also integrates with other VMware Cloud services, such as VMware Cloud on AWS, VMware Cloud on Dell EMC, and VMware Tanzu Mission Control, to provide unified visibility and management across your hybrid and multi-cloud environments2.

The on-premises editions of vRealize Operations (Standard, Advanced, and Enterprise) do not support near real-time monitoring, as the minimum data collection interval is 5 minutes3. Therefore, they are not suitable for scenarios that require faster and more granular data analysis and alerting. The on-premises editions also have different feature sets and licensing models compared to vRealize Operations Cloud4. References:

• vRealize Operations Cloud FAQ
• vRealize Operations Cloud Overview
• vRealize Operations Manager Data Collection
• vRealize Operations Cloud vs. vRealize Operations

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

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

To get application-related data (metrics) from the VM that vRealize Operations doesn’t collect, the administrator can use the custom script feature of the End Point Operations Management agent. The custom script feature allows the administrator to run custom scripts in the end point VM and collect custom data which can then be consumed as a metric. The administrator needs to install the End Point Operations Management agent on the VM, place the appropriate script to the VM, and then configure the agent to call the script from the Manage Agent location for the VM in vRealize Operations. The script metrics are created under an object called Custom Script which is a single object per end point VM. The administrator can view the output for the specific metric in the All Metrics tab1. The Telegraf agent is not used for custom script monitoring, but for application monitoring using predefined plugins2. The script should not be placed in the vRealize Operation Manager, but in the end point VM. References: 1: Custom Script 2: Application Monitoring

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

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

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

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

In VMware vSphere environments, "Business Intent" is a feature in vRealize Operations that allows administrators to align workloads with business requirements. It ensures that specific workloads, like database virtual machines in your scenario, stay on or are moved to designated clusters based on defined business policies. This feature is essential for maintaining operational efficiency and ensuring that resources are optimized according to business needs.

Business intent is a feature that allows you to define the desired state of your clusters based on your business objectives and workload requirements. You can use business intent to specify the cluster placement and resource allocation for your database virtual machines according to their performance, availability, or efficiency needs1. For example, you can create a business intent policy that assigns high priority and high CPU and memoryreservations to your critical database VMs, and places them on a cluster that has the best hardware and network configuration2. Business intent works with vSphere DRS to automatically move and balance your VMs across the clusters that match your policy3.

The other options are not correct because they do not allow you to configure the cluster placement and resource allocation for your database VMs based on your business objectives. Custom group is a feature that allows you to group objects in your environment based on common attributes or relationships, but it does not define the desired state of your clusters. Compliance benchmark is a feature that allows you to assess the security and configuration compliance of your clusters against predefined or custom standards, but it does not define the desired state of your clusters. Operational intent is a feature that allows you to define the operational behavior of your clusters based on your operational objectives and constraints, such as power management, maintenance mode, or fault tolerance, but it does not define the desired state of your clusters. References: Business Intent, Create a Business Intent Policy, vSphere DRS and Business Intent, [Custom Group], [Compliance Benchmark], [Operational Intent]

The type of cost driver that the administrator should configure to allocate the cost of database software across a vSphere cluster that has been licensed is Applications. Applications are software components that run on top of the virtual machines and provide business value. Examples of applications are database software, web servers, middleware, etc. You can assign application costs to VMs based on the type of application they run, such as Oracle, SQL Server, Apache, etc. You can also create custom application types and assign costs to them. By configuring application costs, you can track the expenses of running different types of applications on your private cloud and optimize your resource utilization and budget12. References: 1: Application Cost Driver 2: Costing with VMware vRealize Operations Part 1

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

According to the vRealize Operations Cloud Getting Started guide1, the two steps that are needed to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance are:

• Deploy and configure a cloud proxy. 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.
• Add a vCenter cloud account. A vCenter cloud account is a configuration that defines the connection details and credentials of the on-premises vCenter instance. It also specifies the cloud proxy that is associated with the vCenter instance. The guide provides the steps to add a vCenter cloud account using the vRealize Operations Cloud user interface1.

The other options are not correct because:

• Deploying and configuring a Data node is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A Data node is a component of the vRealize Operations Cloud cluster that stores and processes data. It is managed by the vRealize Operations Cloud service provider and does not need to be deployed or configured by the customer2.
• Deploying and configuring a Primary node is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A Primary node is a component of the vRealize Operations Cloud cluster that provides the user interfaceand administration functions. It is managed by the vRealize Operations Cloud service provider and does not need to be deployed or configured by the customer2.
• Adding a vRealize Operations Cloud account is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A vRealize Operations Cloud account is a configuration that defines the connection details and credentials of the vRealize Operations Cloud instance. It is used to integrate vRealize Operations Cloud with other VMware Cloud services, such as VMware Cloud on AWS or VMware Cloud Director. It is not related to the on-premises vCenter instance3. References: 1: vRealize Operations Cloud Getting Started guide, pages 9-132: vRealize Operations Cloud Concepts guide, pages 5-63: vRealize Operations Cloud User Guide, pages 17-18.

 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

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.

 The Troubleshooting Workbench is a feature in vRealize Operations that helps you perform advanced troubleshooting tasks on an alert or an object. You can look for potential evidences of a problem within a specific scope and time range. The potential evidences are based on three types of data: Alerts, Events, and Property Changes. Alerts show the active and inactive alerts that are related to the object or its peers. Events show the events that are based on a change in the metrics, such as spikes, drops, or anomalies. Property Changes show the changes in the configuration or properties of the object or its peers, such as CPU, memory, or disk allocation. These types of data help you identify the root cause of the issue and take corrective actions. Symptoms and Anomalous Metrics are not considered as potential evidence in the Troubleshooting Workbench, although they may be used to trigger alerts or events. Logs are not displayed in the Troubleshooting Workbench, but they can be accessed from the Logs tab of the object. References: Discovering Potential Evidences Using the Troubleshooting Workbench, Solving Real Problems with vRealize Operations TroubleshootingWorkbench, Troubleshooting Workbench Home Page, vROps 8.0 Troubleshooting Workbench and Blue Medora

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

The cause of this issue is that changes made to scope, time, or potential evidence are not saved after logging out of the vRealize Operations user interface. The troubleshooting workbench feature allows the administrator to perform advanced troubleshooting tasks on an alert or an object by looking for potential evidences of a problem within a specific scope and time range. The administrator can modify the scope, time, or potential evidence in the active session, but these changes are not persistent and are lost when the administrator logs out or closes the browser1. The administrator can see the virtual machine context as a recent search because the recent searches are stored in the browser’s local storage, but the changes made to the troubleshooting workbench are not2.

The other options are not the cause of this issue. Option A is incorrect because the troubleshooting workbench feature is available in all editions of vRealize Operations, and the license edition does not affect the saving of the changes3. Option C is incorrect because there is no Save option when using the troubleshooting workbench, and the administrator cannot save the changes manually1. Option D is incorrect because restoring the vRealize Operations instance from an earlier backup would not affect the changes made to the troubleshooting workbench, as they are not stored in the vRealize Operations database or file system1.

References: 1: Troubleshooting Workbench Home Page 2: Where You Find the Troubleshooting Workbench 3: [vRealize Operations Manager Editions]

 The action that would help achieve the goal of excluding alerts triggered by the test/development VMs, but not other VMs, is to create a policy inherited from the current active policy, set the alert definition state to “Disabled”, and then assign to test/development VMs. A policy is a set of configuration settings that define the behavior and appearance of vRealize Operations for the objects to which it is applied1. A policy can be inherited from another policy, and it can override or customize the settings of the parent policy2. An alert definition is a configuration that defines the conditions and actions for generating analert3. An alert definition can be enabled or disabled in a policy, and it can be assigned to specific object types or groups4. By creating a policy inherited from the current active policy, the administrator can preserve the existing settings for the other VMs, and only modify the alert definition state for the test/development VMs. By setting the alert definition state to “Disabled”, the administrator can prevent the alert from being triggered by the test/development VMs, and avoid the unnecessary noise and notifications. By assigning the policy to the test/development VMs, the administrator can apply the customized settings to the desired objects, and ensure the policy precedence and inheritance. Under Alerts, select Alerts Definitions, and then remove the Symptoms Definition (option B) is not a correct action, as it would affect the alert definition for all the VMs, not just the test/development VMs, and it would also remove the ability to detect the CPU usage issue for the other VMs. On the Environment tab, select all test/development VMs, and then unassign the active policy that is currently assigned to the test/development VM (option C) is not a correct action, as it would not disable the alert definition for the test/development VMs, but rather assign them the default policy, which may have different settings and alert definitions than the current active policy. Under Alerts, select Alerts Definitions, and then set the alert definition to “Disabled” for test/development VMs (option D) is not a correct action, as it would not create a separate policy for the test/development VMs, but rather modify the current active policy, which may affect the other VMs that are using the same policy. References:

• 1: vRealize Operations Manager User Guide, VMware, 2021, p. 51.
• 2: vRealize Operations Manager User Guide, VMware, 2021, p. 52.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 93.
• 4: vRealize Operations Manager User Guide, VMware, 2021, p. 94.
• [5]: vRealize Operations Manager User Guide, VMware, 2021, p. 55.

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.

According to the VMware vRealize Operations User Guide1, an automated action is a predefined or custom action that can be executed automatically when an alert is triggered. An automated action can help to resolve or prevent the problem that caused the alert, or to notify the relevant stakeholders. To allow an automated action to be triggered from an alert, two conditions must be met:

• Within the active policy, the alert definition’s automated setting must be set to enabled. This allows the alert definition to trigger automated actions when the alert criteria are met. By default, the automated setting is disabled for all alert definitions, and must be manually enabled by the administrator.
• The alert must have a recommendation attached to it. A recommendation is a suggested action that can help to resolve or prevent the problem that triggered the alert. A recommendation can include a link to a related topic in the documentation or an external URL. A recommendation can also be associated with an automated action, which can be executedby the system or by the user. An alert definition can have one or more recommendations, but only one of them can be associated with an automated action.

Therefore, the correct answers are B. Within the active policy, the alert definition’s automated setting must be set to enabled. and E. The alert must have a recommendation attached to it, as these are the two conditions that must be met to allow an automated action to be triggered from an alert. References:

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

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

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

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

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

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

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

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

 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]

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

References:

1: Troubleshooting Workbench - VMware Docs 2: Use the Troubleshooting Workbench 3: Integrate vRealize Operations with Other Products - VMware Docs 4: Launch Other Products from vRealize Operations Manager 5: vRealize Network Insight - VMware 6: vRealize Network Insight User Guide : [vRealize Network Insight Integration - VMware Docs] : [Use vRealize Network Insight Data in vRealize Operations Manager] : [vRealize Operations Manager User Guide] : [vRealize Operations Manager Installation and Configuration Guide] : [vRealize Operations Manager Concepts Guide] : [vRealize Operations Manager Administration Guide] : [vRealize Operations Manager Customization and Extensibility Guide] : [vRealize Operations Manager Troubleshooting Guide] : [vRealize Operations Manager API Programming Guide] : [vRealize Operations Manager Certification Exam Guide]