Download VMware.5V0-31.VCEplus.2023-05-17.70q.tqb

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 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.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.Reference: 1: VMware vSAN documentation 2: VMware vSAN documentationA 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.Reference:VMware vSAN 7.0 Design and Sizing Guide:https://storagehub.vmware.com/t/vmwarevsan/vmware-vsan-7-0-design-and-sizing-guide-2/VMware vSAN Documentation:https://docs.vmware.com/en/VMwarevSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-9B7C9685-64C5-49C2-8E3CCC2E47AFBC6F.html

Option B: Spine and Leaf network topology with layer-3 at Spine - A spine and leaf network topology is designed for high scalability and performance, and layer-3 at the spine ensures that there is no single point of failure for the layer-3 termination. This meets several of the requirements, including scalable high-performance networking with layer-3 termination at top-of-rack, protecting workloads from switch/NIC/rack failure, and providing isolation for DMZ workloads.Option D: Spine and Leaf network topology with layer-3 at top of rack - Similar to Option B, this topology also provides high scalability and performance, and layer-3 at the top of rack meets the requirement for layer-3 termination at top-of-rack.Option F: Core Aggregation network topology - This topology provides a highly available, redundant core switch for aggregation and routing, which meets the requirement for protecting workloads from switch/NIC/rack failure.Based on the given choices, the correct answers would be B, D, and F.Sources: [1] Designing VMware Infrastructure Topology and Architecture; Authors: Russel Nolan, Eiad Al-Aqqad [2] Network Topology Considerations for VMware vSAN;https://docs.vmware.com/en/VMware-vSAN/7.0/com.vmware.vsan.networking.doc/GUID-1A901C10-4894-4E9B-8A36-AD15ED52E61B.html [3] Spine-Leaf Architecture: Introduction;https://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-seriesswitches/datasheet-c78-733553.html

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.Reference:VMware Cloud Foundation Operations and Administration Guide:https://docs.vmware.com/en/VMware-Cloud-Foundation/index.htmlVMware vSphere Security Guide:https://docs.vmware.com/en/VMware-vSphere/7.0/vspheresecurity-guide.pdfTo 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 from the same identity sources without any additional configuration in each individual workload domain.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/techoverview/vmware-cloud-foundation-consolidated-architecture-dell-emc-vxrail.pdfVMware Cloud Foundation Administration Guidehttps://docs.vmware.com/en/VMware-Cloud-Foundation/index.html