An administrator troubleshooting a pilot deployment is deciding which architecture task to run next. Which task correctly applies functional and non-functional requirements?
Select an answer to reveal the explanation.
Short Explanation
You need to check the proposed architecture against the documented requirements, one by one. If sizing and integration don't satisfy them, you don't proceed.
Full Explanation
The correct task is reviewing the documented requirements and confirming the proposed architecture, sizing and integration approach satisfy each one before proceeding. Requirements only guide decisions if someone actually checks the proposed design against them, which is why this review step is the task, not a side effect of some other activity. Choosing the smallest possible deployment footprint to minimise cost is incorrect because minimising cost without regard to requirements can under-provision for real availability or latency needs. Copying the architecture from the vendor's reference documentation without adjustment is incorrect because reference documentation describes a generic case, not the customer's specific requirements. Deferring architecture decisions until after the pilot is already in production is incorrect because deferring the decision past production start means requirements are applied too late to shape the architecture. For the exam, treat requirements review as an explicit task, not an assumption.