5V0-35.21 Dumps with Practice Exam Questions Answers

The workload placement feature between vRealize Automation Cloud and vRealize Operations Cloud allows vRealize Operations Cloud to provide recommendations for the initial placement of virtual machines based on the demand and allocation models. To enable this feature, the following pre-requisites must be met12:

• Both vRealize Automation Cloud and vRealize Operations Cloud must manage the same Cloud Account. This means that the vCenter Server instance that is used as a cloud account in vRealize Automation Cloud must be the same as the one that is monitored by vRealize Operations Cloud. This ensures that the vSphere objects are consistent and identifiable across both platforms.
• In vRealize Automation Cloud, the target Cloud Zone Placement Policy must be set to ADVANCED. This option activates the integration with vRealize Operations Cloud and allows it to provide placement recommendations based on the vRealize Operations policy settings. The other options, such as SPREAD or BINPACK, use the vRealize Automation Cloud’s own placement logic and do not leverage vRealize Operations Cloud.
• All clusters within the target Cloud Zone must have fully automated VMware DRS enabled. This is a requirement for vRealize Operations Cloud to provide placement recommendations, as it relies on the DRS algorithm to balance the workload across theclusters. If the clusters do not have DRS enabled or set to manual or partially automated, vRealize Operations Cloud cannot provide placement recommendations.

The other options, such as installing the vRealize Operations Management Pack for vRealize Automation Cloud, enabling VMware HA on the clusters, or setting the placement policy to SPREAD, are not required to enable the workload placement feature between vRealize Automation Cloud and vRealize Operations Cloud. References: 1: Advanced Workload Placement for Allocation Model 2: Learn more about workload placement

vRealize Operations provides the following three key benefits within an environment:

• Capacity optimization: vRealize Operations helps you optimize the capacity of your infrastructure and applications by providing visibility, analysis, planning, and automation. You can monitor and forecast the demand, supply, and utilization of resources, identify and reclaim unused or overprovisioned resources, balance the workload across clusters and datastores, and plan for future growth or consolidation scenarios. You can also automate the capacity optimization actions based on policies and alerts.
• Performance optimization: vRealize Operations helps you optimize the performance of your infrastructure and applications by providing real-time and historical metrics, alerts, dashboards, and reports. You can monitor and troubleshoot the health, risk, and efficiency of your environment, identify and resolve performance issues, analyze the root cause and impact of problems, and optimize the configuration and placement of your workloads. You can also automate the performance optimization actions based on policies and alerts.
• Monitoring and troubleshooting: vRealize Operations helps you monitor and troubleshoot your environment by providing comprehensive and integrated visibility across physical, virtual, and cloud infrastructures. You can collect and analyze data from various sources, such as vSphere, NSX, vSAN, Kubernetes, AWS, Azure, etc., and correlate them to provide a unified view of your environment. You can also leverage artificial intelligence and machine learning to detect anomalies, generate smart alerts, and provide recommendations. You can also use various tools, such as dashboards, heat maps, topology maps, logs, etc., to drill down into the details and resolve issues faster.

References: vRealize Operations Overview; vRealize Operations Cloud for Service Providers; What’s New in vRealize Operations 8.6

A support bundle is a collection of log and configuration files that can help troubleshoot a vROps issue. To create a support bundle, the system administrator can use the vROps UI and select the option to create a light or full support bundle. A light support bundle includes 24 hours of logs, while a full support bundle includes all available logs and configuration files. For an intermittent issue that occurred in the last 12 hours, a light support bundle should be sufficient to collect the relevant information. The system administrator can also select the cluster nodes that need to be evaluated for support, and download the support bundle in ZIP format for analysis or sending to VMware Technical Support1. The other options are not recommended or efficient ways to collect the relevant information. Collecting the vCenter and vROps primary node logs using SSH and the vm-support utility would not include the logs from the other vROps nodes, and would require manual steps to gather and compress the files. Using the vROps UI to create a full support bundle for ESXi, vCenter, and primary vROps nodes would include unnecessary and excessive data that could slow down the process and consume more disk space. Using SSH to copy the log files from each of the vROps nodes from /var/log/warn & /var/log/messages locations would also require manual steps to gather and compress the files, and would not include the configuration files that could be useful for troubleshooting. References: 1: Create a vRealize Operations Support Bundle

 To add a custom metric configuration file to a scoreboard widget in a dashboard, the correct process is to create a metric file in XML format, set the scoreboard widget Self Provider to Off, and create a widget interaction with a provider widget. A custom metric configuration file is a file that defines the metrics that the scoreboard widget displays for different object types. The file must be in XML format and follow a specific schema. The file must be uploaded to the vRealize Operations server and selected in the Metric Configuration option of the scoreboard widget. The Self Provider option determines whether the widget shows metrics of the objects selected during editing of the widget or selected on another widget. When the Self Provider option is set to Off, the widget shows metrics of the objects selected on another widget. The widget interaction is a mechanism that allows widgets to communicate with each other and pass data. A provider widget is a widget that provides data to another widget. A receiving widget is a widget that receives data from another widget. To create a widget interaction, the administrator must edit the dashboard and select the provider widget and the receiving widget, and then configure the interaction type and the data to pass. By creating a widget interaction with a provider widget, the administrator can enable the scoreboard widget to display the custom metrics for the objects selected on the provider widget. References: How the Scoreboard Widget and Configuration Options Work; Question on How to Scoreboard Dashboard - Metric Configuration XML - Max & Avg Metric Values; Dashboard widget can set default metric key

 The vSphere Solution’s Default Policy is a policy that is automatically created when you add a vCenter Cloud Account to vROps. This policy applies to all the objects that are discovered and collected by the vSphere adapter. The origin of the settings in this policy is the base settings that are provided by the data adapters and solutions installed in vROps. The base settings are a collective group of rules that apply to all objects, regardless of their type or source. The vSphere Solution’s Default Policy inherits all the base settings by default, and you can modify them to suit your specific needs. The default policy setting is not defined by another administrator, nor is it added during the installation of the vROps management pack for vSphere. The settings of this policy are also not defined during the vROps OVF deployment, as they are determined by the data adapters and solutions. References: Default Policy in vRealize Operations, Configure VMware SDDC Benchmarks