Empirical model testing requires a defined decision frame. Option D must occur first because the quality threshold, acceptable latency, expected request volume, and associated cost envelope determine what constitutes a successful result. Without these criteria, a representative-sample test can produce measurements but cannot support a defensible selection.

Option C is the next upstream step. Known model capabilities and the workload profile are used to identify a plausible candidate rather than testing models arbitrarily. Anthropic’s model-selection guidance recommends evaluating capability, speed, cost, and effort requirements before narrowing the candidate set. Choosing the Right Model

Option A occurs after empirical testing because the architect cannot know which lightest model consistently meets the quality bar until sample results have been evaluated. Option B belongs to ongoing lifecycle management after a new version becomes available. Option E is a deployment-governance activity that follows successful model selection, security review, and readiness validation.

The correct sequence is: define workload criteria, shortlist candidate models, run a representative evaluation, compare quality and operational metrics, select the least costly model that reliably satisfies all gates, and periodically retest the decision.

Study Guide references/topics: Requirements-driven model selection; representative sampling; quality thresholds; latency and volume requirements; capability–cost trade-offs; model lifecycle reassessment.

===============