The scenario involves a VCF consolidated architecture with seven ESXi hosts in a single cluster, likely

using vSAN as the default storage (standard in VCF consolidated deployments unless specified

otherwise). The goal is to minimize storage I/O disruption for an application’s two VMs during

business hours while maintaining availability, all within budget and hardware constraints.

Requirement Analysis:

Minimal disruption to storage I/O: Storage I/O disruptions typically occur during vSAN resyncs, host

maintenance, or resource contention.

No reduction in availability: Solutions must not compromise the cluster’s ability to keep VMs running

and accessible.

Budget/hardware constraints: Options requiring new hardware purchases are infeasible.

Option Analysis:

A . Apply 100% CPU and memory reservations on these virtual machines:

Setting 100% CPU and memory reservations ensures these VMs get their full allocated resources,

preventing contention with other VMs. However, this primarily addresses compute resource

contention, not storage I/O disruptions. Storage I/O is managed by vSAN (or another shared storage),

and reservations do not directly influence disk latency, resync operations, or I/O performance during

maintenance. The VMware Cloud Foundation 5.2 Administration Guide notes that reservations are

for CPU/memory QoS, not storage I/O stability. This option does not effectively mitigate the risk and

is incorrect.

B . Implement FTT=1 Mirror for this application virtual machine:

FTT (Failures to Tolerate) = 1 with a mirroring policy (RAID-1) in vSAN ensures that each VM’s data is

replicated across at least two hosts, providing fault tolerance. During business hours, if a host fails or

enters maintenance, vSAN maintains data availability without immediate resync (since data is

already mirrored), minimizing I/O disruption. Without this policy (e.g., FTT=0), a host failure could

force a rebuild, impacting I/O. The VCF Design Guide recommends FTT=1 for critical applications to

balance availability and performance. This option leverages existing hardware, maintains availability,

and reduces I/O disruption risk, making it correct.

C . Replace the vSAN shared storage exclusively with an All-Flash Fibre Channel shared storage

solution:

Switching to All-Flash Fibre Channel could improve I/O performance and potentially reduce

disruption (e.g., faster rebuilds), but it requires purchasing new hardware (Fibre Channel HBAs,

switches, and storage arrays), which violates the budget constraint. Additionally, transitioning from

vSAN (integral to VCF) to external storage in a consolidated architecture is unsupported without

significant redesign, as per the VCF 5.2 Release Notes. This option is impractical and incorrect.

D . Perform all host maintenance operations outside of business hours:

Host maintenance (e.g., patching, upgrades) in vSAN clusters triggers data resyncs as VMs and data

are evacuated, potentially disrupting storage I/O during business hours. Scheduling maintenance

outside business hours avoids this, ensuring I/O stability when the application is in use. This

leverages DRS and vMotion (standard in VCF) to move VMs without downtime, maintaining

availability. The VCF Administration Guide recommends off-peak maintenance to minimize impact,

making this a cost-effective, availability-preserving solution. This option is correct.

E . Enable fully automatic Distributed Resource Scheduling (DRS) policies on the cluster:

Fully automated DRS balances VM placement and migrates VMs to optimize resource usage. While

this improves compute efficiency and can reduce contention, it does not directly mitigate storage I/O

disruptions. DRS migrations can even temporarily increase I/O (e.g., during vMotion), and vSAN

resyncs (triggered by maintenance or failures) are unaffected by DRS. The vSphere Resource

Management Guide confirms DRS focuses on CPU/memory, not storage I/O. This option is not the

most effective here and is incorrect.

Conclusion:

The two most effective options are Implement FTT=1 Mirror for this application virtual machine (B)

and Perform all host maintenance operations outside of business hours (D). These ensure storage

redundancy and schedule disruptive operations outside critical times, maintaining availability

without additional hardware.

Reference:

VMware Cloud Foundation 5.2 Design Guide (Section: vSAN Policies)

VMware Cloud Foundation 5.2 Administration Guide (Section: Maintenance Planning)

VMware vSphere 8.0 Update 3 Resource Management Guide (Section: DRS and Reservations)

VMware Cloud Foundation 5.2 Release Notes (Section: Consolidated Architecture)