[May 30, 2024] Verified 5V0-35.21 dumps and 150 unique questions [Q16-Q39]

NO.16 An administrator is asked to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance.
Which two steps are needed to accomplish this goal? (Choose two.)

Deploy and configure a Data node.

Deploy and configure a cloud proxy.

Add a vRealize Operations Cloud account.

Deploy and configure a Primary node.

Add a vCenter cloud account.

NO.17 Which is the valid out-of-the-box notification type supported by vRealize Operations Manager?

SMS

Remedy

Microsoft Teams

Slack

NO.18 What is used to monitor third-party solutions from vRealize Operations?

Inventory

Management packs

Authentication sources

Super metrics

NO.19 An administrator discovered a problem in the virtual infrastructure and obtained instructions that would resolve the triggered alert.
Which alert component was used by the administrator?

Threshold

Symptom

Recommendation

Reclamation

NO.20 An administrator has enabled the allocation model in a policy and set the CPU overcommit ratio to 4:1 for all vSphere clusters in a vSphere datacenter.
Why would vRealize Operations report that the cluster has 0 days remaining when the actual CPU overcommit ratio is less than the 4:1 configured value?

The allocation model will always report zero remaining capacity when the actual ratio is less than the configured ratio.

The allocation model does not account for powered off virtual machines.

The CPU demand in the cluster is less than the total CPU capacity.

The CPU demand in the cluster is greater than the total CPU capacity.

The reason why vRealize Operations reports that the cluster has 0 days remaining when the actual CPU overcommit ratio is less than the 4:1 configured value is that the CPU demand in the cluster is greater than the total CPU capacity. The allocation model is a method of calculating the capacity and utilization of resources based on the amount of resources that are allocated to the objects, such as virtual machines, clusters, or datastores. The allocation model allows the administrator to set the overcommit ratio for CPU, memory, or disk space, which is the ratio of the allocated resources to the available resources. The overcommit ratio determines how much the resources can be overcommitted without affecting the performance or availability of the objects1.
When the administrator enables the allocation model in a policy and sets the CPU overcommit ratio to 4:1 for all vSphere clusters in a vSphere datacenter, it means that the administrator allows the CPU resources to be allocated four times more than the availableCPU resources in the clusters. For example, if a cluster has 100 GHz of CPU capacity, the administrator can allocate up to 400 GHz of CPU resources to the virtual machines in the cluster. However, this does not mean that the virtual machines can consume up to 400 GHz of CPU resources without any impact. The actual CPU consumption of the virtual machines depends on the CPU demand, which is the amount of CPU resources that the virtual machines require to run their workloads. The CPU demand can vary depending on the workload type, intensity, and pattern2.
If the CPU demand in the cluster is greater than the total CPU capacity, it means that the virtual machines are requesting more CPU resources than the cluster can provide. This can result in CPU contention, performance degradation, and SLA violations. In this case, vRealize Operations reports that the cluster has 0 days remaining, which means that the cluster has reached its maximum capacity and cannot accommodate any more CPU demand. The cluster has 0 days remaining even if the actual CPU overcommit ratio is less than the 4:1 configured value, because the overcommit ratio only reflects the allocated resources, not the consumed resources. The overcommit ratio does not guarantee that the cluster can support the CPU demand of the virtual machines, but only indicates the potential capacity of the cluster based on the allocation model1.
References: 1: Allocation Model – VMware Docs 2: Demand Model – VMware Docs

NO.21 When should the advanced sizing guide be used instead of the basic sizing guide in the vRealize Operations Manager (vROps) online Sizing tool?

When yROgs High Availability or Continuous Availability features are going to be enabled

When the monitored environment will have more than 16 vSphere clusters

When additional management packs are going to be implemented

When the yROgs analytics nodes will be distributed across more than one physical data center

NO.22 A customer would like to add virtual machines to a non-hyperconverged cluster, and the administrator needs to gauge the impact on a particular cluster.
Which option within the What-If Analysis feature should be used to obtain this information?

Cluster Planning: Traditional

Virtual Machine Planning: Traditional

Infrastructure Planning: Traditional

Workload Planning: Traditional

NO.23 An administrator wants to configure vRealize Operations to operate in Continuous Availability mode for resiliency. The administrator has deployed all required nodes, registered the nodes as members of the vRealize Operations cluster, and must now configure the Continuous Availability mode.
How should this configuration be completed?

The administration User Interface –> System Status –> Configure Availability

The product User Interface -> Administration -> Cluster Management -> Configure Availability

The administration User Interface -> Architecture -> Configure Availability

The product User Interface -> Administration -> Support -> Configure Availability

NO.24 Which type of node in a vRealize Operations (vROps) design allows an administrator to scale out vROps to monitor very large environments?

Remote collectors

Replica Primary nodes

Primary nodes

Data nodes

NO.25 Which two are supported Cloud Account types in vRealize Operations? (Choose two.)

Microsoft Azure

Horizon Connection Server

Google Cloud Platform

vRealize Automation

vCenter Server

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]

NO.26 Which Grouping Option in vRealize Operations allows the configuration of Tiers?

Tags

Roles

According to the vRealize Operations User Guide1, Business Intent is a feature that allows the administrator to define the performance, efficiency, and consolidation goals for the clusters and hosts in the SDDC, and to specify the maximum amount of cluster resources to be reserved for burst capacity. Business Intent is applied to objects in vRealize Operations using vCenter Server tags, which are key:value labels that allow operators to add meta-data to vCenter Server objects. By tagging VMs, hosts, and/or clusters with specific tags, the administrator can create business-related placement constraints, such as VMs can only be placed on hosts/clusters with matching tags. For example, the tag OS: Linux can indicate a cluster or VM that is assigned to the category OS with a tag name of Linux. vRealize Operations then uses these tags to optimize the placement and balance of the workloads, and to perform automated remediation actions in the event of an issue. The other options are not correct because:
Groups are not used to apply Business Intent to objects in vRealize Operations. Groups are collections of objects that share common characteristics, such as type, name, location, or relationship. Groups are used to organize objects for monitoring, analysis, alerting, or policy assignment, but not for workload placement or balance1.
Policies are not used to apply Business Intent to objects in vRealize Operations. Policies are sets of configuration settings that define how vRealize Operations monitors and manages the objects in the SDDC. Policies are used to enable or disable alerts, metrics, properties, symptoms, recommendations, or actions for different types of objects, but not for workload placement or balance1.
Roles are not used to apply Business Intent to objects in vRealize Operations. Roles are collections of permissions that define what actions a user can perform on the objects in the SDDC. Roles are used to control the access and visibility of the objects for different users, but not for workload placement or balance1. References: 1: vRealize Operations User Guide, pages 57-59, 62-63, 66-67, 70-71.

NO.30 An administrator has been tasked with configuring service discovery to identify which virtual machines are running Active Directory services. All virtual machines are running on vSphere 6.5.
Which credentials, if any, are needed for the administrator to complete this task?

No credentials are needed since credential-less service discovery can be used.

Local Windows administrator account and password.

Active Directory domain administrator account and password.

Active Directory domain user account and password.

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.

NO.31 Due to multiple hardware failures, several virtual machines were corrupted and are being restored from a recent backup. One of the corrupted virtual machines was the primary replica node of a large production vRealize Operations Manager cluster.
How should the system administrator resolve this availability issue within vRealize Operations Manager?

Remove the corrupted node, and then disable and re-enable vRealize Operations Manager High Availability to reassign the primary replica role to another existing node in the cluster.

Deploy a new vRealize Operations Manager node, and then add it to the existing cluster.

Clone an existing primary vRealize Operations Manager node, and then add it into the vRealize Operations Manager cluster.

Ask the backup administrator to restore the corrupted primary replica node, and then refresh the nodes from the vRealize Operations Manager administrator interface.

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

NO.32 An administrator is using the troubleshooting workbench in vRealize Operations for troubleshooting purposes.
Which other vRealize Suite product’s data will be shown in this view when the integration is configured?

vRealize Log Insight

vRealize Network Insight

vRealize Automation

vRealize AI Cloud

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]

NO.33 An administrator wants to enable a custom metric configuration file to a scoreboard widget in a dashboard, but after configuring it, the scoreboard does not show the new metrics at all.
Which scoreboard widget configuration option possibly caused this problem?

Refresh content set to On

Self Provider set to Off

Self Provider set to On

Refresh content set to Off

NO.34 An administrator is planning the size of a new vRealize Operations Manager (vROps) platform using the vROps sizing tool. The output of different configurations and sizing information from the tool were modeled for internal design discussion.
Refer to the exhibit:

Which configuration was sized?

High Availability

Continuous Availability

Stretched Cluster

Fault Tolerance

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.

NO.35 Which option in vRealize Operations is able to calculate measurements on a Guest OS?

Custom Script

HTTP Check

UDP Check

TCP Check

NO.36 Which two statements accurately characterize reports in vRealize Operations? (Choose two.)

Views and Dashboards are the only data types available for a report.

Only PDF type reports can be used to schedule a report generation.

A report layout can contain table of contents, cover page, and footer.

Scheduling of reports can be done hourly, daily, weekly, and monthly.

Reports scheduled for generation can only be shared out via email.

NO.37 At which frequency are new services discovered when using Service Discovery in vRealize Operations?

Every 15 minutes

Every 24 hours

Every 5 minutes

Every hour

NO.38 An administrator is asked to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance.
Which two steps are needed to accomplish this goal? (Choose two.)

Deploy and configure a Data node.

Deploy and configure a cloud proxy.

Add a vRealize Operations Cloud account.

Deploy and configure a Primary node.

Add a vCenter cloud account.

According to the vRealize Operations Cloud Getting Started guide1, the two steps that are needed to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance are:
Deploy and configure a cloud proxy. A cloud proxy is a virtual appliance that acts as a bridge between the on-premises vCenter instance and the vRealize Operations Cloud instance. It collects data from the vCenter instance and sends it securely to the vRealize Operations Cloud instance. It also enables actions and remote console access from the vRealize Operations Cloud instance to the on-premises vCenter instance. The guide provides the steps to download, deploy, and configure the cloud proxy using the vRealize Operations Cloud user interface1.
Add a vCenter cloud account. A vCenter cloud account is a configuration that defines the connection details and credentials of the on-premises vCenter instance. It also specifies the cloud proxy that is associated with the vCenter instance. The guide provides the steps to add a vCenter cloud account using the vRealize Operations Cloud user interface1.
The other options are not correct because:
Deploying and configuring a Data node is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A Data node is a component of the vRealize Operations Cloud cluster that stores and processes data. It is managed by the vRealize Operations Cloud service provider and does not need to be deployed or configured by the customer2.
Deploying and configuring a Primary node is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A Primary node is a component of the vRealize Operations Cloud cluster that provides the user interfaceand administration functions. It is managed by the vRealize Operations Cloud service provider and does not need to be deployed or configured by the customer2.
Adding a vRealize Operations Cloud account is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A vRealize Operations Cloud account is a configuration that defines the connection details and credentials of the vRealize Operations Cloud instance. It is used to integrate vRealize Operations Cloud with other VMware Cloud services, such as VMware Cloud on AWS or VMware Cloud Director. It is not related to the on-premises vCenter instance3. References: 1: vRealize Operations Cloud Getting Started guide, pages 9-132: vRealize Operations Cloud Concepts guide, pages 5-63: vRealize Operations Cloud User Guide, pages 17-18.

NO.39 Which three node configurations are supported during installation, according to vRealize Operations Sizing Guidelines? (Choose three.)

Large

Small

Tiny

Very Large

Medium

No limit

Premium VCE Dumps

Premium VCE Dumps

[May 30, 2024] Verified 5V0-35.21 dumps and 150 unique questions [Q16-Q39]

Leave a Reply Cancel reply