Why are disaster recovery requirements essential for a vSphere design?
An architect is designing a new vSphere-based solution for a customer.
During a requirement gathering workshop, the following information is provided:
The solution must have a primary and secondary site.
The solution must support a maximum of 1,000 concurrent workloads.
The profile of the workloads are as follows:
- 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
- Development Workloads
-- 200 x Small: 1 vCPU, 2 GB RAM
The corporate security policy states that, during normal operations, production workloads must be physically segregated from development workloads.
All production workloads are split evenly across the primary and secondary site.
All development workloads run only within the secondary site.
In the event of a disaster affecting workloads in the primary site, the secondary site must be capable of running all production and development workloads.
The vCPU to physical core ratio should be a maximum of 10:1 for production workloads and 20:1 for development workloads.
The solution should provide a minimum of N + 1 resiliency at each component level.
The target physical host hardware platform has already been defined by the company's hardware standards and therefore each host has the following configuration:
-- 2 x 24 physical cores
-- 768 GB RAM
-- 2 x 100 GB SSD drives
-- 6 x 10 GbE network cards
What is the minimum number of hosts required to meet the requirements?
An architect is designing a new vSphere environment to meet the following requirements:
- The environment must support 5,000 virtual machines.
- The environment will be built initially using 350 hosts.
Which vCenter Server appliance deployment size should the architect specify for the design?
An architect has 50 ESXi hosts to deploy and DHCP servers are not allowed on any network.
Which automated host deployment method should the architect use?
