Academy/VCDX Defense Preparation/Lab C3: Design Scenario — Regulated Industry (Healthcare + Middle East Data Residency)
This lab targets VCF 9.0

Lab C3: Design Scenario — Regulated Industry (Healthcare + Middle East Data Residency)

VCF 9.0Intermediatevcdx-distinguished⏱ 90 min

Objectives

  • Design a VCF 9.0 architecture for a UAE healthcare customer subject to UAE health-data regulation: federally, Federal Law No. (2) of 2019 on the use of ICT in health fields (the Ministry of Health and Prevention, MOHAP, is the law's 'Ministry'); in Abu Dhabi, the Department of Health (DoH) ADHICS standard, now in version 2.

Prerequisites

VCF lab environment deployed and operational

Lab Environment

Standard VCF lab environment for VCDX Defense Preparation

Tasks

Task 1 Lab C3: Design Scenario — Regulated Industry (Healthcare + Middle East Data Residency)

Design a VCF 9.0 architecture for a UAE healthcare customer subject to UAE health-data regulation: federally, Federal Law No. (2) of 2019 on the use of ICT in health fields (the Ministry of Health and Prevention, MOHAP, is the law's 'Ministry'); in Abu Dhabi, the Department of Health (DoH) ADHICS standard, now in version 2.

Step 1

Capture constraints: UAE health-data residency (Federal Law No. (2) of 2019, Article 13: health data and information related to health services provided in the UAE may not be stored, processed, generated or transferred outside the State unless a Health Authority resolution, issued in coordination with MOHAP, allows it), retention of health data for at least 25 years from the last health procedure (Article 20), ADHICS V2 compliance if the customer operates in the Emirate of Abu Dhabi, and any cybersecurity standard set by the customer's own health authority.

Step 2

Design isolated management and workload domains with NSX + vDefend zero-trust.

Step 3

Size vSAN ESA for 700 workloads with 3-year growth; pick OSA vs ESA vs Max with rationale.

Step 4

Design HCX RAV migration waves from source vSphere 7.x and write cut-over runbook.

Step 5

Design site availability and DR as two separate decisions: (a) a vSAN stretched cluster for site availability within one metro region (less than 5 ms RTT between the data sites, VCF 9.0.1 docs p.1609), and (b) DR to a secondary site inside the UAE with a stated RPO/RTO and a replication-based recovery design; add NSX Federation where networks must span the locations.

Step 6

Document which compliance controls each design decision satisfies.

Validation Gate

Check: Verify lab completion

Expected: Lab exercise completed successfully

Common Errors

Healthcare design without explicit mapping to the UAE controls named in step 1 (ADHICS V2 where it applies, Federal Law No. (2) of 2019 residency and retention rules, any other health-authority standard)
Fix: Map each applicable control from the frameworks captured in step 1 to a specific design element. Examples from ADHICS V2 (DoH Abu Dhabi, Abu Dhabi Healthcare Information and Cyber Security Standard V2, May 2024): https://www.doh.gov.ae/-/media/Feature/Resources/Standards/ADHICS-v2-standard.ashx: DP 1.4.4 and CO 9.2.6 (health information and its copies are not stored, processed or transferred outside the UAE unless DoH has approved an exemption) → every copy, backup and DR target inside the UAE; CS 1.2.2 (a cloud environment is hosted inside the UAE, including backup and disaster recovery) and CS 1.2.4 / CS 1.2.5 (cloud data at rest and in transit always encrypted, with the key not provided by the hosting cloud provider) → vSAN encryption and encrypted transport, with a key provider the customer controls wherever a provider hosts any part of the platform; AC 6.2.2 (all user activities logged with the associated identifier) and CO 6.2 (logs preserved in a centralised log management solution; retention per CO 6.2.4) → NSX DFW + vCenter/VCF RBAC with VCF Operations for logs + syslog; CO 5.1.1 (backup management) and SC 2.1.3 (RTO and RPO set through a business impact analysis) → the backup and DR design. For the federal layer cite Articles 4 (confidentiality, integrity and availability of health data), 13 (no storage or processing outside the State without a resolution) and 20 (retention of at least 25 years) of Federal Law No. (2) of 2019 Concerning the Use of the Information and Communications Technology in Health Fields: https://uaelegislation.gov.ae/en/legislations/1209/download. Quote control IDs from the edition the customer is assessed against; panelists will ask where a named control is addressed. HIPAA is US legislation and is not the baseline for a UAE design; mention it only as a contrast.
Not addressing third-party and data-residency implications in the design
Fix: If any component involves a third-party service (cloud DR, managed backup, SaaS monitoring, remote vendor support), document which components store or process health data, where the provider keeps it, and the design alternative if the provider cannot meet the residency requirement. Under ADHICS V2, CS 1.2.3 rules out access, use or support of cloud-stored health data by a party that transfers data outside the UAE for analytics or provides remote support from outside the UAE, and TP 2.1 requires security requirements, right-to-audit terms, incident notification to DoH and exit and data-return clauses in the third-party agreement; under Federal Law No. (2) of 2019, Article 13, storage or processing outside the State needs a Health Authority resolution issued in coordination with MOHAP.
Health-data flow not mapped end-to-end
Fix: Map where patient health data exists (at rest), moves (in transit), and is processed (in use) through the entire design. Each touchpoint must have encryption (at rest and in transit), access control (RBAC), audit logging and a UAE location. A gap in the data-flow map is a compliance gap against the frameworks captured in step 1.

Final Validation

Lab completed successfully

✓ All steps completed → No errors observed

Cleanup / Restore

• Revert to snapshot if needed

Design Reflection (VCDX)

Regulated industry design scenarios test compliance awareness beyond technical architecture. VCDX panelists want to see that regulatory requirements drive design decisions, not just technology features.

⚠ Known Pitfalls

Designing for healthcare without explicitly mapping the controls of the customer's frameworks (ADHICS V2 where it applies, Federal Law No. (2) of 2019 residency and retention rules, any other health-authority standard) — panelists will find the gaps.
Ignoring residency and third-party obligations for cloud DR, backup or SaaS components in the design — this is a compliance blind spot.
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.