SIMULATION
An existing 4-node VxRail standard cluster has to be scaled out with 2 additional nodes and
configured as a stretched cluster. An administrator must prepare a vSAN storage policy that should
have the following:
- vSAN Policy Name: vSAN
Stretched Cluster
- Data protection across the sites
- Local protection: RAID-1 with
FTT=1
- Thick Provisioning
An administrator should be able to provision a VM even if the currently available cluster
resources cannot satisfy the current policy.
Use the simulator to create the required vSAN storage policy.
Answer : A
To create the required vSAN storage policy in the vSphere Client for a VxRail stretched cluster, follow these steps:
Log in to vSphere Client:
Open the vSphere Client.
Enter the username: administrator@vsphere.local.
Enter the password: VMw@r3!123.
Click Login.
Navigate to Storage Policies:
From the home screen, go to Policies and Profiles in the left-hand navigation pane.
Click on VM Storage Policies.
Create a New Storage Policy:
Click Create VM Storage Policy.
Enter the name as vSAN Stretched Cluster.
Click Next.
Configure Policy Rules:
In the Policy Structure section, choose Enable tag-based placement rules if needed.
Click Next.
Add vSAN Rules:
In the Storage Compatibility section, click Add rule and select vSAN.
Configure the following:
Primary level of failures to tolerate (PFTT): 1 failure - RAID 1 (Mirroring)
Secondary level of failures to tolerate (SFTT): 1 failure - RAID 1 (Mirroring)
Failures to Tolerate: 1
Provisioning type: Thick Provisioning
Ensure 'Force Provisioning' is enabled. This allows the VM to be provisioned even if the current resources do not satisfy the policy.
Set Data Services:
Skip the Data Services section if not applicable.
Click Next.
Review and Finish:
Review the policy settings.
Click Finish to create the storage policy.
Apply the Storage Policy to VMs:
Navigate to the VMs section.
Select the VMs that need the new storage policy.
Right-click and select VM Policies > Edit VM Storage Policies.
Choose the vSAN Stretched Cluster policy for the applicable disks.
VMware vSAN Storage Policy Creation Guide: vSAN Storage Policies
=========================
Note: The exact steps may vary slightly based on the version of vSphere Client being used. Make sure to adjust any specific configurations based on the latest guidelines and available features in the interface.
An administrator needs to place a node in maintenance mode They want to ensure vSAN does not start rebuilding absent components during the time it takes for maintenance to be completed
What would allow the administrator to achieve this?
Answer : C
To ensure that vSAN does not start rebuilding absent components while a node is in maintenance mode, an administrator should increase the vSAN Object repair timer. The Object repair timer controls the delay before vSAN initiates the rebuild of absent components. By increasing this timer, the administrator can ensure that maintenance can be completed without triggering unnecessary rebuilds, reducing the load on the system and preventing potential data redundancy issues.
VMware vSAN Configuration Guide: vSAN Configuration Guide
What is the maximum number of days vSAN capacity history is available'?
Answer : D
The maximum number of days vSAN capacity history is available is 120 days. vSAN maintains a rolling history of capacity usage, providing detailed insights into storage trends and helping administrators manage and forecast storage requirements effectively.
What are two failure states of vSAN components? (Select 2)
Answer : B, C
The two failure states of vSAN components are 'Degraded' and 'Absent.'
Degraded: A vSAN component is considered degraded when it is still accessible but has experienced a loss of redundancy or other performance issues. This state indicates that the data is still available but may be at risk if further failures occur.
Absent: A vSAN component is in an absent state when it is temporarily unavailable, often due to transient issues like network disconnections or host reboots. The system expects the component to return shortly.
In the vSphere Client, where is VxRail Health Monitoring enabled?
Answer : B
In the vSphere Client, VxRail Health Monitoring is enabled under Cluster > Configure > VxRail. This section provides an interface for configuring and monitoring VxRail-specific health and performance metrics, ensuring that administrators can effectively manage and monitor their VxRail clusters.
Steps:
Open the vSphere Client.
Navigate to the specific cluster.
Go to the Configure tab.
Select VxRail from the list.
What is the vSAN automatic rebalancing threshold recommended by VMware?
Answer : D
The recommended vSAN automatic rebalancing threshold by VMware is 20%. This threshold ensures that vSAN automatically initiates rebalancing operations when the storage utilization across the disks in the vSAN datastore becomes uneven beyond this threshold, maintaining optimal performance and storage efficiency.
VxRail nodes have been purchased to add additional capacity The new nodes are based on AMD Chipset, the current cluster is based on Intel Chipset
What should be the next step?
Answer : B
When adding VxRail nodes based on a different chipset (e.g., AMD vs. Intel) to an existing cluster, it is necessary to enable VMware Enhanced vMotion Compatibility (EVC) mode. EVC ensures CPU compatibility for vMotion by masking certain CPU features, making it possible to add nodes with different processors to the same cluster without causing compatibility issues.
Steps:
Enable VMware EVC mode on the existing cluster.
Ensure all cluster nodes meet the EVC requirements.
Add the new AMD-based nodes to the existing cluster.