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

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

According to the VMware vRealize Operations Reference Materials, the Wait Cycle and the Cancel Cycle are the settings that determine how long a symptom condition must be true or false before the symptom is triggered or cancelled. The default cycle for both settings is 5 minutes, which means that each cycle corresponds to one collection interval of 5 minutes. Therefore, if a symptom has a Wait Cycle of 3 and a Cancel Cycle of 2, it will take 15 minutes (3 cycles x 5 minutes) for the symptom to be triggered after the condition becomes true, and 10 minutes (2 cycles x 5 minutes) for the symptom to be cancelled after the condition becomes false. The other options are incorrect because they do not match the calculation based on the given settings and the default cycle. References: Symptom Definition Settings; Alert Definition Best Practices

According to the vRealize Operations User Guide1, the two statements that accurately characterize reports in vRealize Operations are:

• A report layout can contain table of contents, cover page, and footer. The report layout defines the appearance and structure of the report, and can include these optional elements to enhance the readability and presentation of the report1.
• Scheduling of reports can be done hourly, daily, weekly, and monthly. The report schedule defines the frequency and time of the report generation, and can be set to run at regular intervals, such as hourly, daily, weekly, or monthly, or at a specific date and time1.

The other statements are not accurate because:

• Views and Dashboards are not the only data types available for a report. A report can also include other data types, such as alerts, events, metrics, properties, and super metrics1.
• Only PDF type reports cannot be used to schedule a report generation. A report can be generated in different formats, such as PDF, CSV, or XML, and any of these formats can be used to schedule a report generation1.
• Reports scheduled for generation can be shared out via email or FTP. A report can be configured to send the generated output to one or more email recipients, or to upload the output to an FTP server1.

References: 1: vRealize Operations User Guide, pages 81-87.

 The advanced sizing guide should be used instead of the basic sizing guide in the vRealize Operations Manager (vROps) online Sizing tool when additional management packs are going to be implemented. The basic sizing guide provides the default sizing recommendations based on the number of objects and metrics collected from the vSphere environment. However, if the monitored environment includes other types of objects and metrics from different sources, such as management packs, the basic sizing guide may not be accurate. The advanced sizing guide allows the user to specify the number of objects and metrics for each management pack and get a more precise sizing recommendation12. References: 1: vRealize Operations Sizing Guidelines 2: vRealize Operations 8 - VMware Docs

In VMware vRealize Operations, policies determine how objects are analyzed and managed. They include settings for metrics collection, alert definitions, symptoms, recommendations, and more. If an administrator disables some virtual machine metrics in the Production policy, only objects assigned to that specific policy will be affected. The changes won’t impact other policies or globally affect all objects. This is because policies are hierarchical and inherit settings from their parent policies, unless overridden by the child policies. In the exhibit, the Production policy and the TestDev policy are both child policies of theCompany default policy, which is a child policy of the vSphere solution’s default policy, which is a child policy of the Base settings. Therefore, any changes made to the Production policy will only apply to the objects assigned to that policy, and not to the objects assigned to the TestDev policy or any other policy. References:

• vRealize Operations Policies, page 1-2
• Manage Policies, page 3-4
• Disable Metrics Collection, page 5

The alternative that is offered by default when Workload Planning returns that an existing cluster does not have the capacity to accommodate the selected virtual machines is cost comparisons for running in hybrid/private/public cloud. Workload Planning is a feature ofvRealize Operations that allows the administrator to plan and optimize the workload placement and capacity of the vSphere resources in the environment1. Workload Planning can be performed using two scenarios: Workload Optimization and What-If Analysis. Workload Optimization is a scenario that automatically balances the workload across the clusters and datastores based on the business and operational intents, such as performance, consolidation, or compliance2. What-If Analysis is a scenario that simulates the impact of adding or removing workloads, hosts, or datastores, or changing the demand or configuration of the existing workloads3. When Workload Planning is performed using the What-If Analysis scenario, and it returns that an existing cluster does not have the capacity to accommodate the selected virtual machines, the alternative that is offered by default is cost comparisons for running in hybrid/private/public cloud. This alternative allows the administrator to compare the estimated costs of running the selected virtual machines in different cloud platforms, such as VMware Cloud on AWS, Microsoft Azure, or Amazon Web Services, and to choose the best option for the business needs and budget4. Cost options for increasing cluster capacity with additional hosts (option B) is not the alternative that is offered by default, but it is another option that can be selected by the administrator. This option allows the administrator to estimate the costs of adding new hosts to the existing cluster, and to choose the best host model and quantity for the capacity and performance requirements5. Modifications to virtual machine configuration (option C) and modifications to host configurations (option D) are not alternatives that are offered by Workload Planning, as they are not related to the workload placement and capacity planning. These modifications can be performed using other features of vRealize Operations, such as Reclaimable Waste, Oversized Virtual Machines, or Configuration and Compliance. References:

• 1: VMware vRealize Operations Specialist Exam 2023 (5V0-35.21) Exam Guide, VMware, 2021, p. 14.
• 2: vRealize Operations Manager User Guide, VMware, 2021, p. 167.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 179.
• 4: vRealize Operations Manager User Guide, VMware, 2021, p. 187.
• 5: vRealize Operations Manager User Guide, VMware, 2021, p. 186.
• [6]: vRealize Operations Manager User Guide, VMware, 2021, pp. 77-78, 83-84, 229-230.

According to the VMware vRealize Operations Reference Materials, the component that will be available when a user logs in to the vRealize Operations Product UI is the Dashboards page. The Dashboards page is the main interface of the Product UI, where the user can view and interact with various dashboards that display the data and analysis of the monitored objects and environments. The Dashboards page also allows the user to create and customize their own dashboards, as well as access other features such as alerts, reports, views, and policies. The other options are incorrect because they are not available in the Product UI, but in the Admin UI. The Software Update page, the Certificate management, and the System Status page are all components of the Admin UI, which is a separate interface that provides the administrative and configuration functions for the vRealize Operations cluster. The Admin UI can be accessed by logging in to the master node or the replica node of the cluster, using the admin user account or a user account with the Administrator role. The user who has access only to the Product UI cannot access the Admin UI or its components. References: vRealize Operations Manager Overview; Log in to vRealize Operations Manager; vRealize Operations Manager Administration

• Workload Management is a feature of VMware vRealize Operations that enables self-driving operations management for hybrid and multi-cloud environments. It uses artificial intelligence and machine learning to monitor, analyze, and automate the performance, capacity, cost, and configuration of applications, infrastructure, and services12.
• Workload Management allows administrators to set a goal for workload optimization, which defines how vRealize Operations balances the resource utilization across clusters and data centers. The goal can be one of the following options34:
• Workload Management relies on VMware Distributed Resource Scheduler (DRS) and VMware Storage DRS to perform the workload optimization actions. DRS is a feature that automatically balances the compute resources and power consumption across the hosts in a cluster. Storage DRS is a feature that automatically balances the storage resources and I/O load across the datastores in a datastore cluster .
• To enable Workload Management to move a storage resource, such as a virtual disk or a virtual machine, Storage DRS must be enabled for the cluster that contains the storage resource. Storage DRS can be enabled or disabled at the cluster level, and can be configured with different automation levels, such as manual, fully automated, or partially automated .
• If Storage DRS is not enabled for the cluster, Workload Management cannot move the storage resource, as it does not have the permission or the mechanism to do so. This is the underlying reason for the problem. The other options are not relevant for moving a storage resource. DRS is only responsible for moving the compute resources, such as CPU and memory, not the storage resources. Storage DRS can be configured for both intra-datacenter and cross-datacenter migrations, not only for cross-datacenter migrations. The automation level of DRS does not affect the ability of Workload Management to move the storage resource, as long as Storage DRS is enabled.

References:

1: vRealize Operations - VMware 2: vRealize Operations Manager User Guide 3: Workload Optimization Details - VMware Docs 4: Workload Optimization in vRealize Operations Manager : [Distributed Resource Scheduler - VMware Docs] : [Storage DRS - VMware Docs] : [Enable or Disable Storage DRS for a Datastore Cluster - VMware Docs] : [Set the Automation Level for Storage DRS - VMware Docs] : [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 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 support bundle that the customer should send that fits the bandwidth constraints is the light-support bundle from all nodes. A support bundle is a collection of logs, configuration files, and diagnostic information that can be used by VMware support to troubleshoot and resolve issues with vRealize Operations1. A support bundle can be generated from the Admin UI of vRealize Operations, and it can include information from the primary nodes, the replica nodes, and the remote collectors2. A support bundle can be either full or light, depending on the amount and type of information that is included. A full-support bundle contains all the logs, configuration files, and diagnostic information that are available, and it is recommended for most cases. A light-support bundle contains only the essential logs, configuration files, and diagnostic information that are needed for basic troubleshooting, and it is recommended for cases where the bandwidth is limited or the issue is not complex3. A light-support bundle is smaller in size than a full-support bundle, and it can be generated faster and transferred easier. A light-support bundle from all nodes includes the information from the primary nodes, the replica nodes, and the remote collectors, and it can help VMware support to identify the cause of the erratic behavior and the role of the remote collectors. A full-support bundle from the primary nodes only (option A) or a light-support bundle from the primary nodes only (option B) are not the best choices, as they do not include the information from the replica nodes and the remote collectors, which may be relevant for the issue. A full-support bundle from all nodes (option C) is not the best choice, as it is larger in size than a light-support bundle, and it may exceed the bandwidth constraints or take longer to generate and transfer. References:

• 1: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 35.
• 2: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 36.
• 3: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 37.
• 4: VMware vRealize Operations Specialist Exam 2023 (5V0-35.21) Exam Guide, VMware, 2021, p. 11.