Question 137 - 5V0-35.21 discussion

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 the clusters. 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 Model2:Learn more about workload placement