The scheduled Reclaim action is created from the snapshot candidates visible at scheduling time, but execution still depends on the valid runtime state of each selected object. VCF Operations Reclaim supports scheduling snapshot reclamation from the Reclaim page; the administrator expands the cluster, selects one or more VMs or snapshots, and uses Schedule Action to run deletion later, with the job managed in Automation Central . The underlying delete snapshot action first retrieves snapshots based on age, then deletes selected snapshots, and the resulting task status is tracked in Recent Tasks . If a user reverts a VM to one of those snapshots before the scheduled job runs, that snapshot becomes part of the VM’s active rollback/current-state chain rather than an unused candidate that should be safely reclaimed. vSphere snapshot behavior requires caution because deleting a snapshot removes the ability to return to that snapshot state, and reverting changes the VM’s active snapshot relationship . Therefore, the reverted snapshot is not deleted, while the rest of the scheduled snapshot deletions can continue. The overall job is expected to finish as partially successful , reflecting that some selected objects were processed while the reverted snapshot was skipped or failed validation. Reference topic: Objective 4.2 – Reclaim Capacity / Snapshot Reclamation / Scheduled Actions / Automation Central .

The administrator must configure the overcommit ratio and activate the appropriate custom profile at the datastore policy level. In VCF Operations, the Allocation Model is enabled from the policy Capacity card by unlocking Allocation Model and setting the overcommit ratio for CPU, memory, or disk space. For a Datastore , the allocation model specifically allows the administrator to set the overcommit ratio for datastore disk space, which controls how allocated storage capacity is calculated rather than relying only on demand-based usage . The second requirement is to use the current disk space usage of an existing VM to determine how many similar VMs can fit on the datastore. That is handled by a custom profile . Custom profiles define a hypothetical VM configuration and calculate VM remaining for objects such as datastores, datastore clusters, and cluster compute resources . The custom profile wizard also allows metric values to be copied from an existing object, including by VM name, vCenter, VM tag, or custom group . Peak utilization and capacity buffer do not enable allocation modeling or define VM-fit profiles. Reference topic: Objective 4.2 – Manage VCF Capacity / Allocation Model / Custom Profiles / Policy Capacity Settings .

The correct sequence starts by selecting the relevant report template , because VCF Operations schedules are created against an existing predefined or custom report template. The documented workflow is accessed from Infrastructure Operations > Dashboards & Reports > Reports , where the administrator selects the required template from the Report Templates tab and chooses Schedule from the template actions . After the template and target object are selected, the administrator configures the schedule parameters, including time zone, start date, start time, and Recurrence . For a weekly report, the recurrence is set to Weekly . Report output is based on the template format, and VCF Operations supports both PDF and CSV report formats . The next step is to define delivery, such as enabling Email report , entering recipients, and selecting the outbound rule, or saving the report to an external location such as a network share . Finally, the administrator saves the configuration to activate the schedule. Reference topic: Objective 4.10 – Creating Custom Dashboards, Views and Reports / Schedule a Report / Report Templates / Recurrence and Delivery Options .

The required plug-in type is Webhook Notification Plugin . Workload Placement Action-based notifications are a specific notification type used for WLP virtual machine movement tasks , not standard alert notifications. The VCF Operations documentation states that administrators can create and manage Workload Placement action-based notifications and configure actions for which notifications are sent when a WLP action succeeds, fails, or times out. It further specifies that notifications are sent after the WLP VM movement task completes, regardless of final status . Before such notification rules can be created, the administrator must configure the Webhook Notification Plugin . In the WLP Action notification workflow, the outbound method supported by default is the Webhook Notification Plugin, and the administrator selects or creates a Webhook plug-in instance before selecting the payload template . This is reinforced in the payload-template workflow, where Action appears only when Webhook Notification Plugin is selected as the outbound method; WLP Action notification payloads are configurable only for Webhook . Network Share does not support notification rules, and SNMP or Standard Email are used for alert-style notifications, not WLP Action notifications. Reference topic: Objective 4.9 – Notifications / Outbound Plugins / WLP Action-Based Notifications .

The administrator should first locate the relevant VM compliance alert by filtering the VM’s alert list using Alert Subtype = Compliance . Compliance benchmark violations are implemented as alert definitions and symptoms, so filtering by compliance subtype narrows the alert list to the correct class of benchmark findings. After opening the alert, the administrator should inspect the alert evidence and specifically expand Alert Basis . Broadcom documents that Alert Basis shows the active symptoms or conditions that were met for the alert when Active Only is enabled, which directly identifies the symptom or symptoms that triggered the compliance violation ( TechDocs ). The Potential Evidence view is also part of the alert investigation workflow and exposes supporting evidence around the alert, including the basis used to explain why the alert fired ( TechDocs ). Related Alerts is not the correct place to identify the triggering symptom; it shows other correlated alerts. Object Type = Compliance is invalid because compliance is an alert subtype, not a VM object type. Go to Alert Definition shows the configured definition, but not necessarily which symptoms were active on that VM at trigger time. Reference topic: Objective 4.16 – Compliance Benchmarks / CIS Security Standards / Alert Basis and Triggered Symptoms .

The administrator must create the scheduled action directly from the Rightsize feature. VCF Operations Rightsize is the capacity-optimization workflow used to adjust CPU and memory allocations for oversized and undersized virtual machines. For oversized VMs, the administrator selects the target VM, opens the resize workflow, reviews the recommended vCPU and memory reduction, and can use the edit controls to modify the recommendation before execution. In this scenario, the default recommendation is a 4 vCPU reduction, but the agreed action is only 50 percent of that value, so the administrator adjusts the reduction to 2 vCPU . The Rightsize page also provides SCHEDULE ACTION , which opens a scheduling dialog so the resize action can run later during the maintenance window; scheduled jobs are then managed through Automation Central . Automation Central is used to manage scheduled jobs, but the rightsizing task is initiated from Rightsize. Reclaim is used for powered-off VMs, idle VMs, snapshots, and orphaned disks, not vCPU rightsizing. vSphere scheduled tasks bypass VCF Operations recommendations. Reference topic: Objective 4.2 – Manage VCF Capacity / Rightsize Workloads / Oversized VMs / Scheduled Actions .

The correct configuration is to set Operational Intent Cluster Headroom to 20% and set Workload Optimization to Consolidate. VCF Operations Workload Optimization is governed by Operational Intent, which defines how workloads are placed and balanced across clusters. The Workload Automation policy settings define Workload Optimization goals as Balance, Moderate, or Consolidate. The documentation states that Consolidate proactively minimizes the number of clusters used by workloads, potentially freeing resources and supporting cost optimization while still meeting performance goals . That directly maps to the requirement to place workloads into as few clusters as possible. The same policy workspace includes Cluster Headroom, which establishes a required capacity buffer, with the documentation explicitly giving 20 percent as an example and explaining that it preserves extra space for growth inside the cluster . Business Intent tags are used for placement rules based on vCenter tag categories such as operating system, environment, tier, network, or other business constraints, not for defining operational headroom or consolidation strategy . Reference topic: Objective 4.6 – Workload Optimization / Operational Intent / Consolidate mode / Cluster Headroom.