Free VMware 5V0-35.21 Practice Exam with Questions & Answers | Set: 2

 According to the vRealize Operations User Guide1, one of the best ways to quickly identify the underlying problem of slow application VMs is to use the out-of-the-box Performance dashboards that display contention on both VMs and ESXi hosts. These dashboards show the key performance indicators (KPIs) of CPU, memory, disk, and network for the selected objects, and highlight any contention or saturation issues that may affect the performance. The administrator can use these dashboards to drill down into the details of the metrics, alerts, events, and properties of the objects, and isolate the root cause of the problem. The other options are not correct because:

• Under Inventory, selecting Manage Agent, then selecting the VMs, and running Remote Checks on ICMP, HTTP checks is not a helpful action, as it only verifies the connectivity and availability of the VMs, but does not provide any information about the performance or contention of the VMs or the ESXi hosts2.
• Under Report, using Configuration Report - Virtual Machines to list down possible changes that have occurred is not a helpful action, as it only shows the configuration details of the VMs, such as name, UUID, power state, guest OS, CPU, memory, disk, and network, but does not show any performance or contention metrics or alerts of the VMs or the ESXi hosts3.
• Under Administration, choosing Configuration, selecting Object Relationships, and then identifying the VMs and ESXi hosts relationship to generate a correlation of the metric, and finally, isolate the issue is not a helpful action, as it only shows the hierarchical and logical relationships between the objects, such as parent, child, sibling, and peer, but does not show any performance or contention metrics or alerts of the objects4. References: 1: vRealize Operations User Guide, pages 57-59, 62-632: vRealize Operations User Guide, pages 69-703: vRealize Operations User Guide, pages 81-824: vRealize Operations User Guide, pages 84-85.

• A compliance alert is an alert that indicates that an object in the environment is not compliant with a predefined or custom compliance standard. A compliance standard is a collection of compliance alerts that are based on a specific security or regulatory guideline, such as the VMware vSphere Security Configuration Guide. A compliance alert is triggered when one or more symptoms that represent the compliance rules are violated by the object12.
• The VMware vSphere Security Configuration Guide is a document that provides prescriptive guidance and best practices for securing vSphere components, such as ESXi hosts, virtual machines, vCenter Server, and vSphere networking. The guide defines several security configuration baselines for different vSphere versions and environments, and provides recommendations and procedures for applying the security settings34.
• The following symptoms could have triggered a compliance alert based on the VMware vSphere Security Configuration Guide:
• The other options are not symptoms that could have triggered a compliance alert based on the VMware vSphere Security Configuration Guide. Transparent Page Sharing is a memory management technique that allows the hypervisor to identify and eliminate redundant memory pages across multiple virtual machines. The guide does not provide any recommendation on the Transparent Page Sharing setting for virtual machines, as it depends on the security and performance requirements of the environment . The SNMP service is a protocol that enables the monitoring and management of network devices. The guide does not provide any recommendation on the SNMP service setting for ESXi hosts, as it depends on the monitoring and management needs of the environment . The Enable 3D Support setting is a feature that allows the virtual machine to use the hardware-accelerated graphics capabilities of the ESXi host. The guide does not provide any recommendation on the Enable 3D Support setting for virtual machines, as it depends on the application and user experience requirements of the environment .

References:

1: Compliance Alerts - VMware Docs 2: Compliance Benchmarks - VMware Docs 3: VMware vSphere Security Configuration Guide 4: VMware vSphere Security Configuration Guide - VMware Docs 5: Lockdown Mode - VMware Docs : [Enable or Disable Lockdown Mode on an ESXi Host - VMware Docs] : [Disable Copy and Paste Operations Between the Guest Operating System and Remote Console - VMware Docs] : [Disable Copy and Paste Operations Between the Guest Operating System and Remote Console - VMware Docs] : [Security Policies for Virtual Switches - VMware Docs] : [Configure Security Policies for a Distributed Port Group - VMware Docs] : [Transparent Page Sharing - VMware Docs] : [Transparent Page Sharing - VMware Docs] : [SNMP Agent - VMware Docs] : [Configure SNMP for ESXi - VMware Docs] : [Hardware-Accelerated 3D Graphics - VMware Docs] : [Enable 3D Support for a Virtual Machine - VMware Docs] : [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]

To enable High Availability (HA) on a vRealize Operations cluster, the following two options are requirements:

• The cluster must have at least one Primary node: The primary node is the first node that is deployed in the cluster and it is responsible for managing the cluster configuration, user interface, and administration functions. The primary node also stores data and performs analytics like any other data node. Without a primary node, the cluster cannot function properly1.
• The cluster must have at least one Data node: A data node is a node that collects data from various sources, stores data in its local file system, and performs analytics and alerting functions. A data node also participates in the cluster load balancing and data replication. To activate HA, you must have at least one data node deployed, in addition to the primary node. This allows the creation of a replica node that can take over the primary node functions in case of a failure2. References: 1: About vRealize Operations High Availability 2: High Availability (HA)

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.

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.

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 cloud proxy is an appliance that enables vRealize Operations Cloud to collect and monitor data from the on-premises environment. A cloud proxy is deployed as an OVA template on a vCenter Server instance that manages the on-premises resources. A cloud proxy creates a one-way communication between the on-premises environment and vRealize Operations Cloud by uploading data from the remote collectors to the cloud service. A cloud proxy can support multiple vCenter Server accounts and other data sources that are configured in vRealize Operations Cloud1.

The other options are not appliances that are needed to achieve this goal. A reverse proxy is a server that receives requests from clients and forwards them to the origin server. A reverse proxy can provide security, load balancing, caching, and compression functions. A reverse proxy is not used to create a one-way communication between the on-premises environment and vRealize Operations Cloud2. A web proxy is a server that acts as an intermediary between a web browser and the internet. A web proxy can provide anonymity, filtering, caching, and security functions. A web proxy is not used to create a one-way communication between the on-premises environment and vRealize Operations Cloud3. A VMware proxy is not a valid appliance in vRealize Operations.

References: 1: Configuring Cloud Proxies in vRealize Operations 2: What is a Reverse Proxy Server? | NGINX 3: What is a Web Proxy? | Proxy Server | Cloudflare

To allow the newly added group members to login quickly into vRealize Operations, the administrator needs to synchronize the user groups from the Active Directory source and check if the automatic synchronization option is enabled. Synchronizing the user groups imports the latest user group information from the source to vRealize Operations. Checking the automatic synchronization option ensures that the user group membership is updated periodically without manual intervention. Re-adding or deleting the authentication source are not necessary steps, as they would disrupt the existing user access control. Adding a SAML IdP as authentication source is not relevant, as the question is about Active Directory groups. References: Import User Groups From Source, Export and Import of User Groups, Synchronize the Active Directory Groups for VMware Aria Operations in Workspace ONE Access

According to the VMware vRealize Operations Reference Materials, a vRealize Operations cluster consists of three types of nodes: primary, data, and remote collector. The primary node is the initial and required node that manages the cluster configuration and data synchronization. The data nodes are optional nodes that have adapters installed and perform data collection and analysis. The remote collector nodes are also optional nodes that can navigate firewalls, interface with remote data sources, reduce bandwidth consumption, and reduce the load on the analytics cluster. They only gather objects for the inventory, without storing data or performing analysis. Therefore, options A, C, and E are correct.

The other options are not correct because they are not types of nodes that make up the vRealize Operations cluster. Option B is not correct because the cloud connector is not a node, but a service that connects vRealize Operations to VMware Cloud services. Option D is not correct because the worker node is not a term used in vRealize Operations, but in vRealize Automation. Option F is not correct because the secondary node is also not a term used in vRealize Operations, but in vSphere Replication. References:

• About vRealize Operations Cluster Nodes
• vRealize Operations Manager Cluster Node Types
• Service Discovery Overview

 To configure vRealize Operations cost drivers to assign a different cost per GB for different storage tiers, the administrator should use a vSphere tag category, assign different tag values for that category to the different tiers in the vSphere client, and then assign different costs per GB for each tag value. This is because vRealize Operations uses vSphere tags to identify the storage tiers and apply the corresponding cost drivers. vSphere tags are metadata that can be attached to objects in the vSphere inventory, such as datastores, clusters, hosts, VMs, etc. A vSphere tag category is a logical grouping of tags that share a common characteristic, such as storage tier, license type, backup policy, etc. A vSphere tag value is a specific label within a category that can be assigned to one or more objects, such as Tier 1, Tier 2, Tier 3, etc. By using a vSphere tag category and tag values for storage tiers, the administrator can easily classify the datastores into different tiers based on their performance, availability, or other criteria. Then, the administrator can assign different costs per GB for each tag value in vRealize Operations, which will reflect the different storagebase rates for each tier. This way, the administrator can achieve a granular and accurate cost visibility and analysis for the storage resources in vRealize Operations. References: Overview of Cost Drivers; VM Cost with VMware vRealize Operations; Using Tags to Organize Your Inventory