Question 6 of 100
A customer is planning to deploy a vSAN cluster to host their in-house distributed ERP system. The hardware specifications for their server nodes include:
✑ 2 x Intel Xeon CPU E5-2697 v3 @ 2.60GHz
✑ 1TB memory
Which boot device is supported for the vSAN ESXi nodes for this customer?
    Correct Answer: A

    For an ESXi host with more than 512GB of memory, such as the one described with 1TB of memory, the supported boot device needs to meet specific requirements. A SATADOM device with at least 16GB capacity is needed and it must use single-level cell (SLC) technology for durability and reliability. This ensures that the boot device can handle the increased memory and workload demands. Therefore, a 16GB SLC SATADOM device is the correct choice.

Question 7 of 100
A company hosts a vSAN 7 stretched cluster for all development workloads. The original sizing of a maximum of 250 concurrent workloads in the vSAN cluster is no longer sufficient and needs to increase to at least 500 concurrent workloads within the next six months.
To meet this demand, the original 8-node (4-4-1) cluster has recently been expanded to 16 nodes (8-8-1).
Which three additional steps should the administrator take to support the current growth plans while minimizing the amount of resources required at the witness site? (Choose three.)
    Correct Answer: A, B, C

    To support the current growth plans while minimizing resources at the witness site, the administrator should first add the new vSAN witness appliance to vCenter Server. Next, they need to deploy a new large vSAN witness appliance at the witness site to handle the increased workload. Finally, the administrator should configure the vSAN stretched cluster to use the new vSAN witness appliance. These steps ensure that the expanded cluster is properly configured and utilizes the new witness appliance effectively, without the need for an extra-large witness or a shared witness appliance, which is not required for a single stretched cluster.

Question 8 of 100
Upon investigating a workload performance issue, a vSAN administrator observed a high backend IOPs on a vSAN cluster.
Which two causes explain this behavior? (Choose two.)
    Correct Answer: B, E

    High backend IOPs in a vSAN cluster can often be attributed to scenarios where data needs to be rebuilt or resynchronized, leading to increased read and write operations. A vSAN node failure can trigger a rebuild process, as the cluster attempts to restore data redundancy, thereby increasing backend IOPs. Additionally, a change in the vSAN policy protection level from FTT=0 to FTT=1 requires data replication to meet the new policy level, which also results in increased backend IOPs as data is copied across the nodes to achieve the desired protection.

Question 9 of 100
An administrator wants to check the performance metrics for the workloads and their virtual disks that are running on a vSAN cluster, but no statistical charts are displayed in the vSphere client.
Why is this behavior being seen?
    Correct Answer: C

    In a vSAN cluster, the performance metrics for workloads and their virtual disks are dependent on the vSAN performance service. If no statistical charts are displayed in the vSphere client, it is likely because the vSAN performance service is turned off. Enabling this service is a prerequisite to view the performance charts, making option C the correct answer.

Question 10 of 100
During a maintenance action on a vSAN node, a vSAN administrator noticed that the default repair delay time is about to be reached.
Which two commands must be run to extend the time? (Choose two.)
    Correct Answer: B, C

    To extend the repair delay time on a vSAN node, you need to use the esxcli command to set the ClomRepairDelay parameter to a new value. Options B and C correctly provide commands that set this parameter with different integer values. Restarting services like clomd or vsanmgmtd is not necessary for extending the repair delay time directly.