Download VMware.3V0-21.23.VCEplus.2025-02-21.24q.tqb

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.

Virtual Machine EncryptionTo 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 ProviderThe 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) providerWhile 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.

vSphere Lifecycle Manager helps reduce operational expenditure (OPEX) by automating the patching and management of the vSphere environment. It provides centralized management for host updates, ensuring consistency across the environment and reducing the manual effort required for ongoing operations. This leads to reduced operational overhead, which directly addresses the requirement to reduce OPEX.

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.

This strategy meets the requirements because:Keeps data locally: By selecting a partner with a global data center presence, data can remain local to each specific location, meeting the geographical data residency requirement.Quick scalability: The partner already has data centers in place, enabling the company to scale quickly and be functional within one month, which meets the timeline requirement.Utilizes current processes: The existing processes around vSphere can still be leveraged since the partner can deploy compatible company architecture that aligns with the company's current infrastructure and processes.VMware licensing costs: VMware licenses would be managed as part of the partnership arrangement, ensuring costs are aligned with the company's existing VMware infrastructure.

1. Production Workloads:Total vCPUs required for production:Total production vCPUs = 300 + 800 + 400 = 1,500 vCPUs2. Development Workloads:Total vCPUs required for development:3. Workload Distribution:4. vCPU to Physical Core Ratio:5. Hosts Configuration:6. Host Calculation:Production Workloads (750 vCPUs per site):Development Workloads (200 vCPUs):7. Resiliency:8. Total Hosts:Total hosts required = 4 (primary production) + 4 (secondary production) + 1 (secondary development) + 2 (N + 1) = 12 hosts.

The database must be backed up every day during the maintenance window of 1:00AM and 3:00AM.This is a logical design requirement because it specifies the timing for the backup operations. It's important to define backup schedules to align with the maintenance window, ensuring minimal disruption to production workloads. The database will be backed up using an API-based backup solution.This is a logical design decision that specifies the method of backup. Using an API-based backup solution is a modern, efficient way to ensure consistent and application-aware backups of databases.

The workload profile (CPU and memory) of each workloadUnderstanding the CPU and memory requirements for each workload is crucial for determining the capacity needed on each host. This helps ensure that each host has sufficient resources to run the virtual machines (VMs) efficiently.The amount of resources required for virtual machine (VM) swap and VM snapshotsVM swap files and snapshots require additional storage and compute resources. It's important to account for these resource requirements to avoid overloading the hosts or running into resource bottlenecks.The number of existing workloads that will be migrated onto the new solutionKnowing how many workloads will be migrated allows the architect to estimate the total resource demand and determine the number of hosts required to support the migrated workloads effectively.The hardware specification of the underlying infrastructureThe hardware specifications of the hosts, including the CPU, memory, storage, and network interfaces, play a significant role in determining how many hosts are needed to support the workloads. More powerful hardware may reduce the number of hosts required, while less capable hardware might increase the number needed.

Must use the latest version of VMware vSphereThis is a constraint because the design must adhere to the specific requirement of using the latest version of VMware vSphere. This limits the possible versions or features that can be incorporated into the solution. Must use VMXNET3 virtual network interface cardThis is also a constraint because it mandates the use of a specific virtual network interface card (VMXNET3), restricting the design to that particular choice for network connectivity.

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.