Free VMware Cloud Foundation 9.0 Administrator Practice Questions

The VCF Automation Costing and Pricing Guide explains:

“Define core costs for CPU, memory, and storage under Base Settings to apply fleet-wide.” (A)

“Mark the created policy as the default to ensure it applies globally.” (B)

For SAP HANA, “Create an exception policy under Base Settings with VM setup charges assigned to the SAP HANA cluster.” (E)Default Policy (C, F) is system-reserved. Sub-policies under “Resources” (D) are not valid. Correct configuration steps: A, B,

E.  

The VCF 9.0 Automation Guide details the use of Property Groups to standardize blueprint inputs and constants across projects. Property Groups allow administrators to define sets of inputs (like size, os, location) and constants (like salt master id) centrally, ensuring consistency across deployments.

The correct actions are:

Create a new Property Group for input properties (C) to capture the standard inputs (size, os, location).

Create a new Property Group for constant properties (E) to include items like the salt master id.

Update all existing blueprints in the production project with the new Property Groups (F) to enforce standardization across new and existing workloads.

Options A and B are incorrect because changes are not required in the appdev project or across the entire organization—only the production project. Option D is redundant since inputs and constants should be separated into distinct groups.

The VCF 9.0 Operations Policies Guide explains how to extend and scope monitoring policies:

Create a child policy under the existing Organization Policy (C): Policies can inherit settings from parent policies. By creating a child policy under Organization Policy, administrators can apply additional metrics without overriding global policies.

Create a Custom Group (F): Custom Groups allow dynamic membership based on naming conventions or criteria. In this case, business-critical VMs can be grouped automatically by naming schema.

Assign the Custom Group to the new child policy (B): This ensures that the additional metrics only apply to the business-critical VMs in the Custom Group.

Incorrect options:

Custom Datacenters (A, D) are not required; the grouping requirement can be met with Custom Groups.

Creating the policy under Base Settings (E) would apply globally rather than inheriting from the Organization Policy.

When creating a Region in VCF Automation, multiple workload domains can be aggregated to provide capacity to Organizations. For consistent provisioning across domains, resource constructs must be uniform.

The VCF 9.0 Automation documentation specifies:

VM Classes must exist with identical names across integrated vCenters to ensure consistent deployment behavior.

Storage Classes must also be consistently defined across Supervisors to allow Kubernetes and VM workloads to consume storage predictably.

Region quotas (A) are applied after region creation.

Reserved VM Classes (C) are not a prerequisite unless specifically required for policy enforcement.

An Organization for VM Applications (D) is not required prior to region creation.

Thus, the administrator must validate:

Consistent VM Classes (B)

Consistent Storage Classes (E)

Deleting an Organization in VCF Automation requires using the Provider Management Portal, not Fleet Management. Before deletion, dependent resources must be removed.

According to the VCF 9.0 Automation documentation:

Administrators must log into the VCF Automation Provider Management Portal (G).

The Organization must first be disabled (C) to prevent active usage.

All associated region quotas must be deleted (D), since Organizations cannot be removed while resource allocations exist.

Finally, the administrator can delete the Organization (A).

Deleting SSL certificates (B) and the embedded Orchestrator (F) are not required for Organization removal. Fleet Management (E) is unrelated to Organization lifecycle operations.