In VMware's design methodology (aligned with VCF 5.2), requirements are classified as functional (what the system must do) or non-functional (how the system must perform or constraints it must meet). Functional requirements describe specific capabilities or behaviors, while non-functional requirements cover quality attributes, constraints, or compliance.
Let's categorize each:
Option A: The design must satisfy PCI-DSS compliance
PCI-DSS (Payment Card Industry Data Security Standard) compliance is a non-functional requirement. It defines security and operational standards (e.g., encryption, access control) rather than a specific system function. The VCF 5.2 Architectural Guide treats compliance as a constraint or quality attribute, not a functional capability.
Option B: The database server must support a minimum of 15,000 transactions per second This is a functional requirement. It specifies a measurable capability-the database server's ability to process 15,000 transactions per second-directly tied to workload performance. The VCF 5.2 Design Guide classifies such performance metrics as functional, as they dictate what the system must achieve.
Option C: The storage network must have a minimum latency of 10 milliseconds prior to path failover This is a non-functional requirement. It defines a quality attribute (latency) and a performance threshold for the storage network, not a specific function. VMware documentation categorizes latency and failover characteristics as non-functional, focusing on "how" the system operates.
Option D: The Production environment must be deployed into the primary data center This is a non-functional requirement or constraint. It specifies a location or deployment condition rather than a system capability. The VCF 5.2 Architectural Guide treats deployment location as a design constraint, not a functional behavior.
Option E: The platform must be capable of running 1500 virtual machines across both data centers This is a functional requirement. It defines a specific capability-the platform's capacity to support 1500 VMs across two data centers-quantifying what the system must do. VMware's design methodology includes such capacity requirements as functional, per the VCF 5.2 Design Guide.
Conclusion:
B: A functional requirement specifying database transaction capacity.
E: A functional requirement defining VM hosting capability.
These two focus on "what" the system must deliver, distinguishing them from non-functional constraints or qualities.
Reference: VMware Cloud Foundation 5.2 Architectural Guide (docs.vmware.com): Section on Requirements Classification.
VMware Cloud Foundation 5.2 Design Guide (docs.vmware.com): Functional vs. Non-Functional Requirements.