VMware Cloud Foundation: Solution Architecture and Design [9.0] — Lesson 1: Design methodology, stakeholder requirements, constraints, assumptions, risks, service levels, workload characteristics, sizing, availability, and recoverability

Learning Objectives

• Assess dependencies, controls, resilience, and the intended service outcome for Design methodology, stakeholder requirements, constraints, assumptions, risks, service levels, workload characteristics, sizing, availability, and recoverability.
• Demonstrate the workflow and leave reproducible evidence in requirements traceability matrix and design-risk register.
• Recommend a preventive improvement after resolving a design assumption being treated as a confirmed requirement and invalidating capacity estimates.

Detailed Topics

• Design methodology
• Stakeholder requirements
• Constraints
• Assumptions
• Risks
• Service levels
• Workload characteristics
• Sizing
• Availability
• And recoverability
• Decision ownership, prerequisites, and acceptance evidence for Design methodology, stakeholder requirements, constraints, assumptions, risks, service levels, workload characteristics, sizing, availability, and recoverability
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The demonstration traces Design methodology, stakeholder requirements, constraints, assumptions, risks, service levels, workload characteristics, sizing, availability, and recoverability from requirement through execution and review. Learners see where evidence should be collected, how requirements traceability matrix and design-risk register supports validation, and which warning signs require investigation.

Hands-On Exercise

Configure and test Design methodology, stakeholder requirements, constraints, assumptions, risks, service levels, workload characteristics, sizing, availability, and recoverability with representative infrastructure or application data. Use “a design assumption being treated as a confirmed requirement and invalidating capacity estimates” as the troubleshooting challenge, compare hypotheses, retest the affected path, and complete requirements traceability matrix and design-risk register for review.

1. Map the current workflow and mark where the expected result can first be observed.
2. Run the scenario while preserving timestamps, object identifiers, and relevant output.
3. Apply a reversible correction only after evidence supports the cause.
4. Retest the original case plus an unaffected case and update the handover record.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Design methodology, stakeholder requirements, constraints, assumptions, risks, service levels, workload characteristics, sizing, availability, and recoverability.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how requirements traceability matrix and design-risk register should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

For a failure in Design methodology, stakeholder requirements, constraints, assumptions, risks, service levels, workload characteristics, sizing, availability, and recoverability, separate access, configuration, compute, network, storage, integration, and timing causes. Compare the observed sequence with requirements traceability matrix and design-risk register; if “a design assumption being treated as a confirmed requirement and invalidating capacity estimates” is confirmed, document why broader changes were rejected.

Validation Checklist

• The scope of Design methodology, stakeholder requirements, constraints, assumptions, risks, service levels, workload characteristics, sizing, availability, and recoverability is clear, including what is deliberately excluded from the test.
• Evidence in requirements traceability matrix and design-risk register supports each material decision and outcome.
• A negative test demonstrates that controls reject or expose an invalid condition.
• Open risks, owners, due actions, and production safeguards are documented.

Lesson Outcome

Learners can apply Design methodology, stakeholder requirements, constraints, assumptions, risks, service levels, workload characteristics, sizing, availability, and recoverability, explain the decisions made, and defend the result with requirements traceability matrix and design-risk register.