An administrator troubleshooting a pilot deployment asks what should drive architecture, sizing, and integration decisions for a modernized application. What is the answer?
Select an answer to reveal the explanation.
Short Explanation
Requirements drive the architecture. Defaults, headcount, and habit aren't requirements, so you need both functional and non-functional requirements to size and integrate the app correctly.
Full Explanation
The application's functional and non-functional requirements together are correct because functional requirements determine what the system must do, and non-functional requirements—availability, latency, throughput, security—determine how well it must do it. Together they constrain the architecture, sizing, and integration choices that will actually satisfy the business. The deployment option suggested by tooling defaults is incorrect because a tool default is a starting point at best and may not fit the workload at all. The number of developers currently assigned to the project is incorrect because team size affects delivery pace, not what the architecture needs to support. The architecture used by the most recent unrelated project is incorrect because a previous project's architecture answered a different set of requirements. For the exam, ground architecture decisions in the stated requirements, not in convenience.