VMware 5V0-35.21 Practice Test - Questions Answers, Page 13

Single sign-on (SSO) is typically integrated with vSphere and vRealize Operations Manager to control user access and permissions. By using SSO, the administrator can leverage the existing vSphere permissions to automatically ensure users have appropriate access to vSphere objects within vRealize Operations Manager without having to manage separate permissions or access lists.

vRealize Operations allows for different node sizes when deploying a cluster to suit various environments and scalability needs. The sizes typically include Small, Medium, and Large, and these sizes determine the capacity and performance of each node in a High Availability configuration.

References:

About vRealize Operations Cluster Nodes

High Availability (HA)

vRealize Operations 8.6.0, 8.6.1, and 8.6.2 Sizing Guidelines

To compare the cost of running workloads hosted with two different custom cloud providers, the administrator needs to create two new pricing cards in vRealize Operations. A pricing card is a template that defines the cost of cloud resources, such as compute, storage, network, and services. By creating two pricing cards, one for each custom cloud provider, the administrator can specify the prices for each resource type and apply discounts or markups as needed. The administrator can then use the pricing cards to run a what-if analysis and compare the cost of migrating or scaling workloads to the custom cloud providers. The other options are not correct for comparing the cost of running workloads hosted with two different custom cloud providers. Adding custom cloud providers as cloud accounts is not possible, as vRealize Operations only supports adding public cloud accounts, such as AWS, Azure, or Google Cloud. Inputting prices manually when running a what-if analysis is not efficient, as it would require entering the prices for each resource type and workload every time. Adding two custom cloud providers is not a valid option, as it is not clear how the administrator would define the cost of the cloud resources without using pricing cards.References:Create a Pricing Card,Compare the Cost of Running Workloads on Different Cloud Providers,What-If Analysis

The vRealize Operations sizing tool is a web-based tool that helps you estimate the resources required for deploying and running vRealize Operations in your environment. The tool has two modes: Basic and Advanced. In the basic mode, you only need to enter information about vCenter objects, such as the number of clusters, hosts, virtual machines, and datastores. The tool also asks for the projected growth rate and data retention period for your environment. Based on these inputs, the tool provides recommendations for the node size, cluster size, and disk space for vRealize Operations.The tool also shows the maximum number of objects and metrics that can be collected by the recommended configuration123. Therefore, the attribute that is required for using the vROps sizing tool in basic mode is thenumber of clusters. The other attributes, such as the number of virtual machine disks, vSwitches, and port groups, are not required in the basic mode.However, they can be entered in the advanced mode, along with other data sources, such as management packs, vRealize Automation, vRealize Log Insight, etc., to get a more accurate and customized sizing recommendation123.References:1:Introducing the vRealize Operations Sizing Tool2:vRealize Operations 8.6.0, 8.6.1, and 8.6.2 Sizing Guidelines3:Everything You Need To Know About vRealize Operations Manager Sizing Tool

Cloud Accounts are the connections that allow vRealize Operations Manager to collect data from various cloud platforms and services.vRealize Operations Manager supports several types of Cloud Accounts, such as VMware Cloud, Amazon Web Services, Microsoft Azure, Google Cloud, and Kubernetes1. To monitor all supported environments, the administrator can use any combination of these Cloud Accounts, depending on the cloud services that the company is consuming. However, among the options given, only Amazon Web Services (AWS) and VMware Cloud on AWS are valid Cloud Accounts that can be used in vRealize Operations Manager.AWS is the leading public cloud provider that offers a wide range of compute, storage, networking, database, analytics, and other services2.VMware Cloud on AWS is a hybrid cloud service that delivers a consistent VMware environment on the AWS infrastructure, allowing customers to migrate, extend, and modernize their applications3.Both AWS and VMware Cloud on AWS can be integrated with vRealize Operations Manager by configuring the respective Cloud Accounts and providing the necessary credentials and regions45.

Google Cloud, Alibaba Cloud, and IBM Cloud are also popular public cloud providers that offer various cloud services, but they are not supported as Cloud Accounts in vRealize Operations Manager. Therefore, they cannot be used to monitor the environments in vRealize Operations Manager. To monitor these cloud platforms, the administrator might need to use other tools or methods, such as third-party management packs, custom integrations, or external APIs .References:

Cloud Accounts

Amazon Web Services

VMware Cloud on AWS

Configure an Amazon Web Services Cloud Account in vRealize Operations

Configure a VMware Cloud on AWS Cloud Account in vRealize Operations

[Google Cloud Platform Management Pack for vRealize Operations]

[Alibaba Cloud Monitoring]

[IBM Cloud Monitoring]

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

vRealize Operations provides out-of-the-box compliance packs for various regulatory and standards-based benchmarks, such as PCI, HIPAA, DISA, CIS, and more1. These compliance packs help you assess and report the compliance status of your environment against the best practices and requirements defined by these benchmarks.You can also customize the compliance packs to suit your specific needs or create your own compliance packs2. Among the options given, PCI and HIPAA are the valid out-of-the-box compliance packs available in vRealize Operations.PCI is a compliance pack that helps you ensure the security of cardholder data in your environment3. HIPAA is a compliance pack that helps you protect the privacy and security of health information in your environment.The other options, GDPR, ISO 27017, and FedRAMP, are not out-of-the-box compliance packs in vRealize Operations, although you can create your own compliance packs for them if needed.References:1: Compliance Overview - VMware Docs(https://docs.vmware.com/en/Management-Packs-for-vRealize-Operations/index.html)2: Compliance Pack Management - VMware Docs(https://docs.vmware.com/en/Management-Packs-for-vRealize-Operations/1.0/Compliance-Pack-for-VMware-Sovereign-Cloud/GUID-3DF17387-8399-444F-BD4B-0F2EA9161532.html)3: PCI Compliance Pack - VMware Docs(https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vmware-vrealize-operations-8.2-datasheet.pdf) : HIPAA Compliance Pack - VMware Docs

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