Question 8: An administrator has been tasked with creating a region to provide resources to an Organization… | Advanced VMware Cloud Foundation 9.0 Automation Practice Question

An administrator has been tasked with creating a region to provide resources to an Organization in VMware Cloud Foundation (VCF) Automation. The following information has been provided to the administrator for this task: • Two workload domains are configured and will integrate with the region. • All workload domains are configured to share a VMware NSX Manager. • All workload domains are configured with VMware vSAN storage. • All workload domain VMware vCenter instances have a Supervisor enabled. Before creating the region, what two additional configurations should the administrator validate? (Choose two.)

Answer

A. An AllApps Organization has been created.
B. All Supervisors are configured with the same services across all vCenter instances.
C. All required virtual machine (VM) classes are present and have the same names across all vCenter instances. Correct
D. A Region Quota has been created and associated with the Organization.
E. All required storage classes are present and have the same names across all vCenter instances. Correct

Explanation

In VCF 9.0, a Region is a logical grouping of resources (typically spanning multiple vCenter/Supervisor instances) that is presented to an Organization for consumption. For the automation engine to treat multiple clusters or vCenter instances as a single, unified pool of capacity, there must be absolute naming parity for resource types. If a blueprint requests a "Large-Memory" VM Class or a "Gold-Storage" Storage Class, that specific name must exist and be configured identically on every Supervisor instance within the region. If naming differs—for example, "Gold-Tier" on one and "Gold-Storage" on another—the provisioning engine will fail to find a consistent placement target, leading to deployment errors. Validating that VM Classes and Storage Classes are synchronized in name and availability across all participating workload domains is a mandatory "Day 0" task before the logical Region construct can be finalized in the Provider Management Portal.