An administrator is tasked with using VMware Cloud Foundation Configuration Drift management in order to...

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