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

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

The regulatory, standards-based compliance pack that is available in vRealize Operations is the CIS Security Standards. The CIS Security Standards are a set of best practices and recommendations for securing IT systems and data against cyberattacks.The CIS Security Standards are developed and maintained by the Center for Internet Security (CIS), a nonprofit organization that provides cybersecurity resources and guidance to organizations and individuals1. The vRealize Operations Compliance Pack for CIS provides alerts, policies, and reports to validate the vSphere resources against the CIS hardening guide.The following resources are being validated using this content: ESXi Host, Virtual Machine, vCenter Server, Distributed Switch, Distributed Port Group, and Distributed Firewall2.The vRealize Operations Compliance Pack for CIS can be downloaded and installed from the VMware Marketplace3. The Sarbanes-Oxley Act (SOX) (option A) is not a regulatory, standards-based compliance pack that is available in vRealize Operations. SOX is a federal law that regulates the financial reporting and auditing of public companies in the United States.SOX does not provide specific technical guidelines or benchmarks for securing IT systems and data4. The Common Vulnerabilities and Exposures (CVE) (option B) is not a regulatory, standards-based compliance pack that is available in vRealize Operations. CVE is a list of publicly known cybersecurity vulnerabilities and exposures that are assigned unique identifiers and descriptions.CVE does not provide specific security standards or recommendations for securing IT systems and data5. The General Data Protection Regulation (GDPR) (option D) is not a regulatory, standards-based compliance pack that is available in vRealize Operations. GDPR is a legal framework that regulates the collection, processing, and transfer of personal data of individuals in the European Union and the European Economic Area. GDPR does not provide specific technical guidelines or benchmarks for securing IT systems and data.References:

1: CIS Security Standards - cisecurity.org, CIS, 2021, [7].

2: vRealize Operations Compliance Pack for CIS - VMware Marketplace, VMware, 2021,1.

3: vRealize Operations Manager User Guide, VMware, 2021, p. 237.

4: Sarbanes-Oxley Act (SOX) - investopedia.com, Investopedia, 2021, [8].

5: Common Vulnerabilities and Exposures (CVE) - cve.mitre.org, MITRE, 2021, [9].

[6]: General Data Protection Regulation (GDPR) - ec.europa.eu, European Commission, 2021, [10].

[7]: CIS Security Standards - cisecurity.org, CIS, 2021, [7].

[8]: Sarbanes-Oxley Act (SOX) - investopedia.com, Investopedia, 2021, [8].

[9]: Common Vulnerabilities and Exposures (CVE) - cve.mitre.org, MITRE, 2021, [9].

[10]: General Data Protection Regulation (GDPR) - ec.europa.eu, European Commission, 2021, [10].

A super metric is a mathematical formula that contains one or more metrics or properties for one or more objects.It can be used to create custom metrics that are specific to your environment and can help you gain deeper insights into the performance and health of your infrastructure1.Super metrics can be applied to any object type that contains the objects or metrics involved in the formula2.

Option A is a valid super metric, as it calculates the average CPU usage of VMs within a Datacenter, which is an object type that contains VMs as child objects.The formula for this super metric could be something likeavg(${this, metric=cpu|usage_average, depth=1}), which means the average of the CPU usage average metric for all the child objects of the current object3.

Option D is also a valid super metric, as it counts the number of Non-Windows VMs in a vSphere cluster, which is an object type that contains VMs as child objects.The formula for this super metric could be something likecount(${this, metric=guestfilesystem|osType, depth=1, where=not contains windows}), which means the count of the guest OS type metric for all the child objects of the current object, where the value does not contain the word windows3.

Option B is not a valid super metric, as it involves the difference of CPU utilization for each VM between two defined time stamps, which is not a metric or property that can be used in a super metric formula.Super metrics can only use metrics or properties that are collected by vRealize Operations, not arbitrary time stamps2.

Option C is not a valid super metric, as it involves string operators that are valid to be used with mathematical calculations in a function, which is not a metric or property that can be used in a super metric formula.Super metrics can only use numerical values, not string values, in mathematical calculations2.

Option E is not a valid super metric, as it involves the average SCSI count with disk size of VMs within an ESXi host, which is not a metric or property that can be used in a super metric formula.Super metrics can only use metrics or properties that are available for the object type that the super metric is assigned to, and the SCSI count and disk size are not available for the ESXi host object type2.

References:

My Top 15 vRealize Operations Super Metrics - VMware Blogs

Configuring Super Metrics - VMware Docs

vRealize Operations 8.10 - Create Super Metric - Virtualization Blog

According to the vRealize Operations User Guide1, the Business Intent option allows the administrator to configure vRealize Operations to ensure that workload performance across 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.

Expected Utilization is the workload option that should be included in the scenario to simulate 25% utilization of the resources. Expected Utilization is a percentage value that indicates how much of the allocated resources (CPU, memory, and storage) are expected to be used by the workload. By setting the Expected Utilization to 25%, the administrator can model the impact of adding or removing a workload that consumes 25% of the resources in the datacenter. Memory, Annual Projected Growth, and CPU are not workload options, but workload attributes. Memory and CPU are the amount of resources allocated to the workload, and Annual Projected Growth is the percentage by which the workload is expected to grow each year. These attributes do not directly specify the utilization of the resources by the workload.References:What-If Analysis - Workload Planning: Traditional, section ''How What-If Analysis - Workload Planning: Traditional Works''.vRealize Operations Manager User Guide, section ''Create and Configure Dashboards''.

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

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 Accounts2:Configure a Microsoft Azure Cloud Account in vRealize Operations3:Configure a vCenter Server Cloud Account in vRealize Operations4:Horizon Adapter: [Configure a Service Account for Google Cloud Platform in vRealize Operations] : [Configure a vRealize Automation Instance in vRealize Operations]

According to the VMware vRealize Operations Cloud Cost Management Guide1, cost drivers are the factors that influence the cost of running a service or a resource. Cost drivers can be based on various parameters, such as hardware, software, labor, power, cooling, etc. Cost drivers can be configured in vRealize Operations to reflect the actual costs of the monitored environment and to generate accurate cost reports and analysis.

One of the types of cost drivers that can be configured in vRealize Operations is Server Hardware. This cost driver allows the administrator to specify the purchase price and date of the physical servers that host the virtual machines. The purchase price and date are used to calculate the depreciation and the residual value of the servers over time. The Server Hardware cost driver has three sub-types: Traditional, Hyper-Converged, and Cloud. Each sub-type has different options and calculations for the cost driver.

The Traditional sub-type is used for servers that have separate storage devices, such as SAN or NAS. The Hyper-Converged sub-type is used for servers that have integrated storage devices, such as vSAN. The Cloud sub-type is used for servers that are hosted by a cloud provider, such as AWS or Azure.

Therefore, the correct answer is A. Server Hardware: Hyper-Converged, as this is the type of cost driver that should be selected by the administrator to configure the cost of the nodes within the VMware vSAN cluster that are being monitored.References:

1: VMware vRealize Operations Cloud Cost Management Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-cloud-cost-management-guide.pdf, page 9-10, 15-16

According to the VMware vRealize Operations Reference Materials, the Custom Script option in vRealize Operations is able to calculate measurements on a Guest OS. The Custom Script option allows the administrator to run a script on the Guest OS of a virtual machine and collect the output as a metric. The script can be written in any language that is supported by the Guest OS, such as PowerShell, Bash, or Python. The script can perform any calculation or operation that is required by the administrator, such as checking the CPU load, memory usage, disk space, or application status. The script output can be numeric or text, and it can be displayed in a dashboard, alert, or report. The other options, such as HTTP Check, UDP Check, or TCP Check, are not able to calculate measurements on a Guest OS. They are used to monitor the availability and response time of a web service, a UDP port, or a TCP port, respectively. They do not run any script on the Guest OS, nor do they collect any metric from the Guest OS.References:Custom Script;How to build a per-guest filesystem report in vRealize Operations using the 'Breakdown By' feature;How to Get In-Guest Metrics in vRealize Operations for Horizon 6