VMware 3V0-21.23 VMware vSphere 8.x Advanced Design Exam Practice Test

Answer : A, C, D

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 VMFS datastores 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.

Answer : B

The customer's requirement for making it easy to identify and apply patches or updates to ESXi hosts, including pre-staging the files, is focused on simplifying the management of the vSphere environment. This is a key aspect of manageability, which refers to the ease with which IT administrators can handle tasks like patching, updates, and configuration management in a consistent and efficient manner.

Answer : B, D

The storage may not have capacity to accommodate 20% year-over-year virtual machine growth.

This is a risk because, while the assumption is that the storage hardware has sufficient capacity, there is a possibility that the hardware may not be able to support future growth, especially if the customer's workload grows faster than expected. Documenting this risk ensures that the design considers potential capacity constraints.

The customer may not have an existing licensing subscription that covers features the architect intends to use.

This is a risk because although the assumption is that the customer will provide licensing, there may be discrepancies between the features required for the design and the customer's existing licensing. This risk ensures that the architect verifies that the customer's licensing aligns with the solution requirements.

Answer : A, C

VMware Validated Solutions offer prescriptive, step-by-step runbooks that help guide users through the deployment process. These runbooks ensure that the implementation follows VMware's recommended practices, reducing complexity and ensuring consistency across deployments.

VMware Validated Solutions are designed based on VMware's best practices, ensuring that the deployed solution is optimized for performance, security, and scalability. This helps organizations achieve a reliable and efficient infrastructure aligned with VMware's recommended guidelines.

Answer : A, B, F

Critical Workloads: 12 hours

For critical workloads, the recovery time objective (RTO) is 1 hour, and the work recovery time (WRT) is 12 hours. Since the customer can tolerate a maximum of 12 hours to restore these workloads after a disaster, the MTD for critical workloads is 12 hours.

Development Workloads: 24 hours

For development workloads, the RTO is 24 hours and the WRT is also 24 hours. Therefore, the MTD for development workloads is 24 hours because it is the maximum time that the customer can tolerate for these workloads to be unavailable.

Production Workloads: 24 hours

Production workloads have an RTO of 12 hours and a WRT of 24 hours. Since the disaster recovery solution waits for the recovery of critical and production workloads before recovering development workloads, the MTD for production workloads can be up to 24 hours, including the time to fully recover both critical and production workloads.

Answer : D

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.

Answer : D

To meet the customer requirements, we need to address the two specific scenarios:

Workloads must be automatically relocated to other hosts in the event that a host hardware is marked as degraded:

This requirement can be fulfilled by Proactive HA. Proactive HA is a feature of vSphere HA that works in conjunction with hardware health monitoring tools, such as the vendor's plugin for vCenter. When the vendor's monitoring tool marks a host as degraded (due to hardware issues), Proactive HA can automatically trigger the migration of workloads to other hosts, based on the Automation Level configuration.

Workloads must be automatically restarted on other hosts in the event of a host failure:

This can be managed using vSphere HA with the setting to restart VMs when a host fails. This ensures that in the event of a host failure, workloads are automatically restarted on available hosts in the cluster.

By enabling Proactive HA with an Automation Level of Automated, the architect ensures that degraded hosts are automatically handled (through workload migration) without manual intervention.