A rollout is scheduled for next quarter and the architects want to avoid an architecture mismatch. Which combination of inputs should they use to size and integrate the new system?
Select an answer to reveal the explanation.
Short Explanation
Leave out either half and you've designed for what it does or how well, never both. You need both the functional requirements and the non-functional requirements to size and integrate the system.
Full Explanation
Functional requirements without non-functional targets can produce a correct system that performs poorly, and non-functional targets without functional requirements have nothing concrete to be measured against, so both are needed together. Relying only on functional requirements is incorrect because retrofitting availability or latency after go-live is far more disruptive than designing for them from the start. Relying only on non-functional requirements is incorrect because functionality is not something that can be deferred once the architecture is already fixed around it. Relying on neither set and using the vendor's recommended configuration is incorrect because a vendor recommendation is generic and does not reflect this system's specific requirements. For the exam, use functional and non-functional requirements together, not as alternatives.