Free VMware 3V0-21.23 Practice Exam with Questions & Answers

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 VMware Cloud Foundation consolidated architecture model is designed to support small-scale environments with the ability to scale as needed. In this model, management and workload domains are deployed on the same hardware, which is suitable for environments that start small but may need to expand later. It provides a simplified, cost-effective setup for organizations that want to implement a software-defined data center (SDDC) with flexibility to grow in the future.

VLAN-backed NSX segments meet the requirement of ensuring that logical networks do not span physical network boundaries because VLANs are inherently limited to a single physical network segment. Each VLAN maps to a specific Layer 2 broadcast domain and can be isolated to particular physical network segments, ensuring that no logical network spans across physical boundaries. Additionally, static routing is supported with VLAN-backed segments, providing the flexibility needed to configure routing between different subnets or networks.

Virtual Machine Encryption

To ensure that the application’s confidential data is protected, Virtual Machine Encryption should be applied. This will ensure that even if someone gains access to the storage layer or the underlying infrastructure, the data in the virtual machine is encrypted and cannot be accessed outside of the VM, as required by the security and compliance requirements.

The vSphere Native Key Provider

The vSphere Native Key Provider can be used to manage encryption keys within the vSphere environment. Since no budget is available for additional infrastructure components or software, leveraging vSphere's native capabilities for key management ensures that encryption is securely handled without introducing external dependencies. This also aligns with the requirement to not introduce additional infrastructure.

External Key Management Service (KMS) provider

While the vSphere Native Key Provider can manage keys within the environment, if there is a requirement for a more secure or compliant key management solution, an External Key Management Service (KMS) may be used. The KMS provider allows for centralized management of encryption keys, ensuring that the keys are securely stored and controlled according to compliance standards (e.g., FIPS 140-2). Although the Native Key Provider may suffice, this option ensures that key management adheres to stricter compliance needs, especially for confidential data.

The requirement specifies that the solution must use shared storage, which refers to a storage solution that can be accessed by multiple ESXi hosts simultaneously. NFS (Network File System) is a widely used method for providing shared storage in a vSphere environment. By including the NFS mount point and the IP address of the NFS server, the architect can specify how the shared storage will be configured and accessed by the ESXi hosts, meeting the requirement for shared storage.

The design became constrained when the customer required the use of the corporate Active Directory Domain Services (AD DS) solution. The security team's intervention and insistence on using the corporate Active Directory effectively limited the options available for the authentication solution, as OpenLDAP was no longer a valid choice. At this point, the solution's scope was restricted to ensure compatibility with the customer's existing Active Directory infrastructure, which imposed a specific requirement on the design.

This statement supports the requirement for ensuring that business-critical applications have the necessary network bandwidth and maintain consistent quality of service (QoS). By creating a distributed switch and enabling Network I/O Control, you can prioritize network traffic and ensure that the necessary bandwidth is allocated to critical applications, improving their performance and quality of service.

The desired consolidation ratio for the target platform is 10:1:

The consolidation ratio is a key technical requirement as it directly influences the planning for the deployment and resource allocation in the new VMware Cloud platform. It defines how many virtual machines can be consolidated per physical host in the target environment, which is critical for the sizing and resource planning.

A VMware Aria Operations report containing current resource usage:

The VMware Aria Operations report provides actual data on the current resource consumption of the application. This report is essential for understanding how much resource the application currently uses and helps in determining the necessary capacity in the target platform. This is a technical requirement since it informs resource allocation, scaling, and performance expectations.

The goal here is to ensure that, in the event of a host failure, the workloads are restarted in the correct order based on their dependencies:

Workload 3 (Identity Broker) is required by both Application A and Application B as a dependency. It needs to be set to High Restart Priority, ensuring that it is restarted before the other dependent workloads.

Workload 4 (Reporting Tool) is required by Application B and Application C, so it should be set to High Restart Priority to ensure it is available before the other dependent workloads (like Workload 5).

Workload 5 (Management Tool) is required by Application C and should have a Medium Restart Priority, meaning it will be restarted after Workload 4.

Workloads 1 and 2 (Self-Service Portal and Database) have Low Restart Priority because they are dependent on Workload 3 (and Workload 4), but they do not have further critical dependencies after Workload 3, so they should be restarted last in the event of a failure.

This setup ensures that all applications can be recovered properly in the event of a host failure, with each workload restarting in the correct order to maintain the application dependencies.