5V0-35.21 Sample Questions Answers

To achieve the lowest cost in Workload Optimization, the administrator should select the Consolidate option, which will place VMs into as few clusters as possible, but allows for less responsive capacity. This is good for populations with steady demand and may reduce licensing and hardware costs, such as power and cooling1. The Consolidate option is one of the three operational intents that can be selected for Workload Optimization, along with Balance and Moderate2. The Balance option will spread VMs evenly over the available resources, but may move VMs more often. The Moderate option will minimize VM contention, but will not attempt to move VMs to achieve better balance or consolidation1. References: 1: Optimize Performance with VMware vRealize Operations 2: Self-Driving Operations by VMware vRealize Operations Datasheet

According to the VMware vRealize Operations User Guide1, a Super Metric is a custom metric that is derived from one or more existing metrics. A Super Metric can be used to calculate complex formulas, aggregate data across multiple objects, or create new metrics that are not available by default. A Super Metric can be created using the Super Metric Editor in vRealize Operations.

However, before a Super Metric’s data collection may begin, the Super Metric must be enabled in a policy. A policy is a set of rules and settings that determine how vRealize Operations analyzes and manages the objects in the environment. A policy can be applied to one or more object types or groups. To enable a Super Metric in a policy, the administrator must edit the policy, select the Collect Metrics and Properties option, and then select the Super Metric from the list of available metrics. The administrator can also specify the collection level, collection interval, and retention period for the Super Metric.

The other options are not required before a Super Metric’s data collection may begin. Enabling in Alerts, Object Types, or Objects are not necessary steps for collecting Super Metric data. These options are used for different purposes, such as creating alert definitions, defining object relationships, or assigning policies to individual objects. References:

• 1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 35-36, 39-40, 43-44

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.

 Exporting the dashboard from the development instance, and importing the dashboard into the other instance is the correct action to accomplish the goal. This method allows the administrator to share the dashboard configuration file (in JSON format) with other vROps instances, and edit the dashboard in the other instances as needed. Generating a custom URL, setting the expiration to “never expire”, and importing this URL into the other instance is not a valid option, as this method only allows the administrator to share a non-authenticated view of the dashboard, not the dashboard configuration file. Using the Embed option to import the HTML code into the other instances is not a feasible option, as this method only allows the administrator to embed the dashboard into a web page, not to import the dashboard configuration file. Connecting the vROps instances together, and synchronizing the dashboards is not a possible option, as vROps does not support thisfeature. References: Export and Import Dashboards, section “Export and Import Dashboards”. Options for Sharing Dashboards, section “Options for Sharing Dashboards”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.

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]

According to the vRealize Operations User Guide1, the action that the administrator should take to accomplish the goal of configuring vRealize Operations to monitor the new NSX-T installation is to add an NSX-T account under Cloud Accounts. An NSX-T account is a configuration that defines the connection details and credentials of the NSX-T Manager instance that manages the NSX-T components across the vSphere infrastructure. By adding an NSX-T account under Cloud Accounts, the administrator can enable vRealize Operations to collect data from the NSX-T Manager instance and monitor the health, performance, capacity, and configuration of the NSX-T components, such as transport nodes, transport zones, logical switches, logical routers, and firewall rules. The guide provides the steps to add an NSX-T account under Cloud Accounts using the vRealize Operations user interface1. The other options are not correct because:

• Configuring NSX-T account in Integrations is not a valid action, as there is no such option in the vRealize Operations user interface. The Integrations option under Administration is used to configure the integration of vRealize Operations with other VMware products, such as vRealize Log Insight, vRealize Automation, and vRealize Business for Cloud1.
• Configuring NSX-T monitoring under the Cloud Account of the existing vCenter Server of the vSphere infrastructure is not a valid action, as there is no such option in the vRealize Operations user interface. The Cloud Account of the existing vCenter Server is used to monitor the vSphere components, such as clusters, hosts, datastores, and virtual machines, but not the NSX-T components1.
• Adding NSX-T account under Other Accounts is not a valid action, as there is no such option in the vRealize Operations user interface. The Other Accounts option under Administration is used to add accounts for other types of cloud services, such as AWS, Azure, Google Cloud, or Kubernetes1. References: 1: vRealize Operations User Guide, pages 17-18, 21-22, 25-26.

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

• VMware vRealize Operations is a platform that provides self-driving operations management for hybrid and multi-cloud environments. It uses artificial intelligence and machine learning to monitor, troubleshoot, optimize, and automate the performance, capacity, cost, and configuration of applications, infrastructure, and services12.
• Management packs are extensions that provide additional functionality and integration for vRealize Operations. Management packs can enable vRealize Operations to monitor, analyze, and manage third-party solutions, such as applications, databases, storage, network, cloud, and security devices. Management packs can also provide dashboards, reports, alerts, policies, and actions for the third-party solutions34.
• Management packs can be installed and configured by administrators in vRealize Operations. Management packs can be downloaded from VMware Marketplace or from third-party vendors. Management packs can use different methods to collect data from the third-party solutions, such as APIs, agents, or adapters .
• The other options are not used to monitor third-party solutions from vRealize Operations. Inventory is the collection of objects that vRealize Operations manages and monitors, such as hosts, VMs, clusters, datastores, and so on. Authentication sources are the methods that vRealize Operations uses to authenticate users and assign roles, such as local users, LDAP, or vCenter Single Sign-On. Super metrics are custom metrics that are derived from one or more existing metrics using mathematical expressions.

References:

1: vRealize Operations - VMware 2: vRealize Operations Manager User Guide 3: Management Packs for vRealize Operations Documentation 4: An overview of Application Monitoring with vRealize Operations : [vRealize Operations Manager Installation and Configuration Guide] : [vRealize Operations Manager Concepts Guide] : [Inventory Objects in vRealize Operations Manager] : [Authentication Sources in vRealize Operations Manager] : [Super Metrics in vRealize Operations Manager] : [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]

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

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

To view the status of all objects in vRealize Operations, you can create a dashboard by adding widgets or views. You can create and modify dashboards and configure them to meet your environment needs. Widgets are graphical elements that display data and analysis from vRealize Operations. Views are predefined or custom presentations of object data that you can use in dashboards, reports, or alerts. Alerts, recommendations, and reports are not objects that can be used to create dashboards, but they can be displayed or accessed from dashboards. References:

• Create and Configure Dashboards
• Dashboards
• vROPS Dashboards Overview

To enable east/west firewall in VMware Cloud Director Tenant Portal, you need to perform the following steps:

• Login to Customer Organization and go to Networking Section of Tenant Portal. This is where you can access the networking capabilities provided by NSX Data Center for vSphere in your VMware Cloud Director organization virtual data center.
• Go to Edge Gateways and enable firewall on one of the Edge Gateways. This will allow you to configure the edge gateway firewall rules for north/south traffic enforcement and perimeter security functionality. You can also enable other services such as NAT, VPN, load balancing, etc. on the edge gateway.
• Go to Networking and enable Distributed Firewall for one of the Network inside the Network section. This will allow you to configure the distributed firewall rules for east/west traffic isolation and access control. You can also apply security policies and groups to the network and the virtual machines within it.

References: NSX Data Center for vSphere Firewall Configuration in the VMware Cloud Director Tenant Portal; Getting Started with the VMware Cloud Director Tenant Portal

Host-based placement is a feature of Business Intent that allows you to use vSphere tags to match VMs with hosts based on your business needs. For example, you can use host-based placement to enforce license compliance, security isolation, or performance optimization. When you create a host-based placement in a Business Intent, vRealize Operations automatically creates VM groups, host groups, and affinity rules for you to meet your objectives. These affinity rules are DRS ‘must run on’ rules that restrict the placement of VMs to hosts with matching tags. After you confirm the host-based placement, any existing DRS rules that conflict with the newly created affinity rules will be disabled. This is to ensure that the Business Intent is not violated by the DRS rules. You can view the disabled DRS rules in the vSphere Client under the Configure tab of the cluster123. References: 1: Using Host Rules with Business Intent in vRealize Operations 7.0 2: Business Intent Workspace 3: Self-Driving all the way to the Host? Oh yeah Host Based Placement …

To generate a daily email report of a list of VMs that have been provisioned from vRA, you need to follow these steps:

• Create a custom view that displays the VM name, owner, and creation date for the deployments in the defined cluster. You can use the vRealize Automation Reporting - vRA8 deployment resources and statuses sample as a reference1.
• Create a report that uses the custom view as the template and select the output format as CSV or JSON.
• Schedule the report to run daily and set the start date and recurrence to daily (option A).
• In the Email addresses text box, enter the email addresses that must receive the report, and select an outbound rule (option B). You also need to configure an email server in vRealize Automation Service Broker to send notifications2.
• Click on Schedule, select vSphere Hosts and Clusters, expand vSphere World, and select the specific cluster (option E). This will filter the report data to only include the VMs provisioned to the defined cluster.
• Save the report and verify that it is sent to the email recipients as expected.

Option C is not required because the report is sent via email and does not need to be stored in an external location. Option D is redundant because the start date and recurrence are already set in option A. Option F is incorrect because it will include all the VMs in the vCenter, not just the ones in the defined cluster. References:

• Create and Configure Reports
• Send email notifications to Service Broker users
• vRealize Automation Reporting - vRA8 deployment resources and statuses

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

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

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.

 To access the Troubleshoot with Logs dashboard from vRealize Operations, the administrator must configure the vRealize Log Insight integration from the vRealize Operations interface and configure vRealize Operations in vRealize Log Insight. The Troubleshoot with Logs dashboard allows the administrator to view graphs of log events in the environment, or create custom sets of widgets to access the information that matters most. The dashboard requires the integration of vRealize Operations with vRealize Log Insight, which is a log management and analysis tool1. The integration can be done in twoways: by configuring the vRealize Log Insight adapter in vRealize Operations, or by configuring vRealize Operations in vRealize Log Insight. Both methods are necessary to access the Troubleshoot with Logs dashboard and the Logs tab in vRealize Operations2. References: 1: Troubleshoot with Logs Dashboard 2: Configuring vRealize Log Insight with vRealize Operations

 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

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.

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

Remote Collector nodes are a type of vRealize Operations nodes that only gather objects for the inventory, without storing data or performing analysis. Remote Collector nodes can navigate firewalls, interface with remote data sources, reduce the bandwidth across data centers, or reduce the load on the vRealize Operations analytics cluster1. Remote Collector nodes are not part of the analytics cluster, but they are members of the vRealize Operations cluster2.

Data nodes, Primary Replica nodes, and Primary nodes are all part of the analytics cluster and they store data and perform analysis. Data nodes have adapters installed and perform collection and analysis. Primary Replica nodes are replicas of the Primary nodes and provide high availability or continuous availability. Primary nodes are the initial and required nodes in vRealize Operations and manage all other nodes2. References:

• Additional Operations from the Manage Telegraf Agents Page
• About vRealize Operations Cluster Nodes

A cloud account in vRealize Operations is a configuration that enables data collection from a cloud platform or service. vRealize Operations supports various cloud account types, such as vCenter Server, AWS, Azure, Google Cloud Platform, VMware Cloud on AWS, and VMware Cloud on Dell EMC1. VMware Cloud on AWS is a cloud account type that allows you to monitor and manage your VMware Cloud on AWS SDDC resources, such as hosts, clusters, datastores, and virtual machines2. NSX-T and NSX-V are not cloud account types, but network and security solutions that can be integrated with vRealize Operations3 . References: 1: Cloud Accounts in vRealize Operations 2: Configure a VMware Cloud on AWS Cloud Account in vRealize Operations 3: Configure an NSX-T Cloud Account in vRealize Operations : [Configure an NSX-V Cloud Account in vRealize Operations]

According to the VMware vRealize Operations Reference Materials, the component that will be available when a user logs in to the vRealize Operations Product UI is the Dashboards page. The Dashboards page is the main interface of the Product UI, where the user can view and interact with various dashboards that display the data and analysis of the monitored objects and environments. The Dashboards page also allows the user to create and customize their own dashboards, as well as access other features such as alerts, reports, views, and policies. The other options are incorrect because they are not available in the Product UI, but in the Admin UI. The Software Update page, the Certificate management, and the System Status page are all components of the Admin UI, which is a separate interface that provides the administrative and configuration functions for the vRealize Operations cluster. The Admin UI can be accessed by logging in to the master node or the replica node of the cluster, using the admin user account or a user account with the Administrator role. The user who has access only to the Product UI cannot access the Admin UI or its components. References: vRealize Operations Manager Overview; Log in to vRealize Operations Manager; vRealize Operations Manager Administration

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

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

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

 To estimate the monthly cost of running workloads in IBM Cloud, the administrator can use the What-If Analysis feature of vRealize Operations, which allows forecasting the impact of migrating a workload to a public cloud instance such as AWS, IBM Cloud, Microsoft Azure, Google Cloud or to VMware Cloud on AWS1. The administrator can select the Migration Planning option and choose IBM Cloud as the target cloud provider. Then, the administrator can import the existing VMs that support the business-critical applicationfrom the custom group in vRealize Operations and select all machines to be included in the scenario. Finally, the administrator can run the scenario and get the vRealize Operations analysis and assessment of the plan, which includes the cost and capacity information for the IBM Cloud region2. References: 1: What-If Analysis - Migration Planning: Public Cloud 2: Migration Planning

The administrator needs the Active Directory domain administrator account and password to configure service discovery to identify which virtual machines are running Active Directory services. Service discovery is a feature of vRealize Operations that allows the administrator to discover and monitor the applications and services running on the virtual machines in the environment1. Service discovery can be performed using two methods: credential-less and credential-based. Credential-less service discovery uses VMware Tools to query the guest operating system for the list of running processes, and then matches them with a predefined set of signatures to identify the applications and services2. Credential-based service discovery uses the credentials provided by the administrator to log in to theguest operating system and run commands or scripts to discover the applications and services3. Credential-less service discovery can be used for most common applications and services, such as web servers, database servers, or file servers, but it has some limitations, such as not being able to discover clustered or distributed applications, or applications that run on non-standard ports4. Credential-based service discovery can be used for more complex and customized applications and services, such as Active Directory, Exchange, or SharePoint, but it requires the administrator to provide the appropriate credentials for each guest operating system. For Windows operating systems, the credentials must be either a local administrator account or a domain administrator account. For Active Directory services, the domain administrator account is preferred, as it has the necessary permissions to access the Active Directory information and configuration. Therefore, the administrator needs the Active Directory domain administrator account and password to configure service discovery to identify which virtual machines are running Active Directory services. No credentials are needed since credential-less service discovery can be used (option A) is not a correct answer, as credential-less service discovery cannot discover Active Directory services, which require credential-based service discovery. Local Windows administrator account and password (option B) is not a correct answer, as the local administrator account may not have the sufficient permissions to access the Active Directory information and configuration, which require the domain administrator account. Active Directory domain user account and password (option D) is not a correct answer, as the domain user account may not have the necessary permissions to access the Active Directory information and configuration, which require the domain administrator account. References:

• 1: vRealize Operations Manager User Guide, VMware, 2021, p. 237.
• 2: vRealize Operations Manager User Guide, VMware, 2021, p. 238.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 239.
• 4: vRealize Operations Manager User Guide, VMware, 2021, p. 240.
• [5]: vRealize Operations Manager User Guide, VMware, 2021, p. 241.
• [6]: vRealize Operations Manager User Guide, VMware, 2021, p. 242.
• [7]: vRealize Operations Manager User Guide, VMware, 2021, p. 244.

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

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

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

References:

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

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

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

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

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

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

According to the VMware vRealize Operations 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

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)

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

 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.

Continuous Availability (CA) is a feature of vROps that separates the analytics cluster into two fault domains, stretching across vSphere clusters, and protects the analytics cluster against the loss of an entire fault domain. CA requires a witness node to be deployed in the cluster, which acts as a tiebreaker in case of a network partition between the two fault domains. CA ensures that the data stored in the primary node and data nodes in one fault domain is always 100% synced to the replica node and data nodes in the other fault domain. CA is not a disaster recovery solution, but it provides a higher level of availability and data protection than High Availability (HA), which only protects against the loss of a single node. HA creates a replica for the primary node, but does not replicate the data nodes. Therefore, if a whole rack fails, HA may not be able to prevent data loss. Deploying an additional vROps deployment as a standby or configuring remote collector groups are not options that address the requirement of ensuring no monitoring data is lost in the event of a whole rack failure. These options may provide some redundancy or scalability, but they do not guarantee data consistency or availability across fault domains. References: 1: About vRealize Operations Continuous Availability 2: Continuous Availability Considerations 3: About vRealize Operations High Availability 4: High Availability Considerations

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

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

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

 A super metric is a custom metric that you can define using existing metrics and mathematical functions. They allow you to create new metrics that are specific to your environment and can help you gain deeper insights into the performance and health of your infrastructure1. Before enabling a super metric in a policy, you need to associate it to an object type. An object type is a category of objects that share common characteristics, such as hosts, virtual machines, clusters, datastores, etc. By associating a super metric to an object type, you can calculate the super metric for all the objects of that type and display it in the dashboards and reports2. For example, if you create a super metric that calculates the average CPU usage of all the virtual machines in a cluster, you need to associate it to the cluster object type. Then, you can enable the super metric in a policy and apply it to the cluster object or group. This way, you can monitor the average CPU usage of the cluster as a super metric3. References: 1: Configuring Super Metrics 2: Metrics and Properties Details 3: Supercharge Your vRealize Operations with Super Metrics

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

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]