3V0-32.23 · Question #56
An architect is responsible for creating a new design to centralize the logging infrastructure for an existing vSphere environment. The key stakeholder in the project has provided the following list…
The correct answer is D. The management solution must forward all logs to the existing centralized Security Incident and E. The management solution must support the collection of a minimum of 10,000 events per second. Functional requirements define what a system must do - specific capabilities and behaviors. D and E both describe functions the system must perform: actively forwarding logs to an external SIEM (D) and actively collecting a defined volume of events (E). These describe system…
Question
An architect is responsible for creating a new design to centralize the logging infrastructure for an existing vSphere environment. The key stakeholder in the project has provided the following list of requirements:
- The management solution must forward all logs to the existing
centralized Security Incident and Event Management (SIEM) solution.
- The management solution must be a minimum of N + 1 resilient.
- The management solution must provide the ability to view at least 2
months of live data.
- The management solution must meet a monthly uptime SLA of 99.9%.
- The management solution must support the collection of logs from ten
geographically separated data center locations.
- The management solution must support the collection of a minimum of
10,000 events per second. Given the information from the stakeholder, which two statements would be considered functional requirements? (Choose two.)
Options
- AThe management solution must be a minimum of N + 1 resilient.
- BThe management solution must meet a monthly uptime SLA of 99.9%.
- CThe management solution must provide the ability to view at least 2 months of live data.
- DThe management solution must forward all logs to the existing centralized Security Incident and
- EThe management solution must support the collection of a minimum of 10,000 events per second.
How the community answered
(40 responses)- A3% (1)
- B10% (4)
- C5% (2)
- D83% (33)
Explanation
Functional requirements define what a system must do - specific capabilities and behaviors. D and E both describe functions the system must perform: actively forwarding logs to an external SIEM (D) and actively collecting a defined volume of events (E). These describe system actions, not quality attributes.
A and B are non-functional requirements - they describe how well the system must perform, specifically availability and resilience characteristics (N+1 redundancy and 99.9% uptime SLA). C ("2 months of live data") is a non-functional data retention constraint - it defines a storage/capacity quality of the system rather than a discrete action the system must take.
Memory tip: Ask "Is this something the system does, or something the system is?" Functional = the system does something (forwards, collects, processes). Non-functional = the system is something (resilient, available, fast, retentive). SLAs, uptime percentages, and redundancy levels are almost always non-functional.
Topics
Community Discussion
No community discussion yet for this question.