A Storage Administrator is performing a post-deployment validation on a VCF 9.0 Workload Domain.
The design utilized the vSAN Sizer tool to forecast capacity for a 6-node Stretched Cluster (3 nodes per site).
The Sizer output predicted a specific "Free Capacity" based on an FTT=1 (RAID-1) Local + Dual Site Mirroring policy.
The administrator queries the cluster object distribution using the Ruby vSphere Console (RVC) to verify if the actual component layout matches the Sizer's assumptions.
```
[RVC Output: vsan.obj_status_report ~cluster]
Object Type: Virtual Disk (hard disk 1)
Policy: PFTT=1 (Mirror), SFTT=1 (RAID-1)
Component Layout:
Site A:
- Component 1: 50 GB (Active)
- Component 2: 50 GB (Active)
- Witness: 4 KB (Active)
Site B:
- Component 3: 50 GB (Active)
- Component 4: 50 GB (Active)
- Witness: 4 KB (Active)
Witness Site:
- Witness: 4 KB (Active)
```
Why does this RVC output validate that the Sizer tool correctly estimated a 4.0x capacity overhead for this object, and how does this affect cluster expansion planning? (Select all that apply.)