2026年最新の実際のPassTest 5V0-22.23問題集PDFで100%合格率を保証します
無料VMware 5V0-22.23試験問題と解答
質問 # 16
The vSphere Client reports that the state of some components stored on the vSAN datastore are in the reconfiguring state.
Which situation causes components to enter this state?
- A. The cluster is recovering from a vSAN failure.
- B. Additional storage capacity is added to the cluster.
- C. The applied storage policy is modified.
- D. A host in the cluster enters maintenance mode.
正解：C
解説：
Explanation
The reconfiguring state indicates that some components stored on the vSAN datastore are being moved or resized to meet a new storage policy requirement. This state can occur when the applied storage policy is modified, such as changing the number of failures to tolerate, stripe width, or object space reservation. The other situations will not cause components to enter this state. References: [VMware vSAN Specialist v2 EXAM 5V0-22.23], page 31
質問 # 17
An administrator is troubleshooting a vSAN performance issue. In the vSAN performance monitor there is a high latency on the vSAN cluster.
What is a possible cause of this?
- A. The Virtual Machines are using PVSCSI controllers.
- B. Jumbo frames are not enabled on the VMkernel adapters.
- C. There is congestion in one or more disk groups.
- D. Erasure Coding is disabled in the storage policy.
正解：C
解説：
Explanation
A possible cause of high latency on the vSAN cluster is that there is congestion in one or more disk groups.
Congestion is a measure of how busy the storage devices are in handling I/O requests. When congestion is high, it means that the storage devices are overloaded and cannot process the requests fast enough, resulting in increased latency and reduced throughput. Congestion can be caused by various factors, such as insufficient cache capacity, disk failures, network issues, or heavy workload. The other options are not likely to cause high latency on the vSAN cluster. The Virtual Machines can use PVSCSI controllers without affecting latency, as they are optimized for high performance. Erasure Coding is a space efficiency feature that does not impact latency significantly. Jumbo frames are not required for vSAN, and enabling them does not guarantee lower latency. References: vSAN Performance Monitor; [vSAN Congestion Explained]
質問 # 18
An administrator is performing maintenance on the hosts in a four-node vSAN cluster and has selected the
"Ensure Accessibility" maintenance mode option. All VMs are running with the Default Storage Policy which has not been modified from the default settings.
While one of the hosts in the cluster is down for firmware upgrade, a second host suddenly loses network connectivity to the remaining hosts.
How will the cluster be affected?
- A. VMs might experience data loss
- B. The backend performance metrics will be lost
- C. Cluster will still be fully operational
- D. All VMs in the cluster will be inaccessible
正解：A
解説：
Explanation
If two hosts in a four-node vSAN cluster are down, the cluster might experience data loss because the default storage policy has a Primary level of failures to tolerate (PFTT) of 1, which means that vSAN can tolerate only one host failure. The Ensure accessibility maintenance mode option does not guarantee full data redundancy, but only ensures that all accessible VMs remain accessible. If another host fails while one host is in maintenance mode, some VMs might lose access to their data components and become unavailable or corrupted. References: vSAN Maintenance Mode Options; vSAN Cluster Configuration Limits
質問 # 19
A vSAN administrator of a non-internet connected vSAN environment wants to upgrade the environment from the vSAN 7.0 U3 to the vSAN 8.0 using vLCM.
Which option, if any, should be used as a depot in this case?
- A. Configure the vSphere Lifecycle Manager to download the updates from an Online Depot.
- B. It is not possible to use the vSphere Lifecycle Manager on a non-internet connected environment.
- C. Configure the vSphere Lifecycle Manager to download the updates from the VMware Depot using HTTPS.
- D. Configure the vSphere Lifecycle Manager to download updates from a local UMDS-shared repository.
正解：D
解説：
Explanation
To upgrade the vSAN environment from vSAN 7.0 U3 to vSAN 8.0 using vLCM in a non-internet connected environment, the administrator should configure the vSphere Lifecycle Manager to download updates from a local UMDS-shared repository. UMDS stands for Update Manager Download Service, which is a component of vSphere Lifecycle Manager that can be used to download patches and updates for ESXi hosts, virtual appliances, and VMware Tools from the VMware online depot and store them in a shared repository. The administrator can then configure the vSphere Lifecycle Manager to use the UMDS-shared repository as a custom depot for patching and upgrading the vSAN cluster. This option allows the administrator to perform offline upgrades without requiring internet access for the vSAN cluster12 References: 1: VMware vSphere Lifecycle Manager Administration, page 22 2: VMware vSphere Update Manager Download Service, page 5
質問 # 20
A customer wishes to host a new range of applications with high-performance needs, specifically, low latency.
The applications are required to be hosted at company-owned edge locations, each with minimal rack space (three host slots per edge location for this project).
Which deployment options would satisfy the customer's needs, while maximizing the amount of capacity available per deployment?
- A. A new three-node vSAN 8.0 All-Flash Cluster with ESA in each edge location Each application VM configured with a RAID-1 VM storage policy
- B. A new three-node vSAN 8.0 All-Flash Cluster with OSA in each edge location Each application VM configured with a RAID-1 VM storage policy
- C. A new three-node vSAN 8.0 All-Flash Cluster with ESA in each edge location Each application VM configured with a RAID-5 VM storage policy
- D. A new three-node vSAN 8.0 All-Flash Cluster with OSA in each edge location Each application VM configured with a RAID-5 VM storage policy
正解：B
解説：
Explanation
To satisfy the customer's needs for high-performance, low-latency applications at edge locations, the best deployment option is to use a new three-node vSAN 8.0 All-Flash Cluster with OSA in each edge location and configure each application VM with a RAID-1 VM storage policy. This option will provide the following benefits:
All-flash clusters offer the highest performance and lowest latency for vSAN, as they use flash devices for both cache and capacity tiers. Flash devices have faster read and write operations than magnetic disks, and they also support advanced features such as deduplication, compression, and encryption.
OSA stands for One Socket Architecture, which means that each host has only one CPU socket with multiple cores. This reduces the licensing cost and complexity of vSphere and vSAN, as well as the power consumption and cooling requirements of the hosts. OSA also improves the performance of vSAN by eliminating the NUMA effect, which is the latency caused by accessing memory or devices across different CPU sockets.
RAID-1 is a mirroring technique that creates two copies of each data component and places them on different hosts. This provides high availability and fault tolerance for the application VMs, as they can survive the failure of one host or disk. RAID-1 also offers better performance than RAID-5 or RAID-6, as it does not incur any parity overhead or additional write operations.
The other options are not optimal for the customer's needs, as they either sacrifice performance or capacity.
Option A uses RAID-5, which is an erasure coding technique that splits each data component into three data segments and one parity segment, and distributes them across four hosts. This reduces the capacity consumption by 25%, but it also increases the write latency and network traffic, as each write operation requires four hosts to participate. Option C uses ESA, which stands for Enterprise Storage Architecture, which means that each host has two CPU sockets with multiple cores. This increases the licensing cost and complexity of vSphere and vSAN, as well as the power consumption and cooling requirements of the hosts.
ESA also introduces the NUMA effect, which can degrade the performance of vSAN by adding latency to access memory or devices across different CPU sockets. Option D uses RAID-5 with ESA, which combines the disadvantages of both options A and C.
質問 # 21
An all-flash vSAN ESA cluster contains four nodes.
Which two storage policies can the cluster satisfy? (Choose two.)
- A. FTT=I (RAID-1 Mirroring)
- B. FTT=2 (RAID-6 Erasure Coding)
- C. FTT=3 (RAID-1 Mirroring)
- D. FTT=2 (RAID-1 Mirroring)
- E. FTT=I (RAID-5 Erasure Coding)
正解：B、D
解説：
Explanation
An all-flash vSAN ESA cluster with four nodes can satisfy the storage policies that require FTT=2 (RAID-1 Mirroring) or FTT=2 (RAID-6 Erasure Coding). These policies mean that the cluster can tolerate two host failures while maintaining data availability and redundancy. RAID-1 Mirroring creates three replicas of each object across different hosts, while RAID-6 Erasure Coding splits each object into four data segments and two parity segments across different hosts. Both policies require at least four hosts in the cluster to meet the FTT=2 requirement. The other options are not correct. An all-flash vSAN ESA cluster with four nodes cannot satisfy the storage policies that require FTT=3 (RAID-1 Mirroring) or FTT=1 (RAID-5 Erasure Coding). These policies mean that the cluster can tolerate three or one host failure respectively, but they require more or less hosts than four to do so. RAID-1 Mirroring with FTT=3 requires at least six hosts in the cluster to create four replicas of each object, while RAID-5 Erasure Coding with FTT=1 requires at least three hosts in the cluster to split each object into two data segments and one parity segment. References: vSAN Express Storage Architecture; RAID Configurations, FTT, and Host Requirements
質問 # 22
A vSAN administrator needs to build a vSAN ESA cluster with RAID-5/FTT 1 adaptive storage policy.
What is the absolute minimum number of hosts that need to be part of that vSAN ESA cluster?
- A. 6 hosts
- B. 3 hosts
- C. 5 hosts
- D. 4 hosts
正解：B
解説：
Explanation
To build a vSAN ESA cluster with RAID-5/FTT 1 adaptive storage policy, the absolute minimum number of hosts that need to be part of that vSAN ESA cluster is 3. This is because the vSAN ESA supports a new RAID-5 erasure coding scheme in a 2+1 configuration, which writes the data in a VM as a stripe consisting of
2 data bits and 1 parity bit, across a minimum of 3 hosts. This scheme can tolerate a single host failure (FTT=1) while consuming 1.5x the capacity of the primary data. This scheme is suitable for smaller vSAN clusters that want to reduce capacity usage without compromising performance12 References: 1: VMware vSAN Specialist v2 ExamPreparation Guide, page 15 2: Adaptive RAID-5 Erasure Coding with the Express Storage Architecture in vSAN 8 3
質問 # 23
An administrator is deploying a new two-node vSAN cluster with a shared witness to a remote location.
Which requirement must be met?
- A. The ESXi hosts must have a minimum of 64 GBs of memory.
- B. The ESXi host's controller cache and advanced features must be disabled.
- C. The ESXi host's drives must be configured in RAID 1 to support Failures to Tolerate of 1.
- D. The ESXi hosts must have SSDs or NVMe configured for Virtual Flash File System.
正解：A
解説：
Explanation
To deploy a new two-node vSAN cluster with a shared witness, the administrator must meet several requirements, one of which is that the ESXi hosts must have a minimum of 64 GBs of memory. This is because each host must have enough memory to run the VMs and also to support the vSAN metadata overhead. The other options are not requirements for a two-node vSAN cluster with a shared witness. The ESXi hosts do not need SSDs or NVMe for Virtual Flash File System, as they can use any supported storage devices for vSAN. The ESXi host's controller cache and advanced features do not need to be disabled, as they can be used to improve performance and reliability. The ESXi host's drives do not need to be configured in RAID 1, as vSAN uses its own software-defined RAID mechanism to provide Failures to Tolerate.
References: Shared Witness for 2-Node vSAN Deployments; Two-Node Cluster Requirements
質問 # 24
After a planned power outage, an administrator decided to restart the vSAN cluster manually.
What is the correct sequence of steps for the administrator to follow after powering on the ESXi hosts?
- A. 1. Enable cluster member updates from vCenter Server only on one ESXi host.
2. Run the python reboot helper script only on one ESXi host to recover the cluster.
3. Exit all hosts from maintenance mode. - B. 1. Exit all hosts from maintenance mode.
2. Run the python reboot helper script only on one ESXi host to recover the cluster.
3. Enable cluster member updates from vCenter Server on all ESXi hosts. - C. 1. Exit all hosts from maintenance mode.
2. Enable cluster member updates from vCenter Server only on one ESXi host.
3. Run the python reboot helper script only on one ESXi host to recover the cluster. - D. 1. Enable cluster member updates from vCenter Server on all ESXi hosts.
2. Run the python reboot helper script on all ESXi hosts to recover the cluster.
3. Exit all hosts from maintenance mode.
正解：A
解説：
Explanation
This is the sequence of steps recommended by VMware for manually restarting the vSAN cluster after a planned power outage. The steps are as follows:
Enable cluster member updates from vCenter Server only on one ESXi host. This will allow the host to receive the latest cluster membership information from vCenter Server and avoid any conflicts or inconsistencies with other hosts. The command to enable cluster member updates is esxcfg-advcfg -s 1
/VSAN/IgnoreClusterMemberListUpdates.
Run the python reboot helper script only on one ESXi host to recover the cluster. This will prepare the cluster for a manual restart by partitioning the cluster and ensuring that all hosts have consistent metadata. The command to run the python reboot helper script is python
/usr/lib/vmware/vsan/bin/reboot_helper.py prepare.
Exit all hosts from maintenance mode. This will allow the hosts to resume normal operations and join the vSAN cluster. The command to exit maintenance mode is esxcli system maintenanceMode set -e false.
The other options are incorrect for the following reasons:
B, exit all hosts from maintenance mode, run the python reboot helper script only on one ESXi host to recover the cluster, and enable cluster member updates from vCenter Server on all ESXi hosts, is incorrect because exiting all hosts from maintenance mode before running the python reboot helper script can cause data inconsistency or corruption, as the hosts may not have the latest metadata or cluster membership information. Enabling cluster member updates from vCenter Server on all ESXi hosts is also unnecessary and can cause conflicts or inconsistencies with other hosts.
C, exit all hosts from maintenance mode, enable cluster member updates from vCenter Server only on one ESXi host, and run the python reboot helper script only on one ESXi host to recover the cluster, is incorrect because exiting all hosts from maintenance mode before running the python reboot helper script can cause data inconsistency or corruption, as the hosts may not have the latest metadata or cluster membership information.
D, enable cluster member updates from vCenter Server on all ESXi hosts, run the python reboot helper script on all ESXi hosts to recover the cluster, and exit all hosts from maintenance mode, is incorrect because enabling cluster member updates from vCenter Server on all ESXi hosts is unnecessary and can causeconflicts or inconsistencies with other hosts. Running the python reboot helper script on all ESXi hosts concurrently can also cause a race condition that can result in unexpected outcomes.
References:
Manually Shut Down and Restart the vSAN Cluster
Restart the vSAN Cluster
質問 # 25
What is the minimum required number of hosts to provide data redundancy for a vSAN stretched cluster using dual-site mirroring and local protection with 1 failure - RAID-1 (Mirroring)?
- A. 6 hosts
- B. 3 hosts
- C. 4 hosts
- D. 3 hosts
正解：A
解説：
Explanation
The minimum required number of hosts to provide data redundancy for a vSAN stretched cluster using dual-site mirroring and local protection with 1 failure - RAID-1 (Mirroring) is six hosts. This is because a vSAN stretched cluster requires at least three hosts per site, and each site must have enough hosts to tolerate one host failure. Therefore, the minimum configuration is three hosts per site, plus one witness host at a third site, for a total of six hosts. References: [VMware vSAN Specialist v2 EXAM 5V0-22.23], page 14
質問 # 26
An administrator wants to assign a storage policy to a workload on a two-node vSAN OSA cluster consisting of three disk groups each with nested fault domains. The virtual machine must be protected against a disk or disk group failure.
Which two storage policies meet these requirements? (Choose two.)
- A. RAID-5/FTT 1
- B. RAID-1/FTT 1
- C. RAID-1/FTT 3
- D. RAID-5/FTT 2
- E. RAID-6/FTT 2
正解：B、E
解説：
Explanation
To protect a virtual machine against a disk or disk group failure, the storage policy must have a failure tolerance method (FTM) of RAID-1 or RAID-6 and a failure to tolerate (FTT) value of at least 1. RAID-1 mirrors the data across multiple disk groups, while RAID-6 uses erasure coding to stripe the data and parity information across multiple disk groups. RAID-5 is not suitable for this scenario, as it can only tolerate one disk failure per stripe. FTT 2 or 3 would require more disk groups than available in the cluster.
Therefore, the correct options are C and E. References: 1, page 8; 2, section 3.1
質問 # 27
A vSAN administrator has a vSAN cluster that is using vSphere Lifecycle Manager (vLCM) to manage hypervisor, server drivers, and firmware. All hosts in the cluster are compliant according to the vLCM image.
A 10GB NIC on the servers is experiencing issues, and the vSAN administrator determines a new network driver will resolve the problem. Unfortunately, the required NIC driver is a newer version compared to the driver provided by the most recent Vendor Add-on.
Which action should the vSAN administrator take to ensure the latest network driver is installed on the NIC before remediation?
- A. Modify the vLCM image to omit the NIC Driver, and then manually update the servers with the required NIC driver
- B. Remove theVendor Add-on from the vLCM image, and then manually install the network driver on the servers
- C. Add an individual component to the vLCM image that has the updated NIC driver
- D. Make sure the vLCM image is configured to use the most recent version of the Vendor Add-on
正解：C
解説：
Explanation
To ensure the latest network driver is installed on the NIC before remediation, the vSAN administrator should add an individual component to the vLCM image that has the updated NIC driver. This action allows the administrator to override the driver provided by the vendor add-on and use a newer version that is compatible with the ESXi version and the hardware device. The administrator can add an individual component to the vLCM image by importing it from a ZIP file or selecting it from the vLCM depot. The other options are not correct. Making sure the vLCM image is configured to use the most recent version of the vendor add-on will not help, as the required NIC driver is a newer version than the one provided by the vendor add-on. Removing the vendor add-on from the vLCM image or modifying the vLCM image to omit the NIC driver will not ensure the latest network driver is installed on the NIC, as these actions will leave the NIC without any driver update. Manually installing or updating the network driver on the servers is not recommended, as it might cause inconsistency and non-compliance in the vLCM image. References: vSphere Lifecycle Manager Image Components; [Add an Individual Component to an Image]
質問 # 28
A vSAN administrator was presented with 30 additional vSAN ReadyNodes to add to an existing vSAN cluster. There is only one administrator to complete this task.
What is the fastest approach?
- A. Launch Quickstart to Add Hosts to a vSAN Cluster
- B. Clone the ESXi boot partition to all new hosts, since the hardware is identical
- C. Run vim-cmd to capture, and apply the configuration from an existing host
- D. Use a Host Profile that was extracted from an existing host
正解：D
解説：
Explanation
To add 30 additional vSAN ReadyNodes to an existing vSAN cluster with the fastest approach, the vSAN administrator should use a Host Profile that was extracted from an existing host. AHost Profile is a configuration template that captures the settings of a reference host and applies them to other hosts or clusters.
This way, the administrator can quickly and consistently configure multiple hosts with the same settings, such as network, storage, security, and services. The other options are not correct. Running vim-cmd to capture and apply the configuration from an existing host is not as fast or convenient as using a Host Profile, as it requires running commands on each host individually. Launching Quickstart to Add Hosts to a vSAN Cluster is not possible, as Quickstart is only available for new clusters or clusters that were configured through Quickstart.
Cloning the ESXi boot partition to all new hosts is not recommended, as it might cause conflicts or errors with the host identity, network settings, or licenses. References: Configuring Hosts Using Host Profile; Using Quickstart to Configure and Expand a vSAN Cluster
質問 # 29
How often does the Skyline Health interval validate online if there are new Health Checks available for vSAN?
- A. Every 4 hours
- B. Every 24 hours
- C. Every 12 hours
- D. Every 1 hour
正解：B
解説：
Explanation
The Skyline Health interval validates online if there are new Health Checks available for vSAN every 24 hours. This means that vSAN checks for new health checks from VMware Analytics Cloud once a day and updates the vSAN Health Service accordingly. The other options are not correct, as they do not match the actual frequency of the online validation. References: About the vSAN Skyline Health
質問 # 30
A vSAN administrator receives a request from the application team to create a virtual machine on a vSAN datastore. The requirements state that the virtual machine needs to be available quickly after a failure occurs.
The solution must minimize administrative effort.
Which vSphere feature should the vSAN administrator implement?
- A. Distributed Services Engine
- B. vSphere High Availability
- C. Fault Tolerance
- D. vSphere Distributed Resource Scheduler
正解：B
解説：
Explanation
vSphere High Availability is the correct answer because it meets the requirements of making the virtual machine available quickly after a failure occurs and minimizing administrative effort. vSphere HA monitors the health and availability of the hosts and virtual machines in a cluster and automatically restarts any failed virtual machines on other hosts within minutes. vSphere HA also supports proactive HA, which can migrate virtual machines from hosts that are about to fail or have degraded performance. vSphere HA is easy to configure and manage, as it only requires enabling HA on the cluster level and setting some basic policies and options. Distributed Services Engine,Fault Tolerance, and vSphere Distributed Resource Scheduler are not valid or optimal solutions for this scenario. Distributed Services Engine is a new feature in vSphere 7 that provides network services such as firewalling, load balancing, routing, and NAT for virtual machines and containers. It does not directly affect the availability or recovery of virtual machines after a failure. Fault Tolerance provides continuous availability for virtual machines by creating a secondary copy of the virtual machine that runs in lockstep with the primary copy on another host. If the primary copy fails, the secondary copy takes over without any interruption or data loss. However, Fault Tolerance has some limitations and overheads, such as requiring dedicated network bandwidth, supporting only one vCPU per virtual machine, and consuming twice as much CPU and memory resources as a single virtual machine. Fault Tolerance also requires more administrative effort than vSphere HA, as it needs to be enabled and configured for each individual virtual machine. vSphere Distributed Resource Scheduler is a feature that balances the workload and resources across a cluster by automatically migrating virtual machines based on their demand and priority.
It does not directly affect the availability or recovery of virtual machines after a failure, although it can work together with vSphere HA to find optimal hosts for restarting failed virtual machines. References:
[VMware vSAN Specialist v2 Exam Preparation Guide], page 11
vSphere Availability
Distributed Services Engine
vSphere Distributed Resource Scheduler
質問 # 31
Which VMware solution requires vSAN usage?
- A. VMware Aria Automation
- B. VMware Telco Cloud Automation
- C. VMware Horizon
- D. VMware Cloud Foundation
正解：D
解説：
Explanation
The VMware solution that requires vSAN usage is VMware Cloud Foundation. VMware Cloud Foundation is an integrated software stack that bundles compute virtualization (VMware vSphere), storage virtualization (VMware vSAN), network virtualization (VMware NSX), and cloud management and monitoring (VMware vRealize Suite) into a single platform that can be deployed on premises or as a service within a public cloud.
VMware Cloud Foundation relies on vSAN as the primary storage solution for its workload domains, which are logical pools of resources that can be used to run different types of workloads. The other options are not correct. VMware Horizon, VMware Telco Cloud Automation, and VMware Aria Automation are VMware solutions that do not require vSAN usage, although they can benefit from it. VMware Horizon is a platform that delivers virtual desktops and applications across a variety of devices and locations, and it can use any supported storage solution, including vSAN. VMware Telco Cloud Automation is a cloud-native orchestration and automation platform that enables communication service providers to accelerate the deployment and lifecycle management of network functions and services across any network and cloud. It can use any supported storage solution, including vSAN. VMware Aria Automation is not a valid VMware solution name.
References: VMware Cloud Foundation Overview; VMware Horizon Overview; VMware Telco Cloud Automation Overview
質問 # 32
A vSAN administrator has two identical VMware vSAN clusters, one for staging workloads and another for production workloads. Due to an unforeseen capacity requirement, the vSAN administrator is tasked with merging the staging vSAN cluster into the production.
Which three actions should the vSAN administrator perform on the staging cluster prior to moving the vSAN nodes to the production cluster? (Choose three.)
- A. Remove all capacity drives
- B. Delete all Disk Groups
- C. Enable File Services
- D. Disable vSAN Services
- E. Mark the disks for partial reservation
- F. Delete all partitions from the capacity disks
正解：B、D、F
解説：
Explanation
The three actions that the vSAN administrator should perform on the staging cluster prior to moving the vSAN nodes to the production cluster are:
Disable vSAN Services: This will stop any vSAN-related operations on the staging cluster, such as resynchronization, rebalancing, or repair. This will also prevent any new virtual machines from being created or migrated to the staging cluster.
Delete all Disk Groups: This will remove all disks from the vSAN cluster and erase all data on them.
This will also free up the disks for use in the production cluster.
Delete all partitions from the capacity disks: This will ensure that there are no remnants of any previous vSAN configuration on the disks. This will also avoid any potential conflicts or errors when adding the disks to the production cluster.
Enabling File Services, marking the disks for partial reservation, and removing all capacity drives are not necessary or recommended actions for this scenario. Enabling File Services would add an unnecessary layer of complexity and overhead to the staging cluster. Marking the disks for partial reservation would reduce the available capacity for vSAN and potentially cause performance issues. Removing all capacity drives would leave only cache disks in the staging cluster, which would not be compatible with vSAN. References:
VMware vSAN Specialist v2 Exam Preparation Guide, page 10
質問 # 33
A vSAN administrator has an existing cluster where each ESXi host has the following:
Disk group #1 with one cache device and three capacity devices.
Disk group #2 with one cache device and two capacity devices.
What must the vSAN administrator do to expand disk group #2 to have three capacity devices?
- A. Create a new disk group with a single capacity device and then migrate the existing capacity devices
- B. Put the entire ESXi host in maintenance mode, evacuate all data, then add the new capacity device
- C. Add the new capacity device to the disk group and vSAN will automatically rebalance
- D. Put the disk group in maintenance mode, evacuate all data, then add the new capacity device
正解：C
解説：
Explanation
To expand disk group #2 to have three capacity devices, the vSAN administrator should add the new capacity device to the disk group and vSAN will automatically rebalance. This action allows the administrator to increase the storage capacity of the disk group without disrupting any ongoing operations or evacuating any data. vSAN will automatically distribute data across all devices in the disk group to balance performance and utilization. The other options are not correct. Creating a new disk group with a single capacity device and then migrating the existing capacity devices is not necessary, as it would require more steps and resources than adding a device to an existing disk group. Putting the entire ESXi host or the disk group in maintenance mode and evacuating all data is not required, as it would cause downtime and data movement that could be avoided by adding a device to an existing disk group. References: Add Devices to the Disk Group; Expanding a vSAN Cluster
質問 # 34
All of the virtual machines running on a hybrid vSAN datastore have this storage policy assigned:
Failures to Tolerate (FTT) rule is set to "2 Failures - RAID-1 (Mirroring)" The vSAN administrator needs to reduce the amount of vSAN datastore capacity the virtual machines will consume.
Which action should the vSAN administrator take to meet this goal?
- A. Modify the FTT rule to "2 Failures - RAID-5 (Erasure Coding)"
- B. Add the "Flash read cache reservation" rule to the storage policy, and set to 0%
- C. Change the FTT rule to "1 Failure - RAID-1 (Mirroring)", and select "Now" for Reapply to VMs
- D. Disable Operations reserve and Host rebuild reserve and click "Apply"
正解：C
解説：
Explanation
To reduce the amount of vSAN datastore capacity the virtual machines will consume, the vSAN administrator should change the FTT rule to "1 Failure - RAID-1 (Mirroring)", and select "Now" for Reapply to VMs. This action will reduce the number of replicas for each object from three to two, and thus free up some space on the vSAN datastore. The other options are not correct, as they will not reduce the capacity consumption.
Modifying the FTT rule to "2 Failures - RAID-5 (Erasure Coding)" will not work for a hybrid vSAN cluster, as erasure coding is only supported for all-flash clusters. Adding the "Flash read cache reservation" rule to the storage policy, and setting to 0% will not affect the capacity layer, as it only controls the amount of flash cache reserved for each object. Disabling Operations reserve and Host rebuild reserve and clicking "Apply" will not change the actual space used by the objects, as these reserves are only logicalsettings that affect how much free space is reported by vSAN. References: 1, page 9; , section 4.3
質問 # 35
......
検証済み5V0-22.23問題集と解答で最新5V0-22.23をダウンロード：https://www.passtest.jp/VMware/5V0-22.23-shiken.html
更新された100%カバー率でリアル5V0-22.23試験問題で100%合格保証が付きます：https://drive.google.com/open?id=1823xt_zj0l7YPMarGUw5iSir2nJ6SLY0