VCAP6-DCV Design – Section 2 – Objective 2.2
Section 2 – Create a vSphere 6.x Logical Design from an Existing Conceptual Design
Objective 2.2 – Map Service Dependencies
Evaluate dependencies for infrastructure and application services that will be included in a vSphere design.
You need to understand all vSphere solution such as Update Manager and map out the dependencies on components such as ESXi, DNS, vCenter Server, Update Manager, VIBs etc. Recall that a dependency connection points to what the source depends on, so if an ESXi host requires storage than a line with an arrow from ESXi to Storage is required.
Create Entity Relationship Diagrams that map service relationships and dependencies.
Analyze interfaces to be used with new and existing business processes.
These two are essentially the same as the above but you need to be able to draw them out on the canvas
Determine service dependencies for logical components.
Once again, same as above except at the logical level, remember no IP addresses or lower level items are required at the logical design stage.
Include service dependencies in a vSphere 6.x Logical Design.
You might be tasked with creating a design based on requirements and to also put in dependencies. Pay close attention to the wording of the question. My advice is to follow the wording to the letter.
Analyze services to identify upstream and downstream service dependencies.
Once again it’s all about dependencies. For example, a Web Server depends on an Application Server that depends on a Database. All very straightforward.
Navigate logical components and their interdependencies and make decisions based upon all service relationships.
So based on your dependency diagrams you might need to understand their impact if removed or explain why they are connected a certain way. Also understand the flow of the solution. Remember that flow and dependency are not the same thing here.
Reading: