Section 2 – Create a vSphere 6.x Logical Design from an Existing Conceptual Design

Objective 2.1 – Map Business Requirements to a vSphere 6.x Logical Design

Analyze requirements for functional and non-functional elements.

You need to understand the differences between functional and non-functional requirements

In a nutshell the best way I found the differentiate is to think of non-functional requirements as constraints, generally anything with a metric value I found to be a non-functional requirement.

For example, RTO for replication must be 5 minutes. The backup storage system must be able to de-duplicate the file server data by at least 5x.

Functional requirements are more business orientated rather than technology focused. They should determine what the system should do. For example. There must be backups. There must be auditing of all user actions when logging into the compute systems.


Build non-functional requirements into a specific logical design.

You could be tasked to take a list of non-functional requirements and build a logical design. Remember the designs are done on a Visio style canvas. Familiarize yourself with vSphere minimums and maximums including vSAN. Look into all areas such as compute, networking, storage, availability, recoverability and security


Translate stated business requirements into a logical design.

This is similar to the above however you will be analyzing more functional/business requirements and creating a logical design for them on the canvas. Remember a requirement must be adhered to, do not miss something off the design that is a requirement even if it doesn’t sound right.


Incorporate the current state of a customer environment into a logical design.

Here you will need to analyze an existing solution and document it onto the canvas. This is all about understanding the customer’s existing solution. You might be given additional requirements such as creating an extra cluster for certain VM workloads such as Web server, Application server and Database.