VMware 3V0-21.23 Exam With Confidence Using Practice Dumps

vSphere Lifecycle Manager (vLCM) is used to manage ESXi host configurations and software versions in a consistent and streamlined manner. In this case, the architect needs to account for the heterogeneous hardware across two sites (Intel and AMD-based servers).

Since Intel and AMD processors are incompatible for remediation with a single vSphere Lifecycle Manager image, the different processor architectures should be grouped by site (not across sites). Within each site, vLCM can manage a single image per processor architecture, ensuring that each site’shosts with compatible processors are remediated consistently. Intel-based servers will be managed with one image and AMD-based servers with another image, but they can be managed in separate sites.

This approach avoids the issue where heterogeneous hardware with different processor types would need separate images. By keeping them within the same site, the architecture simplifies the lifecycle management and meets the requirement for minimizing clusters and ensuring service availability during upgrades.

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 architecture must support class three (three nines or 99.9%) system availability.

This requirement focuses on the availability of the system, which is a business goal related to ensuring that the system is operational for a specified percentage of time (99.9% uptime). It is a high-level operational requirement that is tied to business continuity and meeting customer service expectations.

The architecture must provide for system recovery point objective (RPO) of two hours.

The RPO is a business requirement related to disaster recovery. It specifies how much data loss is acceptable in the event of a failure. This requirement ensures that business processes are protected by minimizing the potential impact of data loss, making it a key business consideration.