VMware 3V0-21.23 Exam Dumps - Actual Questions Answers

Six 10TB VMFS datastores will be configured on each site for all production workloads.

This choice is based on the need to distribute production workloads across multiple datastores while ensuring that each datastore is large enough to accommodate the space required by the workloads. Given the average sizes of the virtual machines and the growth and snapshot overhead, six 10TB VMFSdatastores would be appropriate for production workloads, ensuring scalability while minimizing the number of LUNs.

Each 10TB LUN will be configured as a VMFS datastore.

VMFS (Virtual Machine File System) is the standard choice for vSphere environments when using Fibre Channel LUNs. It provides the necessary features, such as concurrency and high-performance access, for production workloads. This option is appropriate given that the storage array uses Fibre Channel for connection and VMFS is the standard file system for such configurations.

Two 10TB VMFS datastores will be configured on each site for all DMZ workloads.

The DMZ workloads are smaller in number and storage requirements compared to the production workloads, so configuring two 10TB VMFS datastores for DMZ workloads will provide enough capacity while maintaining logical isolation. This approach also minimizes the number of LUNs required to meet the storage growth needs.

1. Production Workloads:

300 x Small: 1 vCPU, 2 GB RAM

400 x Medium: 2 vCPU, 6 GB RAM

100 x Large: 4 vCPU, 8 GB RAM

TotalvCPUsrequired for production:

Small: 300 x 1 = 300 vCPUs

Medium: 400 x 2 = 800 vCPUs

Large: 100 x 4 = 400 vCPUs

Total production vCPUs= 300 + 800 + 400 =1,500 vCPUs

2. Development Workloads:

200 x Small: 1 vCPU, 2 GB RAM

Total vCPUsrequired for development:

Small: 200 x 1 =200 vCPUs

3. Workload Distribution:

Production workloads are split evenly across the primary and secondary site:750 vCPUs per site(1,500/2).

All development workloads run in the secondary site:200 vCPUs.

4. vCPU to Physical Core Ratio:

Production workloads:10:1 ratio(vCPU to core ratio).

Development workloads:20:1 ratio(vCPU to core ratio).

5. Hosts Configuration:

Each host has24 physical coresand768 GB of RAM.

Since the maximum vCPU-to-core ratio for production is 10:1, each host can support240 vCPUs(24 cores x 10).

For development, with a ratio of 20:1, each host can support480 vCPUs(24 cores x 20).

6. Host Calculation:

Production Workloads(750 vCPUs per site):

750 vCPUs for production divided by 240 vCPUs per host =3.125 hosts(rounding up =4 hostsper site for production).

Development Workloads(200 vCPUs):

200 vCPUs divided by 480 vCPUs per host =0.416 hosts(rounding up =1 hostfor development).

7. Resiliency:

N + 1 resiliencymeans we need one extra host per site to provide redundancy.

8. Total Hosts:

4 hostsfor production in the primary site.

4 hostsfor production in the secondary site.

1 hostfor development in the secondary site.

1 additional hostfor N + 1 resiliency in both sites.

Total hosts required= 4 (primary production) + 4 (secondary production) + 1 (secondary development) + 2 (N + 1) =12 hosts.

The solution will ensure that all VMware ESXi hosts within a site have access to the local VMFS datastore containing the shared VMware Tools repository.

This decision ensures that each site has local access to the VMware Tools repository, which minimizes traffic across the low-bandwidth, high-latency inter-site link. By keeping the repository within each site, the local ESXi hosts can access the repository without needing to traverse the inter-site link frequently.

The solution will set the UserVars.ProductLockerLocation advanced system setting on each VMware ESXi host to point to the local site shared repository.

This ensures that each ESXi host points to the local site repository for VMware Tools. This approach minimizes inter-site traffic by ensuring that all updates and patches are performed using local resources, avoiding the need to transfer VMware Tools files over the low-bandwidth, high-latency connection.

The solution will create a shared repository on a VMFS datastore within each site that contains all approved versions of VMware Tools.

This decision ensures that both sites have a local copy of the approved VMware Tools versions, in line with REQ001, which mandates that only IT Security Team-approved versions of VMware Tools should be installed. Additionally, it minimizes inter-site traffic, as both sites will use their local repositories.