5V0-35.21 questions and answers

The frequency at which new services are discovered when using Service Discovery in vRealize Operations is every 5 minutes.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 environment 1.
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 andservices2.Credential-based Service Discovery uses the credentials provided by the administrator to log in to the guest operating system and run commands or scripts to discover the applications and services3.Credential-less Service Discovery collects the information about the services running inside the guest every five minutes4.Credential-based Service Discovery collects the information about the services running inside the guest every 24 hours 5. Therefore, the frequency at which new services are discovered when using Service Discovery in vRealize Operations depends on the method used, but the most frequent one is every 5 minutes for credential-less Service Discovery.
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: Credential-Less Service Discovery with vRealize Operations, VMware, 2020,.4.
5: Service Discovery with VMware vRealize Operations, Brock Peterson, 2021,.5.

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 environment 1. 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 ports 4. 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.

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 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, or Efficiency. 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

According to the VMware vRealize Operations Reference Materials, primary nodes are responsible for managing the cluster configuration and synchronizing data across the cluster. They can also function as NTP servers for the cluster, ensuring that all nodes have the same time settings. Remote collector nodes, replica nodes, and data nodes rely on the primary nodes for NTP settings and cannot act as NTP servers themselves.
References:
vRealize Operations Manager Cluster Node Types
Configuring NTP Settings

According to the vRealize Operations User Guide1, the two statements that accurately characterize reports in vRealize Operations are: A report layout can contain table of contents, cover page, and footer.The report layout defines the appearance and structure of the report, and can include these optional elements to enhance the readability and presentation of the report.
Scheduling of reports can be done hourly, daily, weekly, and monthly.The report schedule defines the frequency and time of the report generation, and can be set to run at regular intervals, such as hourly, daily, weekly, or monthly, or at a specific date and time.
The other statements are not accurate because: Views and Dashboards are not the only data types available for a report.A report can also include other data types, such as alerts, events, metrics, properties, and super metrics.
Only PDF type reports cannot be used to schedule a report generation.A report can be generated in different formats, such as PDF, CSV, or XML, and any of these formats can be used to schedule a report generation.
Reports scheduled for generation can be shared out via email or FTP.A report can be configured to send the generated output to one or more email recipients, or to upload the output to an FTP server.

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

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

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

References:
Capacity Optimization for Your Managed Environment - VMware Docs,.1.Policies - VMware
Docs

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

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 browser.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 not.
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 changes.
Option C is incorrect because there is no Save option when using the troubleshooting workbench, and the administrator cannot save the changes manually 1.
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 system.

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

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

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

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

vRealize Operations analyzes ESXi memory metrics to detect contention indicators. Ballooning occurs when the hypervisor forces guest OS memory reclamation. Swap-In Rate indicates actual memory shortage requiring disk swap operations. Both are strong contention symptoms. CPU Ready (Option D) relates to CPU contention. vMotion activity (Option B) is unrelated unless triggered by DRS. Datastore IOPS (Option E) is storage-related.

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

.According to the VMware vRealize Operations Reference Materials, the allocation model is a capacity model that allows you to define the overcommit ratios for CPU and memory resources for your clusters.
The allocation model helps you to avoid overcommitment for business-critical workloads and to comply with contractual obligations or SLAs. The allocation model calculates the capacity based on the configured overcommit ratios and the reserved capacity for the clusters. In this case, the company policy states that the clusters should never have greater than a 4:1 virtual to physical CPU ratio and a 1:1 virtual to physical memory ratio. Therefore, the allocation model should be configured for those clusters in vRealize Operations with the same overcommit ratios. This way, the capacity analytics will reflect the company policy and help to plan for infrastructure procurement or migrations based on the projection and avoid the risk of capacity shortage and high infrastructure costs. Therefore, option A is correct. The other options are not correct because they are not capacity models that can be configured for the clusters in vRealize Operations.
Option B is not correct because the demand model is a capacity model that calculates the capacity based on the actual demand for resources in the clusters. The demand model does not consider the overcommit ratios or the reserved capacity for the clusters. The demand model aims to drive towards the most efficient utilization of the clusters based on the historical utilization and the projected utilization.
Option C is not correct because the limit model is not a term used in vRealize Operations, but in vSphere.
The limit model is a setting that specifies the upper limit of resources that can be consumed by a virtual machine. Option D is not correct because the reservation model is not a term used in vRealize Operations, but in vSphere. The reservation model is a setting that specifies the minimum amount of resources that are guaranteed to a virtual machine.
References:
Allocation Model for Capacity Management in vRealize Operations 7.5
Capacity Analytics
Configuring Policies

To configure vRealize Operations to operate in Continuous Availability mode, you need to use the.product User Interface -> Administration -> Cluster Management -> Configure Availability.option. This option allows you to enable or disable Continuous Availability for the vRealize Operations cluster, as well as to view and edit the fault domains and node pairs.You can also monitor the status and synchronization of the nodes in each fault domain 12. The other options are not correct because:
The administration User Interface --> System Status --> Configure Availability option does not exist.The administration User Interface only has the following tabs: System Status, Cluster Management, Software Update, and Support.
The administration User Interface -> Architecture -> Configure Availability option does not exist.The administration User Interface does not have an Architecture tab.
The product User Interface -> Administration -> Support -> Configure Availability option does not exist.The Support tab under the Administration menu only has the following options: Logs, Support Bundles, and Support Alerts.
References:
1: Enable Continuous Availability in vRealize Operations.
2: About vRealize Operations Continuous Availability.
3: [vRealize Operations Manager Administration Interface].
4: [Support]

vRealize Operations can make recommendations for increasing time remaining based on the data it receives and these recommendations appear at the bottom of the Capacity Optimization Overview screen.
You might see two options: Option 1 shows what you can achieve by reclaiming resources.Option 2 shows the results of adding capacity. The recommendations for adding capacity depend on which resource is the most constrained in the cluster. For example, if the cluster is running out of memory, the recommendation might be to add memory to the existing hosts or add new hosts with sufficient memory.Similarly, if the cluster is running out of CPU or disk space, the recommendation might be to add CPU or disk space to the existing hosts or add new hosts with sufficientCPU or disk space. Therefore, the possible recommendations for adding capacity in this situation are
B. Add Memory,
C. Add CPU, and
F. Add Disk Space. The other options,
A. Decrease VM Memory,
D. Increase VM CPU, and E.Decrease VM CPU, are not valid recommendations for adding capacity, as they are related to reclaiming resources or rightsizing
VMs.
References:
Optimize Capacity -VMware Add Capacity - VMware

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

The Operational Intent controls how aggressively vRealize Operations performs workload balancing. With intents such as Balance, Moderate, Efficiency, or Consolidate, administrators can define whether vROps is allowed to move workloads across clusters or optimize only within clusters. License Enforcement (Option B) limits placement but does not drive optimization logic. Maintenance schedules (Option C) govern
blackout periods. Capacity buffers (Option D) only influence capacity calculations, not movement rules.

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 consolidation.
References:
1. Optimize Performance with VMware vRealize Operations.
2. Self-Driving Operations by VMware vRealize Operations Datasheet

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

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:
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,page11-13)

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 infrastructure 1. 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 reports 2. 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 metric.
References:
1: Configuring Super Metrics.2: Metrics and Properties Details.3: Supercharge Your vRealize
Operations with Super Metrics

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

Super Metrics are only computed when they are enabled via a policy and assigned to one or more object types. This ensures that vROps knows which objects the Super Metric calculation applies to. Without policy assignment, the metric remains inactive and cannot be queried or displayed. Linking to alert definitions (Option B) or dashboards (Option C) does not trigger metric computation. Dynamic Thresholds (DT) (Option D) apply only after metrics are collected.

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