An administrator is tasked to monitor configuration drifts of vSphere clusters in a VMware Cloud...

In VMware Cloud Foundation 9.0, configuration drift detection is handled through VCF Operations Configuration Management integrated with vSphere Configuration Profiles.

According to the VCF 9.0 documentation:

vCenter Version Requirement (D):Configuration drift monitoring requires vCenter 8.0 Update 3 or later, as this introduces the enhanced configuration profile capabilities necessary for drift comparison.

Create a Configuration Template (E):VCF Operations requires a defined baseline configuration template to compare cluster states against.

Assign the Template to a Policy (F):Policies enforce and monitor configuration compliance. Assigning the template to a policy allows drift detection against the desired state.

Incorrect options:

vCenter 9.0 (A) is not required; 8.0 U3 is sufficient.

A collector (B) is not specifically required for drift detection.

Scheduling drift detection (C) is part of policy evaluation, not a standalone mandatory step.

Configuring vSphere Configuration Profiles (G) is beneficial but not mandatory for drift monitoring via VCF Operations.

Thus, the three required steps are: vCenter 8.0 U3 or later, create a configuration template, and assign it to a policy.