VMware Cloud Foundation Specialist (VCF v2) Free Sample Questions

The Standard Architecture model deploys the management workload on a dedicated management domain, physically separating it from VI workload domains. This meets the compliance requirement. A vSAN-based management domain requires a minimum of 4 ESXi hosts to provide N+1 redundancy (FTT=1). A Consolidated Architecture runs management and compute workloads on the same cluster, which violates the stated requirement.

Cloud Builder validates NTP reachability from the ESXi hosts themselves. If FQDNs are used for the NTP servers, the hosts must be able to resolve these names. During the initial bring-up, ESXi hosts may not have DNS configured until later in the process. Using IP addresses for NTP servers in the Deployment Parameter workbook is the recommended approach to avoid this dependency. The other options are less likely as Cloud Builder itself, not just the ESXi hosts, needs connectivity, but the error is specific to host reachability.

When enabling vSphere with Tanzu, SDDC Manager requires several non-routable CIDR blocks to be defined for NSX-T to manage. The Namespace Network CIDR (for Pods), Ingress CIDR (for services exposed externally via NSX LB), and Egress CIDR (for SNAT'd outbound traffic) are the primary ranges. The Management Network is for the Supervisor Control Plane VMs and is typically a routable network, not a private overlay.

A vSAN Stretched Cluster provides synchronous replication between two sites, achieving an RPO of zero. Combined with vSphere HA, it offers automated failover. The 3ms latency is well within the 5ms RTT requirement for stretched clusters. NSX Federation provides network and security policy consistency across sites but does not handle storage replication or automated VM failover. Site Recovery Manager provides automated disaster recovery orchestration but typically does not achieve RPO=0 without synchronous storage replication.

VMware Cloud Foundation leverages vSphere Lifecycle Manager (vLCM) for managing host compliance. The correct, VCF-integrated approach is to modify the cluster's desired state image within vLCM to include the required driver. After updating the image, the cluster can be remediated to bring all hosts into compliance. Once vLCM reports compliance, the SDDC Manager pre-check will pass. Manual installation (ESXCLI) would cause drift from the desired state image and is not the recommended practice.

For SDDC Manager to integrate with a Microsoft AD CS server, the Certificate Authority Web Enrollment role service must be installed and configured to use Basic Authentication. This allows SDDC Manager to programmatically submit Certificate Signing Requests (CSRs) using a service account's username and password.

The Supportability and Serviceability (SoS) utility is the primary command-line tool used on the SDDC Manager appliance for health checks and log collection. The sos --collect-logs command, with appropriate flags for specific components and domains, gathers all necessary support bundles from the VCF management components and aggregates them into a single tarball for easy submission to VMware support.

This is true. One of the design choices when creating a new VI workload domain is whether to deploy a new, dedicated NSX Manager cluster for it or to share the existing NSX Manager cluster from the management domain. Sharing the management domain's NSX Manager reduces management overhead and resource consumption, and is a common practice for many deployments.

The SDDC Manager 'Decommission Host' workflow automates several steps: it places the host into maintenance mode (ensuring vSAN data accessibility), evacuates VMs, removes the host from the vSAN cluster, and removes it from the VCF inventory. However, it does not remove the host from the vCenter inventory; the host becomes a standalone host within the data center object, disconnected from the cluster.

The link between Kubernetes persistent storage requests and the underlying vSphere storage is the StorageClass object. The vSphere Container Storage Interface (CSI) driver reads the StorageClass definition. A vSphere administrator creates a StorageClass manifest (.yaml file) that references the specific vSAN storage policy by name. Once this StorageClass is applied to the Kubernetes cluster, developers can reference it in their PVC definitions to provision storage with the desired characteristics.