VMware Cloud Foundation: Solution Architecture and Design [9.0] — Lesson 2: Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations

Learning Objectives

• Break down the prerequisites, components, roles, and decision points involved in Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations.
• Complete a controlled activity for Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations and capture logical VCF topology and failure-domain analysis.
• Challenge the result with management services sharing a failure domain that defeats the stated availability target, then justify the corrective action.

Detailed Topics

• Management-domain and workload-domain topology
• Host clusters
• VCenter placement
• Edge clusters
• Failure domains
• Expansion strategy
• And site considerations
• Decision ownership, prerequisites, and acceptance evidence for Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor configures and tests Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations within a scenario aimed at a defensible VCF 9.0 solution design that converts business requirements into resilient management, compute, networking, storage, security, and lifecycle decisions. The walkthrough contrasts a valid setup with a flawed one and uses logical VCF topology and failure-domain analysis to make the difference explicit.

Hands-On Exercise

Complete a guided task covering Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations. Establish a working baseline, reproduce “management services sharing a failure domain that defeats the stated availability target,” isolate the responsible configuration or dependency, apply a reversible fix, and update logical VCF topology and failure-domain analysis with before-and-after proof.

1. Record the starting state, assumptions, identities, topology, and expected outcome.
2. Execute the planned workflow and collect evidence at each material checkpoint.
3. Test one valid path, one boundary condition, and the stated failure scenario.
4. Document the correction, retest result, rollback option, and follow-up owner.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how logical VCF topology and failure-domain analysis should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Diagnose Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations by checking effective state, ownership, dependencies, health, logs, and recent changes. Use logical VCF topology and failure-domain analysis to locate the earliest divergence. Treat “management services sharing a failure domain that defeats the stated availability target” as a hypothesis until the same test passes after correction and under a boundary condition.

Validation Checklist

• Prerequisites and role permissions for Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations are confirmed before execution.
• The observed result agrees with expected values documented in logical VCF topology and failure-domain analysis.
• Exceptions are explained with evidence instead of being hidden by manual correction.
• The final record names the approver, monitoring point, and next improvement action.

Lesson Outcome

Learners can apply Management-domain and workload-domain topology, host clusters, vCenter placement, edge clusters, failure domains, expansion strategy, and site considerations, explain the decisions made, and defend the result with logical VCF topology and failure-domain analysis.