An administrator troubleshooting a pilot deployment finds that latency requirements were never documented before the architecture was chosen. What symptom would this produce?
Select an answer to reveal the explanation.
Short Explanation
Skip the latency requirement and you get a system that works correctly but answers too slowly to matter. You'll meet functional expectations while response times under real load blow past what users or downstream systems can tolerate.
Full Explanation
The correct symptom is an architecture that meets functional expectations but has response times under real load that exceed what users or downstream systems can tolerate. An architecture chosen without a latency target can still be functionally correct while being too slow for the use case, because nothing in the design forced a decision that would keep response times within bounds. The startup-failure symptom is incorrect because a missing latency requirement does not prevent the application from starting under any configuration. The incorrect-calculation symptom is wrong because calculation correctness is a functional concern, unrelated to latency. The total-integration-failure symptom is also wrong because integration failure has other causes; a missing latency requirement does not block integration by itself. For the exam, connect an undocumented non-functional requirement to the specific symptom it produces later.