A team is building a simple internal tool that classifies short employee feedback comments as positive or negative. Traffic will be modest and the task itself is straightforward. The team wants to keep both cost and response latency as low as possible while still getting reliable results.
Select an answer to reveal the explanation.
Short Explanation
For a simple positive-or-negative call on a short comment, you don't need the biggest, most capable model in the catalog, you need the right-sized one. Catalogs typically include smaller, efficient models built exactly for straightforward classification work, and picking one of those keeps your bill down and your response times snappy without giving up accuracy on a task this simple. Reaching for the flagship model here is like hiring a specialist consultant to answer a yes or no question, more firepower than the job needs, and you pay for it in both dollars and speed. Spreading the same heavy model across regions solves a location problem, not a cost or speed problem tied to the model itself. And cranking up the context window just lets the model handle more text, it does nothing to make each response arrive faster. Match the tool to the job.
Full Explanation
The correct answer is D. The Foundry model catalog includes smaller, more efficient models designed for simpler tasks like short-text sentiment classification, and matching model size to task complexity keeps both cost per call and response latency low without sacrificing reliability on a task this simple. Option A is incorrect because the largest flagship model carries higher cost and latency per request, and that extra capacity is wasted on a two-class classification task that does not need deep reasoning or broad general knowledge. Option B is incorrect because deploying the same oversized model redundantly across regions addresses geographic latency and availability, not the core cost and per-request latency problem, and it multiplies infrastructure cost rather than reducing it. Option C is incorrect because increasing the context window setting affects how much input and output text a model can handle, it does not make inference faster, and an unnecessarily large context window can add overhead rather than remove it. Choosing a right-sized model for the task is the direct way to satisfy both the cost and latency goals stated in the scenario.