5V0-31.22 VMware Cloud Foundation Specialist (v2) Exam
VMware Cloud Foundation Specialist (v2)
The VMware Cloud Foundation Specialist (v2) exam validates a candidate’s knowledge of how to plan for, and execute, the VCF bring up process and demonstrates knowledge of how to use and configure VMware Cloud Foundation.
Product: VMware Cloud Foundation
Associated Certification: VMware Certified Specialist – Cloud Foundation 2023
Exam 5V0-31.22 : VMware Cloud Foundation Specialist (v2)
Language English
Number of Questions 70
Format Single and Multiple Choice, Proctored
Duration 110 Minutes
Passing Score 300
Examkingdom VMware 5V0-31.22 Exam pdf,
Best VMware 5V0-31.22 Free downloads , VMware 5V0-31.22 Dumps at Certkingdom.com
Passing Score –
VMware exams are scaled on a range from 100-500, with the determined raw cut score scaled to a value of 300. Your exam may contain unscored questions in addition to the scored questions, this is a standard testing practice. You will not know which questions are unscored, your exam results will reflect your performance on the scored questions only.
Minimally Qualified Candidate
The Minimally Qualified Candidate (MQC) has 6-12 months hands-on experience installing, configuring, and managing VMware Cloud Foundation. The MQC also has experience in deployment and administration of guest operating systems on
a VMware Cloud Foundation infrastructure. The Minimally Qualified candidate shows intermediate knowledge in: networking including core switching and routing concepts, hardware, monitoring and troubleshooting, and security
concept knowledge including certificates. The MQC also possesses basic business continuity and disaster discovery knowledge, basic understanding of workload platform capabilities including use cases and Kubernetes constructs and
basic knowledge of vRealize Suite. Candidates should have completed all recommended training courses for this credential and hold a VCP-DCV 2020,2021 or 2022. The successful candidate will likely hold additional industry-recognized IT
certifications or accreditations. The MQC should have all the knowledge contained in the exam sections listed below.
Exam Sections
VMware exam blueprint sections are now standardized to the seven sections below, some of which may NOT be included in the final exam blueprint depending on the exam objectives.
Section 1 – Architecture and Technologies
Section 2 – Products and Solutions
Section 3 – Planning and Designing
Section 4 – Installing, Configuring, and Setup
Section 5 – Performance-tuning, Optimization, and Upgrades
Section 6 – Troubleshooting and Repairing
Section 7 – Administrative and Operational Tasks
If a section does not have testable objectives in this version of the exam, it will be noted below, accordingly. The objective numbering may be referenced in your score report at the end of your testing event for further preparation should a retake of the exam be necessary.
Sections Included in this Exam
Section 1 –Architectures and Technologies
Objective 1.1: Identify NSX Federation components and architecture
Objective 1.2: Identify use cases for multiple clusters in a workload domain.
Objective 1.3: Identify the characteristics of Spherelet.
Section 2 – VMware Products and Solutions
Objective 2.1: Identify the use case of NSX Federation in VMware Cloud Foundation.
Objective 2.2: Identify the functions of supervisor cluster control plane.
Section 3 – Planning and Designing
Objective 3.1: Given a scenario, identify the requirements for deploying VMware Cloud Foundation. Objective 3.2: Given a scenario, identify the considerations for management domain sizing.
Objective 3.3: Given a scenario, identify the considerations for workload domain sizing.
Objective 3.4: Given a scenario, identify the design considerations for ESXi in management and VI workload domains.
Objective 3.5: Given a scenario, identify the design considerations for vCenter in management and VI workload domains.
Objective 3.6: Identify the components or steps during the VMware Cloud Foundation bring-up process.
Objective 3.7: Identify information required for the Planning and Preparation Workbook.
Objective 3.8: Identify information required for the Deployment Parameter Workbook.
Objective 3.9: Identify the components of the NSX Management, Control, or Data planes.
Objective 3.10: Given a scenario, identify design considerations for workload domains with shared NSX Manager instances.
Objective 3.11: Given a scenario, identify design considerations for workload domains with dedicated NSX Manager instances.
Objective 3.12: Identify NSX Edge cluster requirements for vSphere with Tanzu.
Objective 3.13: Identify the steps for data plane preparation for NSX-T Data Center Edge nodes in a workload domain.
Objective 3.14: Given a scenario, identify design considerations for vSphere networking in management and VI workload domains.
Objective 3.15: Given a scenario, identify design considerations for storage in management and VI workload domains.
Objective 3.16: Given a scenario, identify the difference between design choices for a consolidated design or standard design.
Objective 3.17: Identify workload domain prerequisites.
Objective 3.18: Identify the prerequisites for vSphere with Tanzu cluster compatibility. Objective 3.19: Identify the role of external service availability.
Objective 3.20: Given a scenario, identify the requirements for the stretched cluster use case. Objective 3.21: Identify stretched cluster components.
Section 4 – Installing, Configuring, and Setup
Objective 4.1: Identify what is validated in the configuration validation process performed by VMware Cloud Builder.
Objective 4.2: Given a scenario, identify how to image a host.
Objective 4.3: Given a scenario, identify how to configure user access to VMware Cloud Foundation.
Objective 4.4: Given a scenario, identify NSX Edge cluster deployment considerations.
Objective 4.5: Identify the functions of vSphere with Tanzu namespaces.
Objective 4.6: Identify the functions of NSX-T networking components.
Objective 4.7: Given a scenario, identify the control plane VM management networking requirements.
Objective 4.8: Given a scenario, identify the appropriate IP address CIDR ranges for pod, ingress, and egress networking.
Objective 4.9: Given a scenario, identify the steps to deploy vSphere with Kubernetes.
Objective 4.10: Given a scenario, identify the storage options for VMware Cloud Foundation.
Objective 4.11: Identify the available CA options in SDDC Manager.
Section 5 – Performance-tuning, Optimization, Upgrades
Objective 5.1: Given a scenario, identify NSX Edge cluster placement considerations.
Objective 5.2: Given a scenario, identify the connectivity options for supplemental storage.
Objective 5.3: Identify the characteristics of scaling vSAN clusters in VMware Cloud Foundation.
Objective 5.4: Given a scenario, identify suitable storage policies for a workload domain cluster.
Objective 5.5: Identify the components that can be supported and upgraded using SDDC manager / vRSLCM.
Objective 5.6: Given a scenario, identify available options for online and offline bundle download using SDDC manager / vRSLCM.
Objective 5.7: Identify the function of vSphere Lifecycle Management in VMware Cloud Foundation.
Objective 5.8: Identify the characteristics of vSphere Lifecycle Manager Baseline-based and Image-based Clusters.
Objective 5.9: Identify the order of upgrade for VMware Cloud Foundation components.
Section 6 – Troubleshooting and Repairing
Objective 6.1: Identify steps in the SDDC Manager backup and restore process.
Objective 6.2: Given a scenario, identify the requirements to perform a full recovery for a VCF deployment.
Objective 6.3: Given a scenario, identify how to upgrade VMware Cloud Foundation software and components.
Objective 6.4: Identify the steps to perform checks and create log bundles with the SoS tool.
Section 7 – Administrative and Operational Tasks
Objective 7.1: Given a scenario, identify how to manage passwords in VMware Cloud Foundation including supported components and options.
Objective 7.2: Given a VMware component, identify which, when, or how to assign license keys.
Objective 7.3: Given a VMware component, identify how to replace a expiring license.
Objective 7.4: Identify the steps to create a workload domain.
Objective 7.5: Identify the steps to scale a workload domain.
Objective 7.6: Identify the steps to delete a workload domain.
Objective 7.7: Identify the steps to decommission hosts.
Objective 7.8: Identify the steps to create a vSphere namespace.
Objective 7.9: Identify the steps to configure limits and permissions for a vSphere namespace.
Objective 7.10: Identify the steps to enable Harbor Image Registry.
Objective 7.11: Identify the characteristics of mapping between storage policies and Kubernetes storage classes.
Objective 7.12: Identify the characteristics of persistent volumes.
Objective 7.13: Identify the steps to replace and install certificates for VMware Cloud Foundation components.
Objective 7.14: Identify the function of VMware Cloud Foundation services.
Recommended Courses
VMware Cloud Foundation Plan and Deploy
VMware Cloud Foundation Management and Operations[V4.3]
VMware Cloud Foundation: Planning, Management, Operations [V4.3]
References
In addition to the recommended courses, item writers used the following references for information when writing exam
questions. It is recommended that you study the reference content as you prepare to take the exam, in addition to the recommended training.
QUESTION 1
An administrator needs additional capacity on a vSAN cluster. Each host currently has only one disk group. Which two approaches can be used to expand storage capacity in this situation? (Choose two.)
A. Increase the number of cache disks in the existing disk group.
B. Add an additional disk group.
C. Disable compression.
D. Increase the number of capacity disks in the existing disk group
E. Disable deduplication.
Answer: BD
To expand storage capacity in a vSAN cluster with one disk group, you can either add more drives to
hosts in the cluster, which is commonly referred to as scaling up, or add capacity drives to existing disk groups
Option B: Add an additional disk group – According to search result [1], adding additional drives to a
host will increase both capacity and performance [1], and each disk group contains one flash cache
device and one or multiple capacity devices for persistent storage [2]. Therefore, adding an
additional disk group to each host would increase the storage capacity of the vSAN cluster.
Option D: Increase the number of capacity disks in the existing disk group – Search result [1] explains
that vSAN clusters require capacity and cache devices to function, and each disk group can contain
multiple capacity devices for persistent storage [2]. Thus, an additional way to expand storage
capacity in the vSAN cluster would be to increase the number of capacity disks in the existing disk group.
Reference: 1: VMware vSAN documentation 2: VMware vSAN documentation
A disk group is a collection of one or more flash-based cache devices and one or more capacity
devices that provide storage capacity for a vSAN cluster. A vSAN cluster can have multiple disk
groups, and each disk group can have a different configuration.
To expand storage capacity in a vSAN cluster where each host currently has only one disk group, the
administrator can add an additional disk group or increase the number of capacity disks in the existing disk group.
Adding an additional disk group involves adding more disks to the host and creating a new disk
group. This approach can provide additional capacity and performance benefits, as the new disk
group can be configured with different settings to optimize performance and capacity.
Increasing the number of capacity disks in the existing disk group involves adding more capacity
devices to the existing disk group. This approach can provide additional capacity, but may not
necessarily provide performance benefits as the existing disk group may already be fully utilized.
QUESTION 2
A VCF architect collected the following requirements when designing the expansion of a new VI
Workload Domain with twenty four vSAN Ready nodes, each with a dual-port 25Gbps network interface card:
Provide scalable high-performance networking with layer-3 termination at top-of-rack
Protect workloads from switch/NIC/rack failure
Provide isolation for DMZ workloads
Provide at-least 25Gbps dedicated bandwidth to backup traffic
Easily accept workloads on traditional VLAN-backed networks
Fully-supported by VMware
Which three design considerations meet all of these requirements? (Choose three.)
A. Two-node Edge Cluster with ECMP
B. Spine and Leaf network topology with layer-3 at Spine
C. Stretched Clustering
D. Spine and Leaf network topology with layer-3 at top of rack
E. Two-node Edge Cluster with BFD
F. Core Aggregation network topology
Answer: BDF
Option B: Spine and Leaf network topology with layer-3 at Spine – A spine and leaf network topology
is designed for high scalability and performance, and layer-3 at the spine ensures that there is no
single point of failure for the layer-3 termination. This meets several of the requirements, including
scalable high-performance networking with layer-3 termination at top-of-rack, protecting workloads
from switch/NIC/rack failure, and providing isolation for DMZ workloads.
Option D: Spine and Leaf network topology with layer-3 at top of rack – Similar to Option B, this
topology also provides high scalability and performance, and layer-3 at the top of rack meets the
requirement for layer-3 termination at top-of-rack.
Option F: Core Aggregation network topology – This topology provides a highly available, redundant
core switch for aggregation and routing, which meets the requirement for protecting workloads from
switch/NIC/rack failure.
Based on the given choices, the correct answers would be B, D, and F.
Sources: [1] Designing VMware Infrastructure Topology and Architecture; Authors: Russel Nolan, Eiad
Al-Aqqad [2] Network Topology Considerations for VMware vSAN;
QUESTION 3
An administrator has registered an external identity source in a consolidated architecture and would
like to make sure that any subsequent workload domains can be accessed using the same identity sources.
How can this goal be achieved with VMware Cloud Foundation?
