VMware Cloud Foundation Specialist (v2) (5V0-31.22) - VMware now Broadcom

To expand storage capacity in a vSAN cluster with one disk group, you can either add more drives to hosts in the cluster, which is commonly referred to as scaling up, or add capacity drives to existing disk groups<br />
<br />
Option B: Add an additional disk group - According to search result [1], adding additional drives to a host will increase both capacity and performance [1], and each disk group contains one flash cache device and one or multiple capacity devices for persistent storage [2]. Therefore, adding an additional disk group to each host would increase the storage capacity of the vSAN cluster.<br />
<br />
Option D: Increase the number of capacity disks in the existing disk group - Search result [1] explains that vSAN clusters require capacity and cache devices to function, and each disk group can contain multiple capacity devices for persistent storage [2]. Thus, an additional way to expand storage capacity in the vSAN cluster would be to increase the number of capacity disks in the existing disk group.<br />
<br />
Reference: 1: VMware vSAN documentation 2: VMware vSAN documentation A disk group is a collection of one or more flash-based cache devices and one or more capacity devices that provide storage capacity for a vSAN cluster. A vSAN cluster can have multiple disk groups, and each disk group can have a different configuration. To expand storage capacity in a vSAN cluster where each host currently has only one disk group, the administrator can add an additional disk group or increase the number of capacity disks in the existing disk group. Adding an additional disk group involves adding more disks to the host and creating a new disk group. This approach can provide additional capacity and performance benefits, as the new disk group can be configured with different settings to optimize performance and capacity. Increasing the number of capacity disks in the existing disk group involves adding more capacity devices to the existing disk group. This approach can provide additional capacity, but may not necessarily provide performance benefits as the existing disk group may already be fully utilized.<br />
<br />
Reference: VMware vSAN 7.0 Design and Sizing Guide: https://storagehub.vmware.com/t/vmware- vsan/vmware-vsan-7-0-design-and-sizing-guide-2/ VMware vSAN Documentation: https://docs.vmware.com/en/VMware- vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-9B7C9685-64C5-49C2-8E3C- CC2E47AFBC6F.html

vSphere Single Sign-On (SSO) provides secure authentication and authorization services for VMware Cloud Foundation components, including vCenter Server and Platform Services Controller (PSC). In a consolidated architecture deployment of VMware Cloud Foundation, the vSphere SSO configuration is shared across all the workload domains. To ensure that subsequent workload domains can use the same identity sources as an external identity source registered in a consolidated architecture, the administrator needs to replicate the vSphere SSO configuration. This can be achieved by configuring the same identity sources for vSphere SSO across all the workload domains. Configuring IWA (Integrated Windows Authentication) or LDAPS (Lightweight Directory Access Protocol over SSL) as an identity source is a part of configuring the vSphere SSO configuration for identity sources. Keeping the pre-configured defaults does not guarantee that the subsequent workload domains will use the same identity sources as the external identity source registered in a consolidated architecture.<br />
<br />
Reference:<br />
<br />
VMware Cloud Foundation Operations and Administration Guide: https://docs.vmware.com/en/VMware-Cloud-Foundation/index.html VMware vSphere Security Guide: https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere- security-guide.pdf To ensure that any subsequent workload domains can be accessed using the same identity sources, it is necessary to replicate the vSphere SSO configuration across all the workload domains in a consolidated architecture deployment. This can be achieved by replicating the vSphere SSO configuration between the primary and additional SDDC Manager instances. This ensures that all the workload domains registered with the SDDC Manager will be able to consume resources and services<br />
from the same identity sources without any additional configuration in each individual workload<br />
domain.<br />
<br />
Reference: VMware Cloud Foundation: Consolidated Architecture Deployment 4.0 on Dell EMC VxRail - Technical Overview (Page 24) https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/vcf/tech- overview/vmware-cloud-foundation-consolidated-architecture-dell-emc-vxrail.pdf VMware Cloud Foundation Administration Guide https://docs.vmware.com/en/VMware-Cloud- Foundation/index.html

The SDDC Manager UI provides a single point of control for managing and monitoring your VMware Cloud Foundation instance and for provisioning workload domains. You use the navigation bar to move between the main areas of the user interface 1. The SDDC Manager UI provides an integrated<br />
<br />
view of the physical and virtual infrastructure and centralized access to manage the physical and logical resources 2. The REST API can also be used to create a new VI workload domain using VMware Cloud Foundation. The VMware Cloud Foundation API Reference Guide provides information on available operations 3.

a valid procedure to replace an expired vSAN license in a VMware Cloud Foundation environment is Option<br />
<br />
A. You can add a new vSAN license to both the SDDC Manager and vCenter Server. Then reassign the<br />
vSAN license to the cluster in the vCenter Server 1. Finally, remove the expired vSAN license from both SDDC Manager and vCenter Server 2. https://my-cloudy-world.com/2022/06/28/updating-a-vsan-license-in-vmware-cloud-foundation/