A large corporation recently experienced a power outage at one of its primary data centers resulting
in service disruption for customers in that region. An administrator is tasked to assess the current
infrastructure and propose a plan to improve resiliency.
Current configuration:
Single-site vSAN Express Storage Architecture (ESA) cluster
12 hosts
Cluster resource utilization (CPU, memory, and storage) is under 30%
Which solution would improve resiliency and minimize service disruption in data center outages with
a recovery point objective (RPO) of zero without requiring additional hosts?
A
Explanation:
The VCF 9.0 Design Guide highlights that for resiliency across sites with RPO = 0, the recommended
approach is a vSAN 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 to relocate hosts and
configure a stretched cluster.
An organization wants to enable Service and Application Discovery across their VMware Cloud
Foundation (VCF) fleet. Which optional VMware Cloud Foundation (VCF) solution must the
administrator enable or deploy to facilitate this capability?
D
Explanation:
The VCF Operations for Networks (formerly vRNI) enables Application Discovery and Network
Visibility. According to VCF 9.0: “Operations for Networks provides flow-based application discovery,
dependency mapping, and security planning. This allows administrators to visualize application
topology and relationships across the VCF fleet.” By contrast, VCF Operations for Logs provides log
aggregation, while the Collector provides integration for metrics, not discovery. The vSphere
Supervisor enables Kubernetes workloads, not application discovery. Therefore, to achieve Service
and Application Discovery, administrators must deploy VCF Operations for Networks.
An administrator is responsible for monitoring VMware vSAN performance across a VMware Cloud
Foundation (VCF) instance. The administrator confirms VCF Operations is configured correctly. When
viewing Storage Operations, the vSAN Cluster Performance widget is not displaying any dat
a. What additional configuration should the administrator complete to ensure the widget displays
data?
D
Explanation:
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.
An administrator is tasked to configure network connectivity to the organization's corporate network
for their container workloads to be deployed on VMware Kubernetes Service (VKS) clusters backed
by VMware NSX networking on a new VMware Cloud Foundation (VCF) deployment. Which gateway
connectivity type should the administrator deploy?
D
Explanation:
The VMware Cloud Foundation 9.0 networking design documentation specifies that container
workloads running on VMware Kubernetes Service (VKS) with NSX networking require external
connectivity via a Centralized Connectivity model. This is implemented using an NSX Tier-0 (T0)
Gateway which provides north-south routing to the corporate physical network.
The guide states: “In VKS deployments backed by NSX networking, workloads achieve external
reachability through a centralized Tier-0 Gateway, ensuring integration with corporate networking
and enterprise services.” This model ensures traffic consolidation, policy enforcement, and simplified
routing for Kubernetes workloads.
Round-robin Connectivity is not a supported NSX gateway connectivity model.
Distributed Connectivity refers to east-west NSX overlay communication, not north-south
connectivity.
Physical Connectivity is not precise, as workloads do not connect directly to the physical network;
instead, they use logical routing.
Centralized Connectivity is the correct model, where the T0 Gateway centralizes external routing for
container workloads.
Reference: VMware Cloud Foundation 9.0 – NSX Networking and VKS Deployment Guide (Tier-0
Gateway connectivity model).
.
What is the purpose of Istio Service Mesh?
B
Explanation:
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.
An administrator is deciding on a storage solution to create the first management workload domain
for a new VMware Cloud Foundation (VCF) instance. Which three storage solutions can be used as
principal storage? (Choose three.)
C, D, E
Explanation:
The VCF 9.0 Architecture Guide outlines valid principal storage options for 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 are not supported for 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.
An administrator is responsible for the management of a VMware Cloud Foundation (VCF)
environment and has been tasked with creating a new Organization in VCF Automation. The
customer previously upgraded from VCF 5.2 and this is the first new Organization since their
upgrade.
The following requirements have been provided for the additional Organization:
Onboard existing Virtual Machines (VM) for management through VCF Automation.
Use third-party integrations, including Tanzu Salt and Active Directory.
Deploy to Native Public Cloud (NPC) endpoints.
What action should the administrator take to complete the objective?
B
Explanation:
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.
Reference: VMware Cloud Foundation 9.0 Automation Guide – Organizations for All Applications
(unified management of VMs, Kubernetes, third-party integrations, and public cloud endpoints).
An administrator is tasked with upgrading a vSphere 8-only environment to VCF 9.0. Which three
components must be deployed as part of the upgrade? (Choose three.)
A, D, F
Explanation:
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.
An administrator is preparing to create a new workload domain within an existing VCF instance.
Which two tasks must be completed before starting the deployment workflow? (Choose two.)
B, D
Explanation:
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).
Which two are use cases for VMware Cloud Foundation (VCF) Automation? (Choose two.)
C, E
Explanation:
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).