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

A workload domain is the appropriate lifecycle boundary when components must be managed independently. VCF 9.0 defines a workload domain as a logical pool containing its own vCenter and one or more vSphere clusters, while NSX Manager can be shared with other workload domains.

The VCF architecture documentation also identifies independent lifecycle management as a benefit of workload domains. A separate workload domain provides its own vCenter management boundary, allowing the new cluster and its associated components to be scaled and lifecycle-managed separately from existing domains.

A new NSX instance is not required simply to obtain independent lifecycle and scaling. VCF explicitly supports sharing an NSX Manager among workload domains, and VCF 9.0 describes shared NSX as a supported cross-workload-domain architecture. Therefore, creating a new workload domain while sharing the existing NSX instance satisfies the requirement with less management overhead than deploying another NSX stack.

The VCF 9.0 Operations Access Control Guide describes how dashboard sharing and user access is managed:

Identity Broker Authentication (D):All external users must authenticate via the VCF Identity Broker, which integrates with Active Directory, LDAP, or other identity providers. Documentation states: “Identity Broker provides single sign-on and federation, ensuring users are authenticated consistently across VCF Operations and Automation services.”

Grant Access to Dashboard (E):After authentication, the administrator must explicitly grant access to the dashboard for the specified group. This ensures that only the intended users can view or interact with the dashboard.

Set Time-Bound Access (C):VCF Operations supports time-bound access policies. The documentation specifies: “Access can be granted with an expiration period, ensuring access is automatically revoked after the configured interval (for example, 90 days).” This aligns with the 3-month requirement.

Other options are not suitable:

Reports (A) only send static data, not interactive dashboard access.

Embedded code (B, F) bypasses access control and does not provide authentication or time-limited sharing, which violates the security requirement.

Thus, the correct three steps are: Use Identity Broker (D), Grant access to dashboard (E), and Configure 3-month access expiration (C).

VCF Automation 9.0 defines Organizations for All Applications as the primary multi-tenancy model for environments that need both traditional VM workloads and modern Kubernetes-based workloads. The documentation states that an All Apps organization can run “a wide variety of applications, including virtual machines (VMs), Kubernetes, data services, and so on.”

The same documentation specifies that these organizations are created from the VCF Automation Provider Management Portal and use underlying vSphere Supervisor infrastructure. This directly satisfies the requirements for VKS and VM deployment.

By contrast, a VM Apps organization is primarily intended for customers continuing legacy Aria Automation-style VM application provisioning. The documentation states that it is most suitable for customers who want to continue “VM-based applications” without disrupting existing operations. It is not the correct choice when Kubernetes and modern integrations are required.

To calculate the elapsed time correctly, we must identify the specific start and end points defined in the VMware operations lifecycle.

Default Collection Interval: VCF Operations collects data every 5 minutes.

Symptom Triggering (The Start Point): A symptom does not " trigger " the moment a threshold is breached. Instead, it triggers only after the Wait Cycle is completed. With a Wait Cycle of 2, the symptom triggers at the 10-minute mark ($2 \times 5\text{ minutes}$). This is the " Triggering " event referred to in the question.

Alert Cancellation (The End Point): For an alert to cancel automatically, the condition must remain " False " for the duration of the Cancel Cycle. With a Cancel Cycle of 2, this requires an additional 10 minutes ($2 \times 5\text{ minutes}$) after the condition has cleared.

The Timeline Breakdown:

T+0 to T+10: Wait Cycles are occurring (Alert is not yet triggered).

T+10: Symptom Triggers (Event A).

T+10 to T+20: Cancel Cycles are occurring (Assuming the condition became false immediately at T+10).

T+20: Alert Automatically Cancels (Event B).

The time elapsed between Event A (Trigger) and Event B (Cancel) is exactly 10 minutes.

The correct solution is Content Library. VMware vSphere and VCF documentation define content libraries as container objects for storing and sharing VM templates, vApp templates, ISO images, text files, and other content. The documentation specifically states that content libraries can be used to “share content across vCenter instances in the same or different locations,” which directly matches the requirement to centrally distribute content across multiple physical sites and VCF instances.

VCF 9.0 further explains that content libraries can distribute VM and vApp templates, ISO images, and other files across vCenter instances, promoting “consistency, compliance, efficiency, and automation in deploying workloads at scale.” Local libraries can be published, while subscribed libraries synchronize content from a publisher.

A vSAN Storage Cluster and shared VMFS datastore provide storage capacity but are not content-distribution mechanisms. Network File Copy is a file-transfer operation rather than a centralized management and synchronization service.

The VCF 9.0 Convergence and Migration Guide outlines prerequisites and unsupported configurations when moving from a standalone vSphere deployment into VCF-managed workload domains.

Enhanced Linked Mode (ELM) must be removed:VCF does not support multiple vCenters joined in Enhanced Linked Mode. Each workload domain has its own dedicated vCenter instance, managed by SDDC Manager. The documentation states:“Before convergence, Enhanced Linked Mode must be deactivated. VCF requires independent vCenters for each workload domain.”

Lifecycle Manager must use Images only:VCF lifecycle operations are exclusively image-based. Baselines are not supported.“All clusters managed by VCF must be converted to vSphere Lifecycle Manager image-based lifecycle management prior to convergence.”

Other options are not required:

25 Gbps uplinks (A) are recommended for high throughput but not mandatory; 10 Gbps uplinks are supported.

An additional vMotion VMkernel (C) is not required by default, as standard vMotion networking is included in convergence designs.

vSphere Standard Switches (D) are not supported; VCF requires Distributed Switches, and existing vDS configurations can be adapted.

Therefore, the two configurations that must change are: Deactivate Enhanced Linked Mode (B) and switch Lifecycle Manager to Images only (E).

https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/building-your-private-cloud-infrastructure/managing-network-connectivity-in-vcenter/managing-distributed-network-connectivity.html

After configuring SSO in VCF, administrators must assign appropriate roles in the management components to grant elevated privileges.

VCF 9.0 architecture includes these primary management components:

vCenter Server (A) – Manages clusters and VMs.

NSX Manager (B) – Manages networking and security services.

VCF Operations (D) – Provides monitoring and operational visibility.

Roles must be assigned within each of these systems to allow full administrative access.

vSAN (E) and ESX (F) are managed through vCenter, not independently assigned service roles.

VCF Installer (C) is used for deployment and does not require ongoing RBAC assignments for operations.

Therefore, the correct components are vCenter, NSX Manager, and VCF Operations.

VCF Automation event subscriptions support Boolean conditions that determine whether the associated workflow runs. VCF 9.0 states that filters can be applied to subscriptions so that “the event and workflow only triggers if the Boolean expression is ‘true’.” Conditions can access event payload values through event.data, and the != operator is explicitly supported.

Because the stated requirement is specifically to create DNS records only when domainName has been provided, the subscription must test the corresponding custom property:

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

Option C checks hostname, which does not satisfy the stated condition. Option B addresses execution ordering: blocking subscriptions prevent another matching subscription from receiving the event until the current runnable item finishes. Option A is relevant to cleanup if the primary workflow fails because VCF supports recovery runnable items for blocking subscriptions, but it does not determine whether the DNS workflow should run based on the presence of the domain name.

A VCF Automation region is built from one or more vSphere Supervisors, and the participating vCenter instances must be integrated with an NSX Manager. VMware Cloud Foundation 9.0 states that before creating a region, administrators must verify that the vCenter instance has a Supervisor enabled.

The documentation also states that VCF Automation creates a region by grouping Supervisors from one or more vCenter instances, provided those vCenter instances are configured with the same NSX instance. A single NSX Manager must therefore integrate with all vCenters participating in a particular region.

Options A and E apply when multiple Supervisors/vCenters are combined into one region because VM classes and storage classes must then be identical across those participating instances. In this scenario, the design is for three separate service-class regions backed by three workload domains, so identical classes across all vCenters are not inherently required. Region quotas are created after regions exist and are assigned to Organizations; they are not prerequisites for creating the regions themselves.

The VCF 9.0 Automation and Orchestration Guide explains how Orchestrator integrates with VCF Automation to provide workflow-driven services such as Active Directory management.

Orchestrator Integration (B):The tenant must be connected to the dedicated Orchestrator instance rather than the embedded one. Documentation notes: “Each tenant can integrate with its own Orchestrator endpoint for workflow execution.”

AD Plugin Configuration (E):The Orchestrator Active Directory plugin must be configured against the development AD only, ensuring that the development team does not impact the production directory.

Publish Workflow (C):The AD user creation workflow must be published to the VCF Automation catalog using the Content Hub. Actions alone are insufficient; workflows are the full automation logic exposed to end users.

Custom Resource Object (F):To enable developers to create and destroy AD accounts, a Custom Resource object must be created in VCF Automation and mapped to the Orchestrator workflows. This provides lifecycle capabilities (create/destroy) in the self-service catalog.

Options A and D are incorrect because publishing only the “action” is not sufficient (workflows are required), and the plugin must not point to production AD. Option G is incorrect because the dedicated Orchestrator has already been deployed, so the embedded Orchestrator is not used.

The Storage Overview dashboard in VCF Operations provides consolidated visibility into storage resources, including:

vSAN datastores

VMFS datastores

NFS datastores

Capacity utilization

Performance metrics

Health indicators

The VCF documentation states:

“The Storage Overview dashboard provides a unified view of storage capacity, performance, and health across vSAN and non-vSAN datastores.”

Other options are not suitable:

VCF Health (A) focuses on component health (vCenter, NSX, ESXi).

Data Protection & Recovery (B) covers backup and DR insights.

Diagnostic Findings (C) highlights detected issues but not comprehensive storage inventory.

Thus, the correct location is the Storage Overview dashboard.

The vSphere 9.0 Resource Management Guide describes Enhanced vMotion Compatibility (EVC) as the mechanism that masks CPU instruction set differences across ESXi hosts, presenting a consistent baseline to VMs.

The documentation states:

“EVC ensures vMotion compatibility across hosts with different CPU generations by exposing a uniform set of CPU features to all virtual machines in the cluster.”

vSphere Fault Tolerance (A): Provides continuous availability for individual VMs but does not address CPU instruction compatibility.

vSphere Availability (B): Refers to HA (High Availability) which handles VM failover, not CPU feature alignment.

Host Affinity Rules (C): Control placement of VMs but cannot solve compatibility between mixed CPU generations.

Enhanced vMotion Compatibility (D): Specifically addresses the requirement for vMotion and DRS across mixed CPU generations, making it the correct answer.