To generate a daily email report of a list of VMs that have been provisioned from vRA, you need to follow these steps:

Create a custom view that displays the VM name, owner, and creation date for the deployments in the defined cluster.  You can use the vRealize Automation Reporting - vRA8 deployment resources and statuses sample as a reference 1 .

Create a report that uses the custom view as the template and select the output format as CSV or JSON.

Schedule the report to run daily and set the start date and recurrence to daily (option A).

In the Email addresses text box, enter the email addresses that must receive the report, and select an outbound rule (option B).  You also need to configure an email server in vRealize Automation Service Broker to send notifications 2 .

Click on Schedule, select vSphere Hosts and Clusters, expand vSphere World, and select the specific cluster (option E). This will filter the report data to only include the VMs provisioned to the defined cluster.

Save the report and verify that it is sent to the email recipients as expected.

Option C is not required because the report is sent via email and does not need to be stored in an external location. Option D is redundant because the start date and recurrence are already set in option A. Option F is incorrect because it will include all the VMs in the vCenter, not just the ones in the defined cluster.  References :

Create and Configure Reports

Send email notifications to Service Broker users

vRealize Automation Reporting - vRA8 deployment resources and statuses

To achieve the goal of automated remediation, the administrator needs to include two alert components in the alert definitions: recommendations and actions. Recommendations are the remediation options that are provided to the users to resolve the problems that the generated alert indicates. Actions are the vRealize Operations tasks that can be executed on the target systems to automate the remediation process.  The administrator can associate one or more actions with a recommendation, and configure the action to run automatically or manually when the alert is triggered 1 .  References :

Defining Alerts in vRealize Operations

What’s Your Issue? How to Use vRealize Operations Alerts

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 is  Applications . 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 budget 1 2 .  References :  1 :  Application Cost Driver   2 :  Costing with VMware vRealize Operations Part 1

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 the Company 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

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

 To estimate the monthly cost of running workloads in IBM Cloud, the administrator can use the What-If Analysis feature of vRealize Operations, which allows forecasting the impact of migrating a workload to a public cloud instance such as AWS, IBM Cloud, Microsoft Azure, Google Cloud or to VMware Cloud on AWS 1 . The administrator can select the Migration Planning option and choose IBM Cloud as the target cloud provider. Then, the administrator can import the existing VMs that support the business-critical application from the custom group in vRealize Operations and select all machines to be included in the scenario.  Finally, the administrator can run the scenario and get the vRealize Operations analysis and assessment of the plan, which includes the cost and capacity information for the IBM Cloud region 2 .  References :  1 :  What-If Analysis - Migration Planning: Public Cloud   2 :  Migration Planning

According to the vRealize Operations User Guide 1 , Business Intent is a feature that allows 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. Business Intent is applied to objects in vRealize Operations using vCenter Server tags, which are key:value labels that allow operators to add meta-data to vCenter Server objects. By tagging VMs, hosts, and/or clusters with specific tags, the administrator can create business-related placement constraints, such as VMs can only be placed on hosts/clusters with matching tags. For example, the tag OS: Linux can indicate a cluster or VM that is assigned to the category OS with a tag name of Linux. vRealize Operations then uses these tags 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:

Groups are not used to apply Business Intent to objects in vRealize Operations. Groups are collections of objects that share common characteristics, such as type, name, location, or relationship.  Groups are used to organize objects for monitoring, analysis, alerting, or policy assignment, but not for workload placement or balance 1 .

Policies are not used to apply Business Intent to objects in vRealize Operations. Policies are sets of configuration settings that define how vRealize Operations monitors and manages the objects in the SDDC.  Policies are used to enable or disable alerts, metrics, properties, symptoms, recommendations, or actions for different types of objects, but not for workload placement or balance 1 .

Roles are not used to apply Business Intent to objects in vRealize Operations. Roles are collections of permissions that define what actions a user can perform on the objects in the SDDC.  Roles are used to control the access and visibility of the objects for different users, but not for workload placement or balance 1 .  References :  1 : vRealize Operations User Guide, pages 57-59, 62-63, 66-67, 70-71.

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 Availability   2 :  Continuous Availability Considerations   3 :  About vRealize Operations High Availability   4 :  High Availability Considerations

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

According to the VMware vRealize Operations Reference Materials, Workload Optimization is a feature that allows you to automatically balance and optimize workloads across your virtualized infrastructure. Workload Optimization has four settings that determine how aggressively it moves workloads between clusters: Moderate, Balance, Consolidate, and Buffer. Each setting has a different impact on the number of vMotion operations, the cluster headroom, and the workload contention.

The Consolidate setting is the most aggressive setting that aims to minimize the workload contention across clusters by reducing the number of clusters used and maximizing the utilization of each cluster. The Consolidate setting performs the most vMotion operations, leaves the least cluster headroom, and has the lowest workload contention. The Consolidate setting is suitable for environments that have overprovisioned clusters and want to free up some clusters for other purposes or reduce the infrastructure costs. Therefore, option C is correct.

The other options are not correct because they do not meet the goal of minimizing the workload contention across clusters by reducing vMotion operations. Option A is not correct because the Moderate setting is the least aggressive setting that aims to maintain the current state of the clusters and avoid unnecessary vMotion operations. The Moderate setting performs the least vMotion operations, leaves the most cluster headroom, and has the highest workload contention. The Moderate setting is suitable for environments that have stable clusters and do not want to disrupt the existing workload placement. Option B is not correct because the Balance setting is a moderate setting that aims to balance the workload distribution across clusters and improve the performance of the clusters. The Balance setting performs a moderate number of vMotion operations, leaves a moderate cluster headroom, and has a moderate workload contention. The Balance setting is suitable for environments that have some imbalanced clusters and want to optimize the workload placement. Option D is not correct because the Buffer setting is a conservative setting that aims to create more cluster headroom and reduce the risk of resource shortage. The Buffer setting performs a low number of vMotion operations, leaves a high cluster headroom, and has a low workload contention. The Buffer setting is suitable for environments that have unpredictable or bursty workloads and want to ensure enough capacity for future demand.  References :

Configuring and Using Workload Optimization

Start Running a Self-Driving Datacenter – vRealize Operations 7.0 Workload Optimization

Using Workload Optimization to Improve Performance