An architect is designing a new VMware Cloud Foundation (VCF)-based Private Cloud solution. During the requirements gathering workshop, a stakeholder from the network team stated that: - The…

Question

Options

• AAvailability
• BPerformance
• CRecoverability
• DManageability

• A
  79% (15)
• B
  11% (2)
• C
  5% (1)
• D
  5% (1)

Explanation

In VMware Cloud Foundation (VCF) 5.2, design qualities (non-functional requirements) categorize how the system operates. The network team's requirements focus on redundancy and routing diversity, which the architect must classify. Let's evaluate: Option A: Availability This is correct. Availability ensures the solution remains operational and accessible. "N+N redundancy" (e.g., dual active components where N failures are tolerated by N spares) for physical networking components eliminates single points of failure, ensuring continuous network uptime. "Diversely routed inter-datacenter links" prevents outages from a single path failure, enhancing availability across sites. In VCF, these align with high-availability network design (e.g., NSX Edge uplink redundancy), making availability the proper classification. Option B: Performance Performance addresses speed, throughput, or latency (e.g., "10 Gbps links"). Redundancy and diverse routing might indirectly support performance by avoiding bottlenecks, but the primary intent is uptime, not speed. This doesn't fit the stated requirements' focus. Option C: Recoverability Recoverability focuses on restoring service after a failure (e.g., backups, failover time). N+N redundancy and diverse routing prevent downtime rather than recover from it. While related, the requirements emphasize proactive uptime (availability) over post-failure recovery, making this Option D: Manageability Manageability concerns ease of administration (e.g., monitoring, configuration). Redundancy and routing diversity are infrastructure design choices, not management processes. This quality

No community discussion yet for this question.