VMware Cloud Foundation: Advanced Solution Architecture and Design [V9.0] — Lesson 2: Multi-site management domains, workload domains, stretched designs, edge placement, network connectivity, dependency mapping, recovery orchestration, and data locality

Learning Objectives

• Assess dependencies, controls, resilience, and the intended service outcome for Multi-site management domains, workload domains, stretched designs, edge placement, network connectivity, dependency mapping, recovery orchestration, and data locality.
• Demonstrate the workflow and leave reproducible evidence in multi-site topology and dependency-failure simulation.
• Recommend a preventive improvement after resolving a site-recovery design depending on a shared service located only in the failed site.

Detailed Topics

• Multi-site management domains
• Workload domains
• Stretched designs
• Edge placement
• Network connectivity
• Dependency mapping
• Recovery orchestration
• And data locality
• Decision ownership, prerequisites, and acceptance evidence for Multi-site management domains, workload domains, stretched designs, edge placement, network connectivity, dependency mapping, recovery orchestration, and data locality
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

Using realistic infrastructure, identities, and workloads, the instructor demonstrates Multi-site management domains, workload domains, stretched designs, edge placement, network connectivity, dependency mapping, recovery orchestration, and data locality. Checkpoints are captured in multi-site topology and dependency-failure simulation, with discussion of alternatives, side effects, and acceptance conditions.

Hands-On Exercise

Build or execute Multi-site management domains, workload domains, stretched designs, edge placement, network connectivity, dependency mapping, recovery orchestration, and data locality for a defined scenario. Introduce the condition “a site-recovery design depending on a shared service located only in the failed site,” inspect the evidence, correct the cause without discarding the audit trail, and document the accepted state in multi-site topology and dependency-failure simulation.

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 Multi-site management domains, workload domains, stretched designs, edge placement, network connectivity, dependency mapping, recovery orchestration, and data locality.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how multi-site topology and dependency-failure simulation should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Avoid changing multiple settings at once while troubleshooting Multi-site management domains, workload domains, stretched designs, edge placement, network connectivity, dependency mapping, recovery orchestration, and data locality. Preserve the failing example, review multi-site topology and dependency-failure simulation, and verify whether “a site-recovery design depending on a shared service located only in the failed site” is the root cause. After remediation, confirm downstream effects and add a monitoring action.

Validation Checklist

• The requirement for Multi-site management domains, workload domains, stretched designs, edge placement, network connectivity, dependency mapping, recovery orchestration, and data locality is linked to an owner and observable acceptance condition.
• Multi-site topology and dependency-failure simulation contains enough detail for another practitioner to repeat the check.
• Normal operation, one boundary condition, and the identified failure path have been tested.
• Access, security, downstream impact, rollback, monitoring, and support ownership are recorded.

Lesson Outcome

Learners can apply Multi-site management domains, workload domains, stretched designs, edge placement, network connectivity, dependency mapping, recovery orchestration, and data locality, explain the decisions made, and defend the result with multi-site topology and dependency-failure simulation.