2V0-17.25 VMware Cloud Foundation 9.0 Administrator Free Practice Exam Questions (2026 Updated)

The VCF 9.0 Upgrade Guide specifies required components when converting from a vSphere-only deployment to full VCF. The must-deploy services include:

VCF Operations fleet management – central monitoring of multiple instances.

VCF Operations – core operational monitoring platform.

VCF Operations Collector – required for data ingestion from vSphere, NSX, and vSAN.The Identity Broker is already embedded with VCF 9.0 SSO, while VCF Operations for Logs and Networks are optional add-ons for extended visibility. Thus, the required three are: A, D, F.

In VMware Cloud Foundation (VCF) 9.0, the licensing architecture has undergone a fundamental shift to simplify the management of large-scale deployments. The legacy method of managing individual 25-character license keys for every component (ESXi, vCenter, NSX, etc.) has been replaced by a unified, subscription-based License File model managed through VCF Operations.

According to the VCF 9.0 Licensing and Administration Guide:

Register the VCF Operations instance with the VCF Business Services console (B): This is the mandatory first step. VCF Operations must be linked to the cloud-based VCF Business Services console (vcf.broadcom.com). This registration allows the environment to sync entitlements and report usage.

Add the license file from the VCF Business Services console to VCF Operations (A): Unlike previous versions that used keys, VCF 9.0 utilizes a "Secure License File" (or an activation code that retrieves it). For environments without direct internet access (Disconnected Mode), the administrator must manually download this file from the Business Services console and upload it to the VCF Operations interface.

Assign licenses to vCenter instances from VCF Operations (F): Once the license file is added to VCF Operations, the "pool" of capacity (measured in Cores or TiBs) becomes available. The administrator then assigns the license specifically to the vCenter Server instances. Documentation states: "License your vCenter, ESX hosts, NSX, VCF Operations, and other components by assigning the license to the vCenter instance." The vCenter then automatically handles the downstream entitlement for the hosts and integrated services.

Why other options are incorrect:

C: While NSX is licensed as part of the fleet, the administrative action in VCF 9.0 is to assign the license to the vCenter instance, which then licenses the "connected assets."

D & E: VCF 9.0 specifically "eliminates the need to manage multiple license keys" (except for certain legacy add-ons). The core fleet licensing uses a single License File rather than individual keys for every component.

VCF 9.0 describes the VKS architecture and explicitly notes: “The Cluster API provides declarative, Kubernetes-style APIs for cluster creation, configuration, and management.” Inputs include resources describing the cluster, VMs, and add-ons. Provisioning flows also present ClusterClass/Cluster API as the supported “cluster type” when creating a Kubernetes cluster via self-service. These extracts confirm that Cluster API is the foundational component used by VMware Kubernetes Service (VKS) on vSphere Supervisor to bootstrap and manage Kubernetes workload clusters in VCF 9.0.

===========

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)

The requirement is to ensure DNS records are created only when a domain name is provided.

Since the blueprint includes a custom property for domainName, the correct conditional logic in the event subscription must validate that this property is not null.

Adding the condition:

event.data.customProperties['domainName'] != null

ensures the workflow executes only when the domain name is provided.

Option B validates hostname instead of domain name.

Option A controls workflow blocking, not conditional execution.

Option C relates to cleanup, not creation condition validation.

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.

Velero is an open-source Kubernetes backup and restore solution integrated into VMware Cloud Foundation for Kubernetes management. The VCF 9.0 Kubernetes Services Documentation describes it as:

“Velero provides backup, recovery, and migration of Kubernetes cluster resources and persistent volumes.”

Key functionality includes:

Backup and restore of Kubernetes objects such as deployments, services, and namespaces.

Data protection for persistent volumes via storage snapshots.

Migration capabilities across clusters.

Analysis of incorrect options:

Publishing DNS records (A) is handled by CoreDNS or external DNS integrations, not Velero.

Monitoring cluster services (B) is the role of Kubernetes health checks and observability tools like Prometheus, not Velero.

Collecting logs and data (C) is done by logging stacks such as Fluent Bit or VCF Operations for Logs.

Therefore, Velero’s primary role is backup and restore of Kubernetes clusters.

In VMware Cloud Foundation 9.0, network security and segment integrity are maintained through Segment Security Profiles. These profiles are applied to NSX segments to define what type of traffic is permitted to originate from or be received by the virtual machines attached to that segment.

According to the VCF 9.0 (NSX) Networking and Security Guide:

The Default Segment Security Profile is designed with a "Zero Trust" approach for foundational services. One of its key default settings is DHCP Server Block, which is set to Yes. This is a security measure to prevent "rogue" DHCP servers from being accidentally or maliciously connected to a segment and disrupting the network by handing out unauthorized IP addresses.

When an administrator intentionally places a legitimate DHCP server on a segment:

Segment Security Profile: The "DHCP Server Block" feature resides specifically within the Segment Security Profile, not the IP Discovery profile (which handles how NSX learns IP addresses via ARP/DHCP snooping).

Cloning vs. Editing: In VCF 9.0, the "Default" profiles are system-defined. While some default settings can be edited in certain versions, the architectural best practice and documented procedure for production environments is to Clone the default profile. This creates a custom profile where the DHCP Server Block can be set to No, allowing the DHCP server's "Offer" and "ACK" packets to pass through the segment.

Application: Once the cloned profile is modified, it must be manually applied to the specific segment where the virtual desktops and the DHCP server reside.

VCF 9.0 licensing is managed through VCF Operations and the VCF Business Services console. The product requires periodic license updates even in connected mode. The documentation states explicitly: “You must update your licenses at least once every 6 months (180 days). If license usage data is not submitted… your licenses are treated as expired, your hosts are disconnected from the vCenter instance, and you cannot start any workload operations.” This language is repeated in the Licensing Overview and Upgrade/Registration sections, confirming the 180-day requirement applies to both connected and disconnected modes (in connected mode usage submission is automated, but you still must perform an update action). Therefore, the correct interval is 180 days.

The VCF 9.0 Kubernetes Service documentation confirms that Antrea is the default CNI used for VMware Kubernetes Service (VKS) workload clusters.

“When deploying a new VKS workload cluster, the Antrea Container Networking Interface is automatically enabled by default to provide pod-to-pod and pod-to-service networking. Antrea is fully integrated with NSX-T for advanced policy control.”

Flannel, Calico, and Cilium are widely used CNIs in upstream Kubernetes but are not the default in VCF. Administrators can optionally integrate with third-party CNIs, but the supported default choice is Antrea.

The VCF Automation documentation defines its primary use cases as:

Self-Service Catalog – “VCF Automation Service Broker provides a catalog for developers and operators to request services and blueprints.”

Application Dependency Mapping – achieved through integration with VCF Operations for Networks. The guide highlights: “Developers can discover application relationships and map dependencies through automated workflows in VCF Automation.”Alerting (A) is handled by VCF Operations, not Automation. VPC implementation (B) and Private AI (D) are supported solutions but not direct Automation use cases. Therefore, the correct answers are C (Self-Service Catalog) and E (Application Dependency Mapping).

VCF Operations primarily focuses on metrics, performance, and health monitoring. However, detailed event-level data, log entries, and historical audit records are not fully captured unless log aggregation is enabled.

The VMware Cloud Foundation 9.0 documentation explains:

“VCF Operations for Logs provides centralized log aggregation and analytics across all VCF components, including ESXi, vCenter, NSX, and other infrastructure services.”

This solution enhances troubleshooting by:

Collecting syslogs and events from infrastructure components

Providing searchable log data

Correlating events across services

Retaining detailed historical log information

Other options are incorrect:

Management Pack (A) extends metrics, not detailed logs.

VCF Automation (B) is unrelated to troubleshooting logs.

Operations Diagnostics (C) is not the primary log aggregation solution.

Therefore, to capture missing event data for future incidents, the administrator should deploy VCF Operations for Logs.

The VCF 9.0 Operations Guide – Metrics and Super Metrics explains that super metrics are used when administrators need to aggregate or compute new values from existing metrics. Super metrics can be applied across multiple objects, such as aggregating the health score of all VMs in a fleet.

The documentation states:

“A super metric is a user-defined formula that calculates a value derived from one or more existing metrics. Super metrics can be applied across objects to provide aggregate insights such as averages or totals.”

Dashboard (A): Dashboards can display metrics but cannot compute new aggregated values on their own.

Symptom (C): Used to define conditions that trigger alerts, not to compute average health values.

Alert (D): Alerts notify administrators of issues but do not calculate averages across many VMs.

Therefore, to display the average health score of all VMs across multiple clusters, the administrator must create a super metric and then visualize it in a dashboard.

The VCF 9.0 Service Mesh Integration Guide defines Istio as: “Istio Service Mesh provides an infrastructure layer that transparently handles service-to-service communication, securing, observing, and controlling traffic between microservices.” The key purpose is enabling structured and observable communication between applications. While Istio includes discovery and load balancing, those are features, not the overarching purpose. A centralized routing table (Option D) is not the core definition. VMware documentation highlights Istio’s role in service-to-service communication, observability, and policy enforcement within the service mesh. Therefore, the correct answer is B.

The documentation clarifies the scenario when a password is changed outside of VCF Operations: “When an error occurs, for example after a password expires, you must manually reset the password in the component product. After you reset the password in a component, you must remediate the password in VCF Operations.” “Password Rotation” is different—it “allows you to orchestrate the rotation” of stored credentials (a planned, VCF-driven change), not reconcile an externally altered password. Therefore, after the direct password change in vCenter, the correct recovery step in VCF Operations is to use Remediate password to synchronize credentials and restore management from VCF Operations.

===========

When using Fibre Channel (FC) as the principal storage type for a workload domain in VMware Cloud Foundation, storage must already be provisioned and visible to all participating ESXi hosts.

The VCF documentation specifies that for VMFS on FC deployments:

Storage LUNs must be created on the SAN.

The LUNs must be zoned and presented to all ESXi hosts.

Hosts must be able to detect the presented LUNs before domain creation.

Incorrect options:

SSD disks (A) are required for vSAN, not Fibre Channel.

Port binding (B) is required for iSCSI, not FC.

A VMkernel interface for storage (D) is required for IP-based storage (NFS/iSCSI), not Fibre Channel.

Therefore, the key prerequisite is ensuring LUNs are presented to all ESXi hosts.

In VMware Cloud Foundation 9.0, when deploying vSphere Supervisor (formerly part of Tanzu) specifically with VMware NSX as the networking provider, the architecture relies on the high-performance routing capabilities of the NSX fabric.

According to the VCF 9.0 Developer Ready Infrastructure Guide:

When NSX is selected as the networking stack for the Supervisor, the system utilizes Distributed Gateways (T1) to handle the routing for the supervisor's internal and external traffic.

Distributed Gateway (C): In an NSX-integrated Supervisor deployment, the East-West traffic and the localized routing for the Kubernetes Control Plane and Pod networking are handled by the Distributed Gateway. This ensures that routing occurs at the host level (kernel space) where possible, minimizing latency and "hairpinning" to a centralized edge node.

Why others are incorrect: * Avi Load Balancer (A): While Avi (NSX Advanced Load Balancer) is the preferred load balancer for VCF 9.0, the question asks for the "networking connectivity type" for the Supervisor deployment itself. Avi provides the Load Balancing service (ingress/egress), but the underlying routing connectivity type is the Distributed Gateway.

Data Network Subnet (B): This is a general networking term and not a specific "connectivity type" construct within the NSX Supervisor deployment workflow.

Centralized Gateway (D): While a Tier-0/Tier-1 gateway can have centralized services (like NAT or Statefull Firewall), the standard connectivity model for Supervisor namespaces to maintain performance and scale across the VCF hosts is the Distributed Gateway.

In VMware Cloud Foundation 9.0, the VCF Fleet Disaster Recovery Design Model explicitly requires deployment of VMware Live Recovery (VLR) to provide:

Cross-instance disaster recovery

Site pairing between regions

Protection of management and workload domains

Orchestrated failover and failback

From the VCF 9.0 Fleet Architecture documentation:

“To implement a Fleet-level disaster recovery model across multiple VCF instances in different regions, deploy VMware Live Recovery to provide orchestration, replication, and recovery operations between paired VCF instances.”

The Fleet DR design requires:

A primary VCF instance (Region A)

A secondary VCF instance (Region B)

VMware Live Recovery to manage DR workflows across instances

Other options are incorrect:

DSM – Provides database-as-a-service capabilities, not DR orchestration.

VCF Operations HCX – Used for workload mobility, not DR orchestration.

VCF Operations – Provides monitoring and observability, not DR functionality.

Document reference (VCF 9.0):

VMware Cloud Foundation 9.0 → VCF Fleet Architecture → Disaster Recovery Design Model

VMware Cloud Foundation 9.0 → VMware Live Recovery Integration with VCF