A build-out is meant to scale from day one, and the customer wants a single rule of thumb for making architecture decisions. Which statement best summarises how those decisions should be made?
Select an answer to reveal the explanation.
Short Explanation
Requirements first, always. You should let documented functional and non-functional requirements guide architecture, sizing, and integration choices. Defaults, stateless-by-default, and copy-paste from the last project are shortcuts around that.
Full Explanation
The requirements-driven statement is correct because requirements are the one input that is specific to this system, so architecture, sizing, and integration decisions should trace back to documented functional and non-functional requirements rather than defaults or assumptions. The default deployment topology option is wrong because a default topology may not satisfy this customer's actual availability or latency needs. The stateless-by-default option is wrong because some applications carry state that a stateless deployment cannot accommodate without loss. The previous-project configuration option is wrong because a previous project answered a different set of requirements. For the exam, state requirements-driven design as the rule, and name the shortcuts it rules out.