3V0-32.23 · Question #21
An architect is designing a greenfield Cloud Management solution. During the requirements gathering workshop with the customer, the following information was captured: - The log monitoring solution…
The correct answer is C. Performance. Performance is the correct classification because both requirements describe measurable throughput and capacity thresholds - 10,000 events/second and 20 concurrent workloads are numeric benchmarks that define how fast or how much the system must handle, which is the textbook…
Question
An architect is designing a greenfield Cloud Management solution. During the requirements gathering workshop with the customer, the following information was captured:
- The log monitoring solution must be capable of collecting a minimum
of 10,000 evets per second.
- The automation solution must be capable of deploying at least 20
concurrent workloads. When creating the design documentation, which design quality should be used to classify the requirements?
Options
- AAvailability
- BManageability
- CPerformance
- DRecoverability
How the community answered
(52 responses)- A2% (1)
- B6% (3)
- C83% (43)
- D10% (5)
Explanation
Performance is the correct classification because both requirements describe measurable throughput and capacity thresholds - 10,000 events/second and 20 concurrent workloads are numeric benchmarks that define how fast or how much the system must handle, which is the textbook definition of a performance requirement.
Availability (A) is wrong because availability concerns uptime, redundancy, and fault tolerance (e.g., "99.9% SLA"), not throughput or concurrency limits. Manageability (B) is wrong because it relates to how easily administrators can operate, monitor, or maintain the system - not raw processing capacity. Recoverability (D) is wrong because it addresses how quickly a system can restore operations after failure (e.g., RTO/RPO), which has nothing to do with event ingestion rates or concurrent deployments.
Memory tip: If a requirement contains a number describing speed, volume, or capacity, think Performance. The phrase "minimum of X" or "at least Y" is a strong signal - it's setting a performance floor, not describing uptime, ease of use, or disaster recovery.
Topics
Community Discussion
No community discussion yet for this question.