Free 5V0-3221 sample questions

Correct answer: Create VM groups within the vApp in Cloud Director and then define affinity rules between these groups.

VMware Cloud Director allows for the creation of VM groups within a vApp. Once these groups are defined, an administrator can create VM-VM affinity or anti-affinity rules that apply to the VMs within those groups. This mechanism is the Cloud Director equivalent of vSphere DRS rules and is the correct way to maintain placement logic within the multi-tenant environment. Directly manipulating DRS in vSphere bypasses Cloud Director's control, and there is no direct import option for these specific settings.

Correct answers: vSphere Storage Policies; VMware Cloud Director Storage Profiles

To offer tiered storage, the administrator must first define Storage Policies in vCenter Server that correspond to the underlying datastores (e.g., a 'Gold' policy tagged to the all-flash vSAN datastore). Then, within VMware Cloud Director, these vSphere Storage Policies are imported and made available to the Provider VDC. These are then presented as Storage Profiles within the Organization VDC, allowing tenants to select them for their VMs. A VM's storage class is just metadata, and VM templates use policies but don't define them.

Correct answer: Copy the certificate files to each cell, then run the `cell-management-tool certificates` command locally on each cell to import the same certificate and key.

Certificate management in a multi-cell VMware Cloud Director deployment must be performed individually on each cell. The `cell-management-tool` is the correct command-line utility for this task. The administrator must copy the certificate, private key, and any intermediate certificates to each cell and then run the command locally on each one to replace the existing certificates. This action is not replicated automatically from the primary cell, and while the VAMI is used for some appliance management, advanced certificate replacement is done via the CMT.

Correct answer: The number of VMs quota for the Organization VDC has been reached.

Organization VDCs have multiple quota types. While CPU and Memory are common, there is also a quota for the total number of virtual machines (both powered on and off) that can exist in the VDC. In this scenario, the most probable cause is that the tenant has hit this VM count limit. The powered-off VMs still count towards this total quota, preventing the creation of new ones even if compute resources are available.

Correct answer: False

An External Network in VMware Cloud Director provides northbound connectivity for tenants. In an NSX-T backed environment, this connectivity is provided by a Tier-0 Logical Router, which connects to the physical network infrastructure. Tier-1 Logical Routers are used for tenant-specific routing and are typically created and managed by Cloud Director as part of an Edge Gateway, not used to back an External Network directly.

Correct answer: A Layer 2 VPN (L2 VPN) service on the tenant's Edge Gateway.

The requirement to extend a Layer 2 network segment specifically points to the need for an L2 VPN. This service, configured on the tenant's Edge Gateway (backed by NSX), allows for the stretching of a broadcast domain between the on-premises environment and the Cloud Director VDC. This facilitates VM migration without changing IP addresses. A standard IPsec VPN provides L3 connectivity but does not extend the L2 segment.

Correct answer: Publish the catalog in the New York instance and create a Subscribed Catalog in the London instance that syncs from the published feed.

The correct method for sharing catalogs between different VMware Cloud Director instances is the publish and subscribe model. The source catalog (New York) is published, creating a shareable URL. The destination instance (London) then creates a subscribed catalog pointing to that URL. This model periodically synchronizes the catalog content, storing a local copy in the London instance. This ensures that when London tenants deploy VMs from the catalog, the data is served locally, avoiding performance issues caused by the high-latency WAN link.

Correct answer: Roll back only the failed cell to its pre-upgrade snapshot, analyze the upgrade logs on that cell, and then re-attempt its upgrade.

The recommended procedure for a failed cell upgrade (when the primary has succeeded) is to not roll back the entire environment. The primary cell and database have already been modified. The correct action is to revert only the failed cell to its snapshot, review its specific upgrade logs (e.g., in /opt/vmware/vcloud-director/logs/) to diagnose the failure, resolve the underlying issue, and then try upgrading that cell again. Reverting the entire cluster is a last resort and not the immediate next step.

Correct answer: Add both storage policies to the Provider VDC and set the 'Hybrid-DS' policy as the default.

To achieve this, the administrator must make both underlying storage policies (one for each datastore) available to the Provider VDC. Then, by setting the policy corresponding to 'Hybrid-DS' as the default, any VM provisioned without an explicit storage policy selection will be placed on that datastore. The 'All-Flash-DS' policy is still available to be selected by tenants for specific VMs, fulfilling the premium offering requirement.

Correct answers: Pay-As-You-Go; Reservation Pool; Flex; Allocation Pool

The valid allocation models for an Organization VDC are Pay-As-You-Go, Allocation Pool, Reservation Pool, and Flex. 'On-Demand' and 'Burstable' are not standard VCD allocation model names. Pay-As-You-Go allocates resources on demand, Reservation Pool guarantees resources, and Flex provides a hybrid approach.