Question 71

A VCF Deployment Specialist is tasked with automating the provisioning of a new VI Workload Domain using the SDDC Manager API.
The security mandate requires that all data be encrypted at rest, and the customer insists on reusing their existing traditional 3-tier Fibre Channel storage array.
```
# SDDC Manager Domain Creation API Payload (Snippet)
{
"clusterName": "Legacy-SAN-Cluster",
"vcenterName": "vcenter-02",
"hostSpecs": [ ... ],
"fcDatastoreSpec": {
"datastoreName": "Tier1-SAN-DS",
"encryption": true
}
}
```
The deployment fails immediately. SDDC Manager reports that automated encryption enablement is not supported for external traditional SAN arrays during domain creation.
Which TWO architectural limitations of 3-tier storage explain this automation and security failure within the VCF ecosystem? (Choose 2.)
  • Question 72

    A CTO is evaluating storage options for a VCF 9.0 Workload Domain that will host a massive 2 Petabyte medical imaging archive. The applications accessing this archive require minimal compute resources (e.g., just four standard 16-vCPU web servers).
    ```
    [Customer Requirement]
    Capacity: 2,000 TB (2 PB)
    Compute: 64 vCPU total (Peak)
    Cost Constraint: Minimize software licensing CapEx.
    ```
    Which statement justifies the selection of an external SAN/NAS solution over a pure vSAN ESA HCI cluster for this specific use case?
  • Question 73

    An Infrastructure Manager imports a configuration from the vSAN Sizer tool to deploy a new 4-node vSAN cluster in SDDC Manager. The Sizer projected that the cluster would have 40 TB of usable capacity after FTT=1 (RAID-1) mirroring.
    However, immediately after SDDC Manager provisions the cluster, the capacity view shows significantly less available space for actual virtual machines than projected.
    ```
    [SDDC Manager - vSAN Capacity View (Post-Deployment)]
    Total Raw Capacity: 80.0 TB
    Total Usable (RAID-1): 40.0 TB
    Operations Reserve (Slack): 4.0 TB
    Host Rebuild Reserve: 10.0 TB
    Free Space for VMs: 26.0 TB
    ```
    Which TWO factors explain the discrepancy between the "Sizer Projected Usable Space" and the actual
    "Free Space for VMs" available post-deployment? (Choose 2.)