VMware Exam 2V0-13.24 Topic 4 Question 9 Discussion

In VMware Cloud Foundation (VCF) 5.2, design documentation categorizes information into requirements, assumptions, constraints, risks, and decisions to guide the solution's implementation. The need for workloads in VI Workload Domains to connect to an existing Fibre Channel (FC) storage array has specific implications. Let's analyze how this should be classified:

Option A: As an assumption

An assumption is a statement taken as true without proof, typically used when information is uncertain or unverified. The scenario states that the architect discovered this need during workshops with stakeholders, implying it's a confirmed fact, not a guess. Documenting it as an assumption (e.g., ''We assume workloads need FC storage'') would understate its certainty and misrepresent its role in the design process. This option is incorrect.

Option B: As a constraint

This is the correct answer. A constraint is a limitation or restriction that influences the design, often imposed by existing infrastructure, policies, or resources. The requirement to use an existing FC storage array limits the storage options for the VI Workload Domains, as VCF natively uses vSAN as the principal storage for workload domains. Integrating FC storage introduces additional complexity (e.g., FC zoning, HBA configuration) and restricts the design from relying solely on vSAN. In VCF 5.2, external storage like FC is supported via supplemental storage for VI Workload Domains, but it's a deviation from the default architecture, making it a constraint imposed by the environment. Documenting it as such ensures it's accounted for in planning and implementation.

Option C: As a design decision

A design decision is a deliberate choice made by the architect to meet requirements (e.g., ''We will use FC storage over iSCSI''). Here, the need for FC storage is a stakeholder-provided fact, not a choice the architect made. The decision to support FC storage might follow, but the initial discovery is a pre-existing condition, not the decision itself. Classifying it as a design decision skips the step of recognizing it as a design input, making this option incorrect.

Option D: As a business requirement

A business requirement defines what the organization needs to achieve (e.g., ''Workloads must support 99.9% uptime''). While the FC storage need relates to workloads, it's a technical specification about how connectivity is achieved, not a high-level business goal. Business requirements typically originate from organizational objectives, not infrastructure details discovered in workshops. This option is too broad and misaligned with the technical nature of the information, making it incorrect.

Conclusion:

The need to connect workloads to an existing FC storage array is a constraint (Option B) because it limits the storage design options for the VI Workload Domains and reflects an existing environmental factor. In VCF 5.2, this would influence the architect to plan for Fibre Channel HBAs, external storage configuration, and compatibility with vSphere, documenting it as a constraint ensures these considerations are addressed.

VMware Cloud Foundation 5.2 Architecture and Deployment Guide (Section: VI Workload Domain Storage Options)

VMware Cloud Foundation 5.2 Planning and Preparation Guide (Section: Design Constraints and Assumptions)

vSphere 7.0U3 Storage Guide (integrated in VCF 5.2): External Storage Integration