MENU
An architect is designing a VMware Cloud Foundation (VCF)-based Private Cloud solution. During the requirements gathering workshop with customer stakeholders, the following information was captured:
The solution must be capable of deploying 50 concurrent workloads.
The solution must ensure that once submitted, each service does not take longer than 6 hours to provision.
When creating the design documentation, which design quality should be used to classify the stated requirements?
In VMware Cloud Foundation (VCF) 5.2, design qualities (or non-functional requirements) categorize how the solution meets its objectives. The requirements---''deploying 50 concurrent workloads'' and ''provisioning each service within 6 hours''---must be classified under a quality that reflects their intent. Let's evaluate each option:
Option A: Availability
Availability ensures the solution is accessible and operational when needed (e.g., uptime percentage). While deploying workloads and provisioning services assume availability, the requirements focus on speed and capacity (50 concurrent workloads, 6-hour limit), not uptime or fault tolerance. This quality doesn't directly address the stated needs, making it incorrect.
Option B: Recoverability
Recoverability addresses the ability to restore services after a failure (e.g., disaster recovery). The requirements don't mention failure scenarios, backups, or restoration---they focus on provisioning speed and concurrency during normal operation. Recoverability is unrelated to these operational metrics, so this is incorrect.
Option C: Performance
This is the correct answer. Performance measures how well the solution executes tasks, including speed, throughput, and capacity. In VCF 5.2:
''Deploying 50 concurrent workloads'' is a throughput requirement, ensuring the system can handle multiple deployments simultaneously.
''Each service does not take longer than 6 hours to provision'' is a latency or response time requirement, setting a performance boundary.
Both align with the performance quality, which governs resource efficiency and user experience in provisioning workflows (e.g., via SDDC Manager or Aria Automation). This classification fits VMware's design framework.
Option D: Manageability
Manageability focuses on ease of administration, monitoring, and maintenance (e.g., automation, UI simplicity). While provisioning workloads involves management, the requirements emphasize how fast and how many---performance metrics---not the ease of managing the process. Manageability might apply to tools enabling this, but it's not the primary quality here.
Conclusion:
The design quality to classify these requirements is Performance (Option C). It directly reflects the solution's ability to handle 50 concurrent workloads and provision services within 6 hours, aligning with VCF 5.2's focus on operational efficiency.
VMware Cloud Foundation 5.2 Planning and Preparation Guide (Section: Design Qualities)
VMware Cloud Foundation 5.2 Architecture and Deployment Guide (Section: Performance Considerations)