Academy/VCDX Defense Preparation/Lab C1: Build a VCDX-Grade Design Document for VCF 9.0 Brownfield Migration
This lab targets VCF 9.0

Lab C1: Build a VCDX-Grade Design Document for VCF 9.0 Brownfield Migration

VCF 9.0Intermediatevcdx-distinguished⏱ 105 min

Objectives

  • Produce a 120–180 page VCDX-style design document for a real-world VCF 5.2 → 9.0 migration.

Prerequisites

VCF lab environment deployed and operational

Lab Environment

Standard VCF lab environment for VCDX Defense Preparation

Tasks

Task 1 Lab C1: Build a VCDX-Grade Design Document for VCF 9.0 Brownfield Migration

Produce a 120–180 page VCDX-style design document for a real-world VCF 5.2 → 9.0 migration.

Step 1

Write the Executive Summary with scope, goals, non-goals (2–3 pages).

Step 2

Fill out a full RCAR register (Requirements, Constraints, Assumptions, Risks): minimum 25 R, 10 C, 15 A, 10 Risks.

Step 3

Create conceptual, logical, and physical designs for compute, storage, network, management (sized per the indicative Academy outline in the VCDX section: conceptual 5–8, logical 10–15, physical 40–80 pages).

Step 4

Add a Design Quality matrix: Availability, Manageability, Performance, Recoverability, Security — rate each design decision.

Step 5

Write explicit justification for every design decision with references (≥5 references per major area).

Step 6

Include operational procedures (runbooks) as an appendix.

Step 7

Add risk register with mitigation + acceptance owner per risk.

Validation Gate

Check: Verify lab completion

Expected: Lab exercise completed successfully

Common Errors

Design document exceeding 300 pages without proportional depth
Fix: A 400-page document with shallow analysis is worse than a 150-page document with deep trade-off analysis. Panelists review the document before the defense — excessive length with thin content signals padding. Target the lab objective of 120–180 pages with dense design rationale (indicative only: there is no required page count; the legacy 2024 preparation guide says successful submissions typically ran 100–300 pages).
Missing executive summary with key design decisions
Fix: The Executive Summary (2–3 pages, as in step 1) should contain: business context, key requirements, an architecture overview diagram and the key design decisions with a one-line rationale each. Panelists read the executive summary to understand the design before diving into details.
Architecture diagrams without clear layer separation
Fix: Use separate diagrams for: conceptual (business services mapped to infrastructure services), logical (component relationships without physical details), and physical (specific hardware, IP addresses, port numbers). Mixing layers creates confusion.

Final Validation

Lab completed successfully

✓ All steps completed → No errors observed

Cleanup / Restore

• Revert to snapshot if needed

Design Reflection (VCDX)

The design document IS your VCDX artifact — it must demonstrate architectural thinking, not just technical configuration. Panelists evaluate design rationale depth, not page count.

⚠ Known Pitfalls

Padding the document to 300+ pages — panelists notice and it counts against you.
Omitting the executive summary — panelists form their first impression from the executive summary.
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.