Broadcom NVMe SSDs and RAID controllers are optimized for use in VMware Cloud Foundation environments.

In a VCF Fleet with Disaster Recovery (AZ model):
vCenter is replicated to ensure management of vSphere workloads continues after a site failure.
NSX is replicated for networking continuity (segments, TEPs, Edge services).
Other components:
SDDC Manager is fleet-level and not replicated per AZ.
VCF Automation and VCF Operations are optional add-ons and not replicated automatically by the DR model.
Thus, vCenter and NSX are replicated across AZs for resiliency.

Datastores enable shared storage access for VMs.

When a requirement is not explicitly stated, an architect should choose the simpler, lower-cost option that meets the baseline need, explicitly document the resulting assumption, and have it validated with the customer - rather than over-engineering (adding HA complexity/cost unprompted) or stalling the design.

To trackconfiguration driftin VMware Cloud Foundation, the solution usesConfiguration Templatesand drift checks:
* A: Template for the Management Cluster ensures cluster-level baseline is tracked.
* B: Schedulingdrift checksevery 30 days ensures changes are detected.
* D: Template forNSX Managerensures network and security components are included in drift detection.
C(Management vCenter) is not separately templated, it's part of cluster drift.
E(remediation every 30 days) is not required - detection is enough.
F(Host Profiles) is vSphere-specific, not aligned with VCF's drift management framework.
Reference:VMware Cloud Foundation 9.0 - Configuration Drift Management.