VMware 5V0-35.21 Practice Test - Questions Answers

According to the vRealize Operations Sizing Guidelines, the supported node configurations during installation are Large, Very Large, and Medium. These are the default configurations that VMware offers based on the number of objects and metrics to be monitored by vRealize Operations. Each configuration has a different amount of vCPU, memory, disk space, and network requirements.The administrator can choose the configuration that best suits the existing infrastructure and the expected growth of the environment1.

The other options are not supported node configurations during installation. Tiny and Small are not valid configurations for vRealize Operations 8.x and later versions.These configurations were available for vRealize Operations 6.x and 7.x versions, but they are not recommended for production environments due to their limited capacity and performance2. No limit is not a configuration option, but a statement that indicates that there is no upper limit on the number of nodes that can be added to a vRealize Operations cluster.However, the number of nodes depends on the node configuration, the network latency, and the data source type3.

References:1:vRealize Operations 8.0.x Sizing Guidelines (75162) - VMware2:vRealize Operations Manager 7.5 Sizing Guidelines (67752)3:vRealize Operations 8 - VMware Docs

According to the VMware vRealize Operations User Guide1, business intent is a feature that allows the administrator to define the desired state and behavior of the clusters and hosts in the environment based on business objectives and constraints. Business intent can be used to optimize the placement and balance of workloads across clusters and hosts, as well as to enforce license compliance and availability requirements.

One of the types of business intent that can be configured in vRealize Operations is Business Intent - Clusters. This type of business intent allows the administrator to assign tags to clusters and virtual machines, and then create rules that match the tags to ensure that the virtual machines are placed on the appropriate clusters. For example, the administrator can tag two clusters as Windows and two clusters as Linux, and then tag the virtual machines accordingly. Then, the administrator can create rules that match the Windows tag and the Linux tag, and set the enforcement mode to Mandatory. This will ensure that the Windows workloads only run on the Windows clusters, and the Linux workloads only run on the Linux clusters.

Therefore, the correct answer is B. Business Intent - Clusters, as this is the type of business intent that should be configured by the administrator to achieve the goal of ensuring the workloads only run on their assigned nodes.References:

1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 49-51, 54-55

According to the VMware vRealize Operations Reference Materials, two of the public cloud providers that are supported out-of-the-box in vRealize Operations What-If planning for public cloud costs are Microsoft Azure and Google Cloud. The What-If planning feature allows the administrator to compare the cost of running workloads in different public cloud providers, such as AWS, IBM Cloud, Microsoft Azure, Google Cloud, and Alibaba Cloud. The administrator can select the public cloud provider, the region, and the instance type, and then run the scenario to see the estimated monthly cost for the selected workloads. The administrator can also compare up to three public cloud providers at a time. The other options are incorrect because they are not supported out-of-the-box in vRealize Operations What-If planning for public cloud costs. Salesforce Cloud and Oracle Cloud are not among the public cloud providers that are available by default in vRealize Operations. However, the administrator can create a custom public cloud provider and upload a rate card to include them in the What-If planning. Alibaba Cloud is supported out-of-the-box in vRealize Operations What-If planning for public cloud costs, but it is not one of the correct answers, as only two options are required.References:What-If-Analysis - Migration Planning: Public Cloud;VMware vRealize Operations What-If Analysis;VMware vRealize Operations for Public Cloud

vRealize Operations Manager supports various notification methods out of the box, including email notifications and integration with third-party systems. Microsoft Teams is one of the platforms supported for notifications, allowing for alerts and updates from vRealize Operations Manager to be directly sent to a Microsoft Teams channel. This integration facilitates real-time alerting and collaboration within IT teams. However, options like SMS and Slack might require additional third-party plugins or integrations and are not natively supported as out-of-the-box notification types. Remedy, being an IT service management tool, can be integrated but is not a direct notification type.

To add an additional data node to the existing vRealize Operations cluster, you need to deploy a new data node from the Administration Ul. A data node is a node that collects, stores, processes, and analyzes data from your environment.You can expand an existing installation to add a data node by following these steps1:

In a Web browser, navigate to the name or IP address of the node that will become the data node. The setup wizard appears, and you do not need to log in to vRealize Operations.

Click Expand an Existing Installation.

Click Next.

Enter a name for the node (for example, Data-1).

From the Node Type drop-down, select Data.

Enter the FQDN or IP address of the primary node and click Validate.

Select Accept this certificate and click Next.

Verify the vRealize Operations administrator username of admin.

Enter the vRealize Operations administrator password.

Click Next, and click Finish.

The other options are not correct because they do not deploy a new data node from the Administration Ul. Option A is incorrect because cloning an existing data node is not supported and may cause data inconsistency. Option C is incorrect because deploying a new virtual appliance from an OVF file is not enough to add a data node to the cluster. You still need to configure the node type and join the cluster from the Administration Ul. Option D is incorrect because enabling High Availability in the Administration Ul does not add a data node to the cluster. It only creates a replica of the primary node for failover purposes.References:Expand an Existing Installation to Add a Data Node

Continuous Availability (CA) is a feature of vROps that separates the analytics cluster into two fault domains, stretching across vSphere clusters, and protects the analytics cluster against the loss of an entire fault domain. CA requires a witness node to be deployed in the cluster, which acts as a tiebreaker in case of a network partition between the two fault domains. CA ensures that the data stored in the primary node and data nodes in one fault domain is always 100% synced to the replica node and data nodes in the other fault domain. CA is not a disaster recovery solution, but it provides a higher level of availability and data protection than High Availability (HA), which only protects against the loss of a single node. HA creates a replica for the primary node, but does not replicate the data nodes. Therefore, if a whole rack fails, HA may not be able to prevent data loss. Deploying an additional vROps deployment as a standby or configuring remote collector groups are not options that address the requirement of ensuring no monitoring data is lost in the event of a whole rack failure.These options may provide some redundancy or scalability, but they do not guarantee data consistency or availability across fault domains.References:1:About vRealize Operations Continuous Availability2:Continuous Availability Considerations3:About vRealize Operations High Availability4:High Availability Considerations

In VMware vSphere environments, 'Business Intent' is a feature in vRealize Operations that allows administrators to align workloads with business requirements. It ensures that specific workloads, like database virtual machines in your scenario, stay on or are moved to designated clusters based on defined business policies. This feature is essential for maintaining operational efficiency and ensuring that resources are optimized according to business needs.

Business intent is a feature that allows you to define the desired state of your clusters based on your business objectives and workload requirements.You can use business intent to specify the cluster placement and resource allocation for your database virtual machines according to their performance, availability, or efficiency needs1.For example, you can create a business intent policy that assigns high priority and high CPU and memory reservations to your critical database VMs, and places them on a cluster that has the best hardware and network configuration2.Business intent works with vSphere DRS to automatically move and balance your VMs across the clusters that match your policy3.

The other options are not correct because they do not allow you to configure the cluster placement and resource allocation for your database VMs based on your business objectives. Custom group is a feature that allows you to group objects in your environment based on common attributes or relationships, but it does not define the desired state of your clusters. Compliance benchmark is a feature that allows you to assess the security and configuration compliance of your clusters against predefined or custom standards, but it does not define the desired state of your clusters. Operational intent is a feature that allows you to define the operational behavior of your clusters based on your operational objectives and constraints, such as power management, maintenance mode, or fault tolerance, but it does not define the desired state of your clusters.References:Business Intent,Create a Business Intent Policy,vSphere DRS and Business Intent, [Custom Group], [Compliance Benchmark], [Operational Intent]

SSH enabled on an ESXi host (Option C) can be a security concern if not properly managed, as it can provide broad access to the host.

A connected Floppy drive (Option D) can be a risk as it could be used to introduce unauthorized data or software into the VM.

Allowing Promiscuous Mode (Option F) on a Distributed Port Group can be a security risk as it allows all virtual machines connected to the port group to see all network traffic, which is generally not recommended in secure environments.

The type of cost driver that the administrator should configure to allocate the cost of database software across a vSphere cluster that has been licensed isApplications. Applications are software components that run on top of the virtual machines and provide business value. Examples of applications are database software, web servers, middleware, etc. You can assign application costs to VMs based on the type of application they run, such as Oracle, SQL Server, Apache, etc. You can also create custom application types and assign costs to them.By configuring application costs, you can track the expenses of running different types of applications on your private cloud and optimize your resource utilization and budget12.References:1:Application Cost Driver2:Costing with VMware vRealize Operations Part 1