My objective is to design and implement a home lab using the VCAP DCD Exam Blueprint as a guide, once the home lab has been deployed I will use it for VCAP DCA study.
I will try to address each of the skills and abilities defined in the objectives, I might not be able to relate my lab design to all of the blue print objectives, but I’ll try and cover them as best I can. I’ll be using the blog as my study notes so it might be a bit rough around the edges, once the exam is done I’ll come back pretty everything up! I’ve used various sources for my notes, mostly I’ve used the documents provided in the blue print, I’ve also leaned heavily on the vBrownbag notes so a BIG Thanks to Shane Williford and Cody Bunch.
Section 1 – Create a vSphere Conceptual Design
Objective 1.1 – Gather and analyze business requirements
1. Associate a stakeholder with the information that needs to be collected.
Before a design can begin the correct information needs to be collected, this information needs to be collected and associated with particular stakeholders. In this case I am the sole stakeholder.
2. Utilize customer inventory and assessment data from a current environment to define a baseline state.
This is a green field deployment, however, if it were an existing site we would do the following…
- Perform current state analysis with tools like VMware Capacity Planner
- Review the current environment documentation
- Collected information from stakeholders and SMEs
3. Analyze customer interview data to explicitly define customer objectives for a conceptual design.
- Goals (why are we doing this and what is the time frame)
- Scope (Whats included, whats not included)
- Business (cost savings, work force reductions)
- Technical ( Uptime, consolidation, DR)
- Legislative ( compliance, security)
- Assumptions ( sufficient cooling for hardware in datacenter)
- Constraints (Must be done – re-use of existing servers or must be HP branded)
- Risks ( could prevent the project from happening like budget not yet approved or a dependency on another project
4. Identify the need for and apply requirements tracking.
Requirements will be tracked in my design
5 .Given results of a requirements gathering survey, identify requirements for a conceptual design.
Objective 1.2 – Gather and analyze application requirements
1. Given a scenario, gather and analyze application requirements
Application requirements are minimal for this deployment, all I require is vCenter Server, MS SQL Express and Update Manager.
2. Given a set of applications within a physical environment, determine the requirements for virtualization.
No P2V required for this project.
3. Gather information needed in order to identify application dependencies.
vCenter Server and update Manager will be dependent on the MSSQL database.
vCenter Server will also be dependent on SSO and Active Directory as I will be using service accounts.
4. Given one or more application requirements, determine the impact of the requirements on the design.
Application requirements are nothing out of the ordinary and will not have a major impact on the overall design.
Objective 1.3 – Determine Risks, Constraints, and Assumptions
1. Differentiate between the general concepts of a risk, a requirement, a constraint, and an assumption.
2. Given a statement, determine whether it is a risk, requirement, a constraint, or an assumption.
I’ve think the previous point covers this.
3. Analyze impact of VMware best practices to identified risks, constraints, and assumptions
I don’t see VMware best practices having an impact on my risks, constraints and assumptions.