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

Istio Service Mesh provides built-in capabilities for managing service-to-service communication within Kubernetes environments.

The Istio documentation highlights default capabilities including:

Service discovery (C): Automatic detection and routing between services.

Mutual TLS (mTLS) encryption (E): Secure communication between services by default.

Istio does not provide:

Multi-cluster backup/restore (A) — handled by tools such as Velero.

Cluster conformance validation (B).

Advanced container runtime (D) — container runtime is handled by container engines such as containerd.

Thus, the correct answers are Service discovery and Connection encryption.

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.

===========

vSphere Supervisor leverages the Cluster API (CAPI) open-source project to manage the lifecycle of Kubernetes clusters.

Cluster API provides declarative APIs to create, scale, upgrade, and manage Kubernetes clusters. The VMware documentation states:

“VMware Kubernetes Service uses Cluster API components to provision and manage Tanzu Kubernetes clusters on vSphere.”

Incorrect options:

Kubeadm (A) is a Kubernetes bootstrap tool but not the lifecycle engine used by Supervisor.

Contour (B) is an ingress controller.

Grafana (C) is a visualization and monitoring tool.

Thus, the correct answer is Cluster API.

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.

In VMware Cloud Foundation 9.0, pricing policies are configured within VCF Operations (Costing and Chargeback).

From the VCF 9.0 documentation under Cost and Chargeback Configuration:

“Base Settings define the default cost drivers for CPU, memory, and storage that apply across clusters unless overridden by a custom policy.”

To meet the requirement:

CPU, memory, and storage pricing must be identical across all clusters.

A new policy named Resources must be created and applied globally.

Thus:

1️⃣ Create a new policy under Base Settings for resource cost (Option A)

This satisfies:

Same CPU, memory, and storage cost across clusters.

From the documentation regarding policy hierarchy:

“When a custom cost policy is set as default, it applies to all objects that do not have a more specific policy assigned.”

2️⃣ Set “Resources” as the default policy (Option E)

This ensures:

All clusters inherit this pricing model.

Other unspecified settings fall back to default behavior.

From documentation regarding overrides:

“Specific object types such as clusters can have additional cost components defined through child policies that override parent policy settings.”

3️⃣ Create a child policy under “Resources” for SAP HANA cluster VM setup charges (Option F)

This satisfies:

VM setup charges applied only to SAP HANA cluster.

Other clusters remain unaffected.

All other settings remain default.

Why Other Options Are Incorrect

B – Setting Default Policy as default contradicts requirement to create a new named policy “Resources.”

C – VM setup charges should not be in Base Settings (would apply globally).

D – Incorrect hierarchy; policies are structured under custom policy trees, not under “Default Policy” in this context.

Document References (VCF 9.0):

VMware Cloud Foundation 9.0 → VCF Operations → Costing and Chargeback

VMware Cloud Foundation 9.0 → Policy Inheritance and Overrides

VMware Cloud Foundation 9.0 → Base Settings and Custom Cost Policies

According to the VCF 9.0 Operations and Monitoring Guide:

Fleet Management: “VCF Operations Fleet Management enables cross-instance monitoring, unifying health and metrics across multiple VCF instances.”

Operations for Networks: “Provides application and network visibility, dependency mapping, and traffic analytics. Required to complete full-stack monitoring.”

Core VCF Operations is already deployed as part of the management stack and does not need to be added separately. Operations for Logs is optional for log aggregation, not mandatory for full-stack observability. The Management Pack Builder (C) is an add-on tool for custom packs, not a required component. Therefore, the correct two to add for full-stack monitoring are VCF Operations Fleet Management (A) and VCF Operations for Networks (E).

Comprehensive and Detailed Explanation:

The Istio integration in VCF 9.0 defines two main logical groupings for organizing workloads within a service mesh: Cluster groups and Service groups. The documentation notes: “Cluster groups allow you to organize and manage objects across different Kubernetes clusters. Service groups let you aggregate and manage services that share common policies, routing rules, or observability requirements.” .

These groups enable administrators to apply consistent service mesh policies across multiple deployments and clusters. They also simplify administration by centralizing traffic management, routing, and observability of workloads. Security, API, and Node are not Istio-specific grouping constructs but instead are other concepts used elsewhere (e.g., security policies, API endpoints, node objects in Kubernetes). Therefore, the correct group types used in Istio Service Mesh are Cluster and Service groups.

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

The VMware Cloud Foundation 9.0 and vSphere with Tanzu documentation describes 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 to vSphere object storage (A). It works with vSAN, VMFS, NFS, and other vSphere-supported datastores.

Its purpose is to provide persistent 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 for ephemeral storage (D); ephemeral storage is provided by local container runtimes and does not require CSI.

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

Resetting identity management in VCF requires removal of existing identity configurations, including external identity providers and the Identity Broker configuration. The VCF documentation states that to reset identity services, administrators must remove the SSO configuration, including broker settings, and then reconfigure SSO.

Option B ensures complete cleanup of identity integrations.

Option C re-establishes identity management with the correct configuration.

Disabling (D) or reverting (E) is not a supported reset method. Leaving provisioned users/groups (A) would not fully reset identity management.

VCF 9.0 replaces legacy bring-up tooling with the VCF Installer, which provides a deployment wizard that validates configuration before bring-up. The guide describes: “The deployment wizard validates your inputs… and displays errors and warnings if any.” and that administrators “Download and complete the planning and preparation workbook and have the information ready for validating inputs in the deployment wizard.”

While the workbook is used to collect information, the validation of those inputs is performed by the VCF Installer wizard prior to deployment. SDDC Manager is used after bring-up for lifecycle operations, and Cloud Builder is not used in VCF 9.0 deployments. Therefore, VCF Installer is the correct tool for collecting (via wizard prompts) and validating initial deployment inputs.

===========

The VCF 9.0 Automation Guide – Content Sharing Policies describes how to control catalog item visibility. Administrators create Content Sharing Policies to restrict which groups can see specific catalog items.

Steps required for this scenario:

Create a new Content Sharing Policy (D): This policy governs catalog item access.

Add the catalog item to the new policy (B): The Mobile Application Backend blueprint must be explicitly added.

Configure the scope as Project → FitnessTrackerApp (C): This ensures the catalog restriction applies only within the FitnessTrackerApp project.

Add the FTA_LeadDevelopers Group (F): Grants visibility only to this group, fulfilling the requirement that only Lead Developers initially see the item.

Incorrect options:

Deployment Limit Policy (A) controls resource limits, not catalog visibility.

FTA_Developers (E) should not be included, as the requirement is Lead Developers only.

Organization scope (G) would expose the item to all projects, which violates the requirement.

Thus, the administrator must configure a Content Sharing Policy, add the catalog item, scope it to the FitnessTrackerApp project, and restrict it to the Lead Developers group.

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.

To enable the visibility of audit events within the VCF Operations interface, the environment must satisfy specific deployment and configuration prerequisites. Without these steps, audit event information will not be populated.

According to the documentation:

Install VCF Operations for Logs (E): If you have not configured VCF Operations, you will not see any information related to audit events. Therefore, you must install VCF Operations for Logs first.

Configure vCenter Server instances in VCF Operations for Logs (D): You must register the vCenter Server instances in VCF Operations for Logs to ensure the management components are sending the necessary log data to the ingestion engine.

Configure VCF Operations for Logs Integration in VCF Operations (F): After you install VCF Operations for Logs, you must configure the VCF Operations for Logs management pack from the Administration > Integrations page in VCF Operations. This includes configuring the VCF Operations for Logs instances which forward logs to the specific VCF Operations for Logs instance that is integrated with VCF Operations.

vSAN File Services is the appropriate feature because it provides file-sharing capabilities from a vSAN cluster and makes file shares accessible over standard file protocols. This allows file-based storage to be consumed by workloads such as virtual machines and external client systems.

vSAN File Services extends the functionality of a vSAN datastore by providing file shares rather than limiting storage consumption to virtual disks used by VMs. This makes it suitable when the requirement is for storage that needs to be accessible to systems outside the traditional VM datastore model.

The other options do not meet the stated requirement. A vSAN Storage Cluster provides distributed storage primarily as a datastore for virtual infrastructure but does not by itself provide client-accessible file shares. A local VMFS datastore provides block-based storage local to an ESX host and is not intended to provide shared file access to client workstations. A vSAN Stretched Cluster provides site-level availability and resiliency but does not itself address file-sharing requirements.

Therefore, the feature that satisfies the requirement for storage accessible to both client workstations and virtual machines is vSAN File Services.

The VCF 9.0 Operations Documentation identifies Operations for Networks as the key enabler for the Network Operations feature:

“VCF Operations for Networks (formerly vRNI) provides visibility into network traffic flows, NSX fabric health, application dependency mapping, and micro-segmentation planning. It integrates directly into VCF Operations dashboards under Network Operations.”

The vDefend firewall is unrelated, as it provides workload-level security. The VCF Operations Collector is required for telemetry ingestion but does not provide full Network Operations. NSX itself provides the underlying virtual networking, but it must be monitored through VCF Operations for Networks. Therefore, the correct answer is VCF Operations for Networks.

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.

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.

The VCF 9.0 Resource Policy Guide describes IaaS Resource Policies as mechanisms to enforce deployment rules for Supervisor-based Kubernetes clusters.

For the production project, only Kubernetes resources are allowed, so administrators must disallow VM deployments (A).

To tolerate a single control plane node failure, production clusters should use multi-control-plane node templates, ensuring availability (B).

In the development project, resources should be minimized, so a single-control-plane node policy is enforced (D), which reduces overhead.

Incorrect options:

Organization-wide policies (C and F) would apply to both projects, which is not desired since dev and prod have different requirements.

Enforcing single-control-plane nodes in production (E) contradicts the requirement for failure tolerance.

Thus, the correct approach is: Disallow VMs in production, enforce multi-control-plane clusters in production, and enforce single-control-plane clusters in development.

The VCF 9.0 Deployment Guide notes: “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) and commission hosts via the management domain vCenter (B).

The vSAN ESA documentation in VCF 9.0 explains that auto-policy management dynamically selects the most efficient data placement policy based on cluster size. For RAID-6 (erasure coding with double parity), the minimum required host count is 6. The docs state:

“RAID-6 (Erasure Coding with FTT=2) requires a minimum of six hosts in a vSAN ESA cluster. This ensures that data and parity components can be distributed across unique failure domains.”

With fewer than six hosts, RAID-6 cannot be enforced and auto-policy management will fall back to RAID-1 mirroring. RAID-6 in vSAN ESA provides higher storage efficiency but comes with stricter host count requirements. Options 2 and 4 are far below requirements, while 8 provides more redundancy but is not the minimum. Therefore, the correct minimum number of hosts for RAID-6 with ESA is 6.

For dark site (air-gapped) deployments, VMware Cloud Foundation requires the use of the VCF Download Tool to retrieve the required software bundles from a connected system before transferring them into the isolated environment.

The VCF 9.0 Installation Guide specifies:

“For deployments in disconnected or air-gapped environments, use the VCF Download Tool on a connected system to download required bundles and then transfer them to the target environment.”

The VCF Installer (A) consumes bundles but does not download them.

SDDC Manager (B) can download bundles only in connected mode.

Broadcom Downloads (D) is the source portal, but not the supported workflow tool for preparing offline repositories.

Therefore, the correct method for dark site deployments is to use the VCF Download Tool.

Document reference (VCF 9.0):

VMware Cloud Foundation 9.0 → Observability and Monitoring Architecture

VMware Cloud Foundation 9.0 → VCF Operations and VCF Operations for Logs

The VCF 9.0 Installation Guide describes the VCF Download Tool for dark sites:

“For environments without Internet access, use the VCF Download Tool on a connected machine to download required bundles and transfer them to the air-gapped VCF environment.”

Broadcom Downloads (B) is the source but not the workflow for dark sites. The VCF Installer (C) consumes binaries but does not fetch them. SDDC Manager (D) manages bundles in connected mode but cannot download in disconnected environments.

Thus, the correct method for dark sites is A. Use the VCF Download Tool.

VCF 9.0 states for the Simple Automation model: “Single node… Applies to Small… Can be scaled out to the high availability model by resizing the node to Medium or Large, which also forces the scale out to 3 nodes.” In addition, the Day-N procedure confirms the action is a Scale (scale-out) operation: “Scale VCF Automation… choose a larger target deployment type such as Medium or Large…” and provide “Additional VIPs” and a “Cluster Node IP Pool” (Medium requires a minimum of four IPs), then submit the scale out request. Therefore, moving from Small (Simple) to Medium necessarily transitions to the High Availability (3-node) model rather than remaining a single medium node. This aligns the form factor with the documented model behavior and the fleet management workflow.

===========

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.

In VMware Cloud Foundation (VCF) 9.0, the Lifecycle Management (LCM) process follows a strict sequential upgrade path. The SDDC Manager (or the VCF Manager in version 9.0) acts as the central orchestrator for all metadata and bundle management for the entire Software-Defined Data Center (SDDC) stack.

According to the VCF 9.0 Upgrade and Migration Guide:

Sequential Bundle Availability: The SDDC Manager UI is designed to only display bundles that are compatible with its current running version. Because an SDDC Manager at version 5.2 does not possess the metadata or orchestration logic required to manage version 9.0 components (such as vCenter 9.0 or ESXi 9.0), those bundles are hidden from the " Available Bundles " list.

Orchestration Logic: To unlock the remaining components of the VCF 9.0 release, the SDDC Manager must be upgraded first. Once the SDDC Manager reaches version 9.0, it retrieves the new manifest from the VMware/Broadcom Depot. This manifest informs the SDDC Manager of the compatible versions for vCenter Server, NSX, and ESXi that constitute the 9.0 Bill of Materials (BOM).

Upgrade Order: The documented upgrade order for VCF 9.0 is:

Step 1: SDDC Manager

Step 2: vCenter Server (Management Domain)

Step 3: NSX (Management Domain)

Step 4: ESXi (Management Domain)

Step 5: Workload Domains (vCenter, NSX, then ESXi)

Why other options are incorrect:

B & C: While an offline repository or a proxy might affect the ability to download bundles, it would not selectively hide everything except for the SDDC Manager bundle if the repository was properly configured.

D: The Async Patch Tool (ASYNC tool) is used for applying individual patches or " out-of-band " updates that are not yet part of an official VCF release. It is not the standard tool for a major version upgrade from 5.2 to 9.0.

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

In VMware Cloud Foundation 9.0, the Account and Password Management table explicitly lists the NSX Local Manager local appliance accounts whose passwords are managed (updated/remediated) through VCF Operations UI or API. Under NSX Local Manager, the accounts shown as managed are:

audit — “Update or remediate by using the VCF Operations UI or API.”

admin — “Update or remediate by using the VCF Operations UI or API.”

root — “Update or remediate by using the VCF Operations UI or API.”

These three correspond exactly to options A (admin), C (audit), and E (root).

Document reference (VCF 9.0):

VMware Cloud Foundation 9.0 → Account Management Design → Table 674: Account and Password Management in VMware Cloud Foundation (section showing NSX Local Manager accounts: audit, admin, root).

To integrate VCF Automation with an external CMDB (such as ServiceNow) for compliance and tracking of Kubernetes or VM resources, the system utilizes a specific extensibility framework. According to the VCF 9.0 documentation on " Integrating VCF Automation for ITSM with ServiceNow " :

Event Subscriptions (D): These act as the trigger mechanism within the VCF Automation Event Broker Service. When a resource (such as a Kubernetes cluster or deployment) is provisioned, an event is published. An administrator creates a subscription to listen for these specific lifecycle events (e.g., Compute.PostProvision or Kubernetes-specific topics) to initiate the registration process.

VCF Operations orchestrator (B): This is the orchestration engine (formerly known as VMware Aria Automation Orchestrator or vRO). Documentation specifies that for CMDB and ITSM compliance, VCF Automation is integrated with VCF Operations orchestrator workflows. These workflows contain the complex technical logic required to:

Separate objects and feed inputs into technical integration tasks.

Handle API tokens and authentication for the external CMDB.

Execute the REST API calls to the CMDB (e.g., to the cmdb_ci_vmware_instance table).

Update custom properties (like serviceNowSysId) back into the deployment for future decommissioning lifecycle events.

Extract from VCF 9.0 Documentation:

" Enterprise users commonly integrate their Cloud Management Platform with an IT Service Management (ITSM) and Configuration Management Database (CMDB) platform for compliance. Following this example, you can integrate VCF Automation with ServiceNow for CMDB and ITSM using VCF Operations Orchestrator Client... This integration uses Event Subscriptions to trigger VCF Operations Orchestrator workflows. "

VCF 9.0 documents two Operations for Logs/Operations models—Simple (Standard) and High Availability (Cluster)—and highlight that Simple is 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 the smallest resource footprint, the Simple model is the correct selection. (Stretched/Continuous Availability options are not listed VCF Operations models in this context.)

For hosts that will be commissioned for a workload domain using VMFS on Fibre Channel as principal storage, the Fibre Channel storage must already be accessible to every ESX host before commissioning begins. VMware Cloud Foundation 9.0 explicitly states: “The VMFS datastore must be mounted on all the hosts before commissioning.”

VCF also requires supported Fibre Channel HBAs and drivers, and the hosts must be able to access the FC array. Fibre Channel does not require a dedicated Ethernet storage network because FC traffic uses Fibre Channel HBAs and the SAN fabric rather than VMkernel-based IP storage networking.

A network pool must exist before host commissioning, but for VMFS-FC it is used for VCF host networking such as management and vMotion; it is not a dedicated Fibre Channel storage network. Therefore, option D is not the specific storage prerequisite asked here. Pass-through mode is also unrelated to FC principal storage.

Because this project must support a Kubernetes-based application, the applicable VCF Automation model is All Apps, where projects consume resources through vSphere Namespaces, not legacy VM Apps cloud zones. VCF 9.0 states that an Organization Administrator can create and delete projects, whereas the Project Administrator manages an existing project but does not create new projects.

The administrator therefore logs in as the Organization Administrator and creates the new project. The documentation states that when configuring a project, the administrator adds at least one namespace so users can start provisioning resources. Namespaces provide the resource envelope for workloads including VKS clusters.

To minimize ongoing membership administration, VCF explicitly recommends assigning roles using groups. The documentation explains that group-based roles allow users to “come and go from your identity provider rather than requiring the project administrator to constantly update the individual users.” Therefore, Active Directory groups should be assigned rather than individual users.