VMware 2V0-17.25 VMware Cloud Foundation 9.0 Administrator Exam Practice Test

In VMware Cloud Foundation 9.0, the construct of VM Applications Organizations was deprecated in favor of All Applications Organizations. The documentation highlights this change:

“Organizations for All Applications provide a unified model for managing both VM and Kubernetes workloads. They support third-party integrations such as Tanzu Salt and Active Directory, and enable deployments to Native Public Cloud endpoints.”

Since the customer upgraded from VCF 5.2, their first new Organization after the upgrade must use the All Applications model. VM Applications Organizations (Option A) are legacy and do not support the full feature set such as NPC or third-party integrations. Option C is incorrect because the Fleet Management API is for monitoring and operational insights, not for creating Organizations.

Therefore, the administrator must create the new Organization as an All Applications Organization in the VCF Automation Provider Management Portal.

TheVCF 9.0 Architecture Guideoutlines validprincipal storage optionsfor the management domain. It states: “The management domain must be deployed using vSAN, NFS, or Fibre Channel (FC). Supported protocols include NFSv3 and VMFS on FC.” vSAN (including OSA) is the default recommended option, but NFSv3 and VMFS on FC are also supported for environments where external storage arrays are required.

NVMe/TCP and vVols arenot supportedfor the initial management domain’s principal storage. vVols may be used in workload domains after deployment, but they are not a supported foundation for the management domain. Therefore, the three correct storage solutions for the first management workload domain are:VMFS on FC, NFSv3, and vSAN OSA.

TheVCF 9.0 Upgrade Documentationclearly outlines a staged upgrade sequence: “The upgrade to VCF 9.0 begins with the SDDC Manager upgrade. Only after SDDC Manager is upgraded to 9.0 are the other component bundles (vCenter, ESXi, NSX, Operations) made available for download and application.”

This design ensures SDDC Manager is compatible with the lifecycle operations required for the rest of the environment. If SDDC Manager is not upgraded first, it cannot process or display other bundles. Offline repositories (A), proxy servers (B), or ASYNC tools (C) do not affect the bundle visibility order. Therefore, the correct answer isD. SDDC Manager must be upgraded first.

TheVCF Operations Dashboards Guidedescribes theStorage Overview dashboard:

“The Storage Overview dashboard provides visibility into capacity, performance, and health across vSAN and non-vSAN datastores. Administrators can track datastore utilization, latency, throughput, and availability from a single pane of glass.”

Diagnostic Findings (B) shows troubleshooting insights, not full storage details. Data Protection & Recovery (C) covers backup/replication information. VCF Health (D) focuses on SDDC Manager, vCenter, NSX, and host health, not datastore metrics.

Therefore, the required datastore overview is accessed through theStorage Overview dashboardin VCF Operations.

TheVCF 9.0 Upgrade Guidespecifies 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 areoptional add-onsfor extended visibility. Thus, the required three are:A, D, F.

The documentation clarifies the scenario when a password is changedoutsideof 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 useRemediate passwordto synchronize credentials and restore management from VCF Operations.

===========

TheVCF 9.0 Operations Guide – Metrics and Super Metricsexplains thatsuper metricsare 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 theaverage health score of all VMs across multiple clusters, the administrator must create asuper metricand then visualize it in a dashboard.

In VMware Cloud Foundation (VCF) 9.0, the VCF Service Broker is the component responsible for providing a self-service catalog of available services, blueprints, and content to end users in the VM Apps tenant. The documentation explains:

“Service Broker acts as the catalog service for VM-based and cloud-native applications, allowing organizations to expose curated content to end users while applying policies, constraints, and governance.”

VCF Operations Orchestrator (A) provides workflow automation but does not expose services directly in a self-service catalog.

VCF Assembler (B) is used for designing blueprints and application templates but not for publishing them to end users.

VCF Config (D) is responsible for infrastructure configuration management and desired state compliance, not catalog services.

Thus, the correct component for the catalog is the VCF Service Broker.

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 underOrganization 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 underBase Settings(E) would apply globally rather than inheriting from the Organization Policy.

VCF 9.0 documents two Operations for Logs/Operations models—Simple (Standard)andHigh Availability (Cluster)—and highlight thatSimpleis the minimal footprint option intended for test/dev: “Architecture flexibility: Can be deployed in a Simple or Highly Available Cluster deployment. Recommended deployment is a HA Cluster… Simple deployment is for test/dev environments, it is not for production use cases.”

By contrast, HA/clustered models increase resources to provide redundancy at scale. Since the requirement is thesmallest resource footprint, theSimplemodel is the correct selection. (Stretched/Continuous Availability options are not listed VCF Operations models in this context.)

TheVCF 9.0 Operations Guide – Views and Reportsexplains the four types of views available for custom dashboards:

Object Relationship View:Displays dependencies and hierarchy between objects (for example, VMs, hosts, datastores) but does not provide exportable tabular data.

Scoreboard View:Provides a high-level KPI visualization of a few key objects but is not intended for large tabular exports.

List View (Correct):Displays tabular data across many objects, such as CPU, memory, and disk metrics for VMs. The guide states:“List views are useful when you want to compare metrics across multiple objects and can be exported to CSV for further analysis.”

Trend View:Focuses on historical data and growth over time, but export to CSV is not its primary purpose.

Because the security team requires bothtabular comparison of VM resource usageand the ability toexport the data to CSV, theList Viewis the only option that meets both requirements.

TheVCF 9.0 Deployment Guidenotes: “All ESXi hosts must be installed with a supported ESXi version using a VMware ISO before they are commissioned into SDDC Manager. Commissioning is always performed via the management domain vCenter.” The new workload domain vCenter does not exist until the domain is deployed, ruling out option A. The VCF Installer is used for initial bring-up, not workload domain expansion (E). Therefore, the two required steps are:install ESXi using a valid ISO (D)andcommission hosts via the management domain vCenter (B).

TheVCF Automation Costing and Pricing Guideexplains:

“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.

VCF 9.0 introducesLog Data Transferinitiatedfrom VCF Operations. The docs say: “You can transfer log data for up to 90 days from Aria Operations for Logs 8.x… The migrated logs are stored in VCF Operations for logs.” and “To transfer logs… navigate to the Logs Data Transfer card in Administration > Control Panel… click the INITIATE TRANSFER button… You can select the duration of logs to transfer…” (emphasis added).

They further clarify that simple forwardingdoes not transfer already ingested logs: “Forward logs… does not transfer already ingested logs. Transfer historical logs up to 90 days… using the Log Data Transfer feature in VCF Operations.”

Hence, the correct action is toinitiate the transfer in VCF Operations (Administration > Control Panel > Logs Data Transfer).

===========

TheVMware Cloud Foundation 9.0 and vSphere with Tanzu documentationdescribes the Container Storage Interface (CSI) as follows:

“The vSphere CSI driver allows vSphere storage to be exposed as persistent storage to containerized applications running on Kubernetes clusters. The driver implements the Kubernetes CSI specification and enables dynamic provisioning, attach/detach, and snapshot operations for persistent volumes.”

Key points from the documentation:

CSI is not limited tovSphere object storage(A). It works with vSAN, VMFS, NFS, and other vSphere-supported datastores.

Its purpose is to providepersistent storage(B), so containerized workloads have data that outlives pod lifecycles.

CSI is not restricted to “cloud native storage only” (C); it is the standard interface for Kubernetes persistent storage.

CSI is not used forephemeral storage(D); ephemeral storage is provided by local container runtimes and does not require CSI.

Therefore, the correct description is that CSI is aplug-in that allows providers to expose storage as persistent storageto Kubernetes workloads running in vSphere Supervisor clusters.

According to the VCF 9.0 Operations and vSAN Integration Guide, performance metrics in the vSAN Cluster Performance widget are only available when the vSAN Performance Service is enabled. The documentation states:

“The vSAN Performance Service must be enabled in vCenter Server for each vSAN cluster to collect and visualize performance statistics in VCF Operations. Without this service, performance dashboards and widgets will not display data.”

Option A (Support Insight) relates to telemetry with VMware, not performance widgets.

Option B (Cloud proxy as Collector) is required for general collection but not specific to vSAN widget visibility.

Option C (SMART data collection) provides disk health analytics, not cluster-level performance stats.

Option D is correct, because enabling the vSAN Performance Service ensures that VCF Operations receives and displays data in the vSAN Performance dashboards.

Therefore, the administrator must enable the vSAN Performance Service for all vSAN clusters in vCenter.

TheVCF 9.0 Design Guidehighlights that for resiliency across sites withRPO = 0, the recommended approach is avSAN Stretched Cluster. Documentation states: “Stretched clusters provide site-level resilience by mirroring data across two fault domains (sites). In the event of a full site outage, workloads remain available with no data loss (RPO = 0).” Relocating six hosts to another site creates the two fault domains required for vSAN Stretched Cluster. Options B and C provide backup or redundancy but not synchronous replication with zero RPO. Option D (fault domains) protects against host/rack failures, not entire data center loss. Therefore, the correct solution is torelocate hosts and configure a stretched cluster.

According to theVCF 9.0 Container Registry Documentation, Harbor is defined as:

“Harbor is an open source registry that secures artifacts with policies and role-based access control, ensures images are scanned and free from vulnerabilities, and signs images as trusted.”

This description aligns exactly with option A. Harbor is not Bitnami (B), though it integrates with open-source images. It includes vulnerability scanning but is not only an image scanner (C). It does not require GitHub as a source (D); Harbor can integrate with multiple registries.

Therefore, Harbor’s primary role within VCF is to act as asecure image registry with RBAC, scanning, and signing capabilities.