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 should model the phased migration by using What-If Analysis workload planning, not migration execution workflows. Because the target workload domain uses vSAN , the correct planning model is the hyperconverged workload-planning workflow, where VCF Operations lets the administrator add or remove VM workloads in a vSAN environment and evaluate the capacity effect on the selected cluster . Each migration phase should be represented as a separate scenario: small VMs, medium VMs, and large VMs. In each scenario, the administrator configures an Application Profile to represent the t-shirt size by defining vCPU, memory, and disk space, then adds the corresponding number of VM workloads for that phase . Since the source vCenter is unmanaged, importing profiles or VM templates directly from the source environment is not the correct method. After the scenarios are created, VCF Operations allows compatible saved scenarios that target the same object to be selected and run together, so the administrator can evaluate the cumulative impact of all planned phases on the target cluster . Reference topic: Objective 4.3 – Forecast VCF Capacity Growth / What-If Analysis / Add VM Workloads / Run Multiple Scenarios Cumulatively .

The administrator should use Edit for Specific Datacenter mode and edit the Facilities cost driver. VCF Operations cost drivers calculate private cloud cost from inventory details such as ESX hosts, datastores, VMs, configuration, and utilization, and administrators can modify data-center expenses when the default reference values do not reflect actual costs . Because the only stated variation across DC1–DC4 is power and cooling , the relevant cost category is Facilities , which covers real estate, data center buildings, power, cooling, racks, and facility management labor . The Facilities workflow specifically allows the administrator to modify power and cooling cost per kilowatt-hour or total monthly facilities cost . Since the four datacenters do not share identical power and cooling values, the administrator must select Edit for Specific Datacenter , which allows different cost-driver values for different datacenters instead of applying a single value globally . Server Hardware: Hyper-Converged is relevant for vSAN/vxRail hardware costing, but the scenario states that all monthly costs are the same except power and cooling. Reference topic: Objective 4.4 – Cost Management / Cost Drivers / Facilities Cost Driver / Specific Datacenter Edit Mode .

The minimum requirements are to register VCF Operations in Connected Mode with the VCF Business Services console and activate Log Assist on a Unified Cloud Proxy . Log Assist is designed to generate support bundles, link them to Broadcom support cases, and attach diagnostic findings for troubleshooting. The official VCF 9.0 guidance states that before using Log Assist, the environment must be in Connected Mode , Log Assist must be activated on a unified collector, and inventory objects must be assigned to Log Assist . The setup workflow specifically instructs the administrator to go to License Management > Registration and register licenses in Connected Mode, then go to Administration > Control Panel > Cloud Proxies , select the collector, and choose Activate Log Assist . Log Assist uses the unified collector to collect and upload support bundles to the Broadcom Support Portal; legacy or Classic collectors do not support this capability . Disconnected mode cannot satisfy automatic support upload. Enabling vCenter log collection is a separate logging function and is not the minimum requirement for Log Assist. Reference topic: Objective 4.9 – Log Assist / Unified Collector / Connected Licensing / Support Case Uploads .

The scheduled oversized action remains valid for acme001, so the VM is reduced by 2 vCPU . Excluding the VM from the undersized list affects subsequent undersized resize actions, not the oversized action that was already scheduled. VCF Operations Rightsize separates oversized and undersized workflows. For oversized VMs, the administrator selects the Oversized VM tab, optionally excludes VMs, selects the target VMs, and schedules or runs the resize action to reduce vCPU or memory . For undersized VMs, the administrator separately selects the Undersized VMs tab, optionally excludes VMs, and then schedules or runs the scale-up action . The Rightsize table explicitly provides separate actions for oversized and undersized VMs, with Schedule Action , Resize VM(s) , and Exclude VM(s) available within each category . Because acme001 was selected for the oversized scheduled action before any undersized exclusion was applied, its vCPU reduction is still scheduled. Because the administrator then excluded acme001 from the undersized list before scheduling the undersized scale-up for the remaining VMs, acme001 is not included in that memory increase. Reference topic: Objective 4.2 – Rightsizing / Oversized and Undersized VM Actions / Exclude VM(s) / Scheduled Actions .

Invoke the process using a VCF Operations API call.

Schedule a job using VCF Operations Automation Central.

The two valid activation methods are to invoke Drift Detection through a VCF Operations API call and to schedule a job using VCF Operations Automation Central . VCF Operations Configuration Drift uses desired-state templates assigned through policy to compare vCenter and vSphere cluster configuration values against approved standards. The VCF 9.0 documentation states that unified configuration management supports scheduled drift detection for vCenter and cluster objects and allows administrators to schedule drift detection through VCF Automation or the VCF Operations orchestrator . The scheduling workflow is performed from Fleet Management > Configuration Drifts > Schedule Drift Detection , where the administrator defines the scope, criteria, and schedule; after creation, VCF Operations creates a new job in Automation Central . API invocation is also valid because VCF Operations exposes fleet and cloud proxy functionality through APIs for automation-driven operations . The GitLab or source-control sync options are not correct because source control synchronizes configuration templates, not the drift detection process itself. Pull requests govern template change review, not drift execution. Reference topic: Objective 4.16 – Monitor Security, Compliance and Configuration / Configuration Drift / Scheduled Drift Detection / Automation Central / API-driven operations

Configure Service and Application Discovery

Manage Services and View Applications

Monitor services using dashboards

The three correct actions are Configure Service and Application Discovery , Manage Services and View Applications , and Monitor services using dashboards . VCF Operations uses the Service Discovery adapter to discover services running inside virtual machines and to build service relationships or dependencies between services running on different VMs. The official workflow states that, to discover and monitor services and add and view applications, administrators should configure Service and Application Discovery, manage services and view applications, monitor services using dashboards, and view discovered services . Configuration starts from Infrastructure Operations > Configurations > Service Discovery , where the administrator enables Service Discovery and Application Discovery on the vCenter integration . Service monitoring is then managed from Workload Operations > Applications > Manage SDMP Services , where administrators can provide credentials, activate service monitoring, and view service discovery status . Applications are viewed from Workload Operations > Applications , where VCF Operations shows application resources, connected VMs, service relationships, graphs, lists, and links . Application Discovery Timeout and Port Group configuration are not required actions in this workflow. Reference topic: Objective 4.7 – Monitor Applications with VCF Operations / Service Discovery / Manage Services / View Applications / Service Discovery Dashboards .

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 three required considerations are data loss, agent reinstallation, and failover/failback downtime. VCF Operations supports Application Monitoring High Availability for collector groups so application monitoring can continue when a cloud proxy or cloud proxy component fails. The documentation states that cloud proxies in an application-monitoring HA collector group operate in a primary-secondary mode . However, existing Telegraf agents cannot simply be converted to HA. To move an existing target machine to application monitoring HA, the administrator must install or reinstall the agent using an application-monitoring HA activated collector group . The same guidance states that adding a cloud proxy currently used by Telegraf agents to an HA activated collector group causes loss of existing application data, so historical application data must be treated as non-preserved during this transition . Finally, HA does not eliminate all interruption: failover or failback has a downtime of three collection cycles , and adding or removing a cloud proxy from the HA collector group also has a three-cycle downtime . Reference topic: Objective 4.7 – Monitor Applications / Product-Managed Telegraf / Application Monitoring High Availability / Collector Groups .