Practice Free 2V0-17.25 Exam Online Questions
Question #11
What prerequisite must an administrator complete in VCF before configuring Provider Networking in VCF Automation?
- A . Create a T0 Gateway in the Organization.
- B . Create a T0 Gateway in NSX Manager.
- C . Create a vDS in Provider Management.
- D . Create a vDS in vCenter.
Correct Answer: B
B
Explanation:
The VCF Automation Provider Networking Guide states:
“Before you can configure Provider Networking, an active Tier-0 (T0) Gateway must be created in NSX Manager and associated with the Provider region.”
This gateway provides external routing and forms the foundation for VPC and tenant networking. Creating a T0 at the Organization level (A) is not correct―organizations consume Provider networking but do not create T0s. vDS in Provider Management (C) or vCenter (D) is unrelated to NSX-based provider networking.
Thus, the required prerequisite is: Create a T0 Gateway in NSX Manager.
B
Explanation:
The VCF Automation Provider Networking Guide states:
“Before you can configure Provider Networking, an active Tier-0 (T0) Gateway must be created in NSX Manager and associated with the Provider region.”
This gateway provides external routing and forms the foundation for VPC and tenant networking. Creating a T0 at the Organization level (A) is not correct―organizations consume Provider networking but do not create T0s. vDS in Provider Management (C) or vCenter (D) is unrelated to NSX-based provider networking.
Thus, the required prerequisite is: Create a T0 Gateway in NSX Manager.
Question #12
An administrator creates a custom alert in VCF Operations for a VM with a symptom definition: “Read Latency > 1 ms.” The alert should trigger immediately once the symptom condition occurs.
What additional step is required to ensure the alert functions?
- A . Enable the alert in an Active Policy.
- B . Create a new Payload Template.
- C . Create an instance of the REST Notification Plugin.
- D . Create and enable a super metric for read latency in the Active Policy.
Correct Answer: A
A
Explanation:
Comprehensive and Detailed
The VCF Operations 9.0 Monitoring Guide specifies: “For any alert definition to be active in the environment, it must be associated with and enabled in an Active Policy.” . Creating symptom and alert definitions only defines conditions; they do not generate alerts until policies include them. REST notification plugins or payload templates are used for outbound integrations, not for enabling alerts. A super metric is only needed for custom composite KPIs, not for native read latency which is a standard metric already available. Therefore, the required step is to enable the alert in an Active Policy so that when the symptom triggers (latency > 1 ms), the alert activates.
A
Explanation:
Comprehensive and Detailed
The VCF Operations 9.0 Monitoring Guide specifies: “For any alert definition to be active in the environment, it must be associated with and enabled in an Active Policy.” . Creating symptom and alert definitions only defines conditions; they do not generate alerts until policies include them. REST notification plugins or payload templates are used for outbound integrations, not for enabling alerts. A super metric is only needed for custom composite KPIs, not for native read latency which is a standard metric already available. Therefore, the required step is to enable the alert in an Active Policy so that when the symptom triggers (latency > 1 ms), the alert activates.
Question #13
An administrator must replace a component’s certificate in VCF with an external CA-signed certificate.
What format must be used when creating the certificate?
- A . DER
- B . PFX
- C . P7B
- D . PEM
Correct Answer: D
D
Explanation:
The VCF 9.0 Security and Certificates Guide states: “VCF supports only certificates in PEM format when replacing system component certificates with those signed by an external Certificate Authority.”
PEM is the standard Base64 format with .crt and .key files. PFX (PKCS#12) is used for Windows stores
but not supported in VCF automation. P7B is for certificate chains, while DER is binary encoding.
Thus, the required format for certificates in VCF is PEM.
D
Explanation:
The VCF 9.0 Security and Certificates Guide states: “VCF supports only certificates in PEM format when replacing system component certificates with those signed by an external Certificate Authority.”
PEM is the standard Base64 format with .crt and .key files. PFX (PKCS#12) is used for Windows stores
but not supported in VCF automation. P7B is for certificate chains, while DER is binary encoding.
Thus, the required format for certificates in VCF is PEM.
Question #14
What is the function of Velero?
- A . Publish DNS records for applications to DNS servers.
- B . Monitor cluster services.
- C . Collect data and logs from different sources, unify them, and send them to multiple destinations.
- D . Backup and restore Kubernetes clusters.
Correct Answer: D
D
Explanation:
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.
Reference: VMware Cloud Foundation 9.0 C Kubernetes Services and Data Protection (Velero integration).
D
Explanation:
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.
Reference: VMware Cloud Foundation 9.0 C Kubernetes Services and Data Protection (Velero integration).
Question #15
An administrator is preparing to deploy a new VMware Cloud Foundation (VCF) fleet to an environment that does not have Internet access.
Which two binaries must be uploaded to the VCF Installer appliance before initiating the deployment? (Choose two.)
- A . Identity Broker
- B . ESX
- C . NSX
- D . VCF Operations
- E . Lifecycle Manager
Correct Answer: C, D
C, D
Explanation:
In VCF 9.x, air-gapped bring-up requires staging the required binaries in the VCF Installer. The documented list explicitly includes NSX and VCF Operations among the components to upload. The product guide states: “VMware Cloud Foundation required binaries include… NSX … VMware Cloud Foundation Operations … vCenter … SDDC Manager…” (exact list excerpt). This list does not call for ESX images or the legacy “Lifecycle Manager.”
Therefore, from the given options the two binaries that must be uploaded are NSX and VCF Operations. ESX is pre-imaged on hosts per preparation guidance and is not a required VCF Installer binary; “Lifecycle Manager” is not used in VCF 9.0 bring-up.
C, D
Explanation:
In VCF 9.x, air-gapped bring-up requires staging the required binaries in the VCF Installer. The documented list explicitly includes NSX and VCF Operations among the components to upload. The product guide states: “VMware Cloud Foundation required binaries include… NSX … VMware Cloud Foundation Operations … vCenter … SDDC Manager…” (exact list excerpt). This list does not call for ESX images or the legacy “Lifecycle Manager.”
Therefore, from the given options the two binaries that must be uploaded are NSX and VCF Operations. ESX is pre-imaged on hosts per preparation guidance and is not a required VCF Installer binary; “Lifecycle Manager” is not used in VCF 9.0 bring-up.
Question #16
Which two resources can be configured in a VM Class in VMware vSphere with vSphere Supervisor? (Choose two.)
- A . CPU
- B . Memory
- C . Network interface
- D . PCI devices
- E . Storage
Correct Answer: A, B
A, B
Explanation:
A VM Class predefines hardware for Supervisor-managed VMs: “The VM class… defines such parameters as the number of virtual CPUs, memory capacity, and reservation settings.” Administration steps show these are configurable: “You can configure hardware resources such as CPU, memory, and different devices” when editing a VM class.
Additionally, the DCLI/API specification underscores CPU and Memory fields: “–cpu-count … Required.” and “–memory-mb … Required.” for a VM class.
While network adapters, PCI devices, and instance storage can also be added via advanced config,
the question asks for two; CPU and Memory are canonical, always-present VM Class resources per
the core definition above.
A, B
Explanation:
A VM Class predefines hardware for Supervisor-managed VMs: “The VM class… defines such parameters as the number of virtual CPUs, memory capacity, and reservation settings.” Administration steps show these are configurable: “You can configure hardware resources such as CPU, memory, and different devices” when editing a VM class.
Additionally, the DCLI/API specification underscores CPU and Memory fields: “–cpu-count … Required.” and “–memory-mb … Required.” for a VM class.
While network adapters, PCI devices, and instance storage can also be added via advanced config,
the question asks for two; CPU and Memory are canonical, always-present VM Class resources per
the core definition above.
Question #17
An administrator is tasked to upgrade a VMware Cloud Foundation (VCF) environment from 5.2 to 9.0. During preparation, the administrator sees only the SDDC Manager 9.0 bundle available.
Why are no other bundles available?
- A . An offline repository was used for upgrade bundles.
- B . A proxy server was used to download bundles.
- C . The ASYNC tool must be used to download all required bundles.
- D . SDDC Manager must be upgraded first.
Correct Answer: D
D
Explanation:
The VCF 9.0 Upgrade Documentation clearly 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 is
D. SDDC Manager must be upgraded first.
D
Explanation:
The VCF 9.0 Upgrade Documentation clearly 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 is
D. SDDC Manager must be upgraded first.
Question #18
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.)
- A . Commission the new ESX hosts into the existing VCF instance from the new workload domain vCenter.
- B . Commission the new ESX hosts into the existing VCF instance from the management domain vCenter.
- C . Pre-install a supported ESX version onto the server with VCF Installer.
- D . Pre-install a supported ESX version onto the server using a valid ISO image.
- E . Commission the new ESX hosts into the existing VCF instance from VCF Installer.
Correct Answer: B, D
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
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
Question #19
An administrator is tasked to converge an existing VMware vSphere environment to VMware Cloud Foundation (VCF). The following information has been provided to the administrator for this task: Three VMware vCenters in Enhanced Linked Mode. Five vSphere clusters per vCenter.
Lifecycle Manager configured with baselines and images.
Each VMware ESX host has 10 Gbps uplinks.
All ESX hosts are configured with LACP.
All clusters within a vCenter share a single vSphere Distributed Switch.
Which two configurations need to be changed before the environment is converged? (Choose two.)
- A . All ESX hosts must have a minimum of 25 Gbps uplinks.
- B . Enhanced Linked Mode needs to be deactivated.
- C . Add an additional VMkernel interface per host for vMotion traffic.
- D . Create a vSphere Standard Switch per host.
- E . Lifecycle Manager needs to be configured with Images only.
Correct Answer: B, E
B, E
Explanation:
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).
Reference: VMware Cloud Foundation 9.0 Convergence and Migration Guide C Unsupported Configurations (ELM), Lifecycle Manager Requirements (Images only).
B, E
Explanation:
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).
Reference: VMware Cloud Foundation 9.0 Convergence and Migration Guide C Unsupported Configurations (ELM), Lifecycle Manager Requirements (Images only).
1 2