A business analyst must summarize lengthy vendor contracts in GitHub, then brainstorm creative launch slogans for the same product. Accuracy and careful reasoning matter for the summary, while speed and variety matter for slogans. Which approach to choosing a Copilot model best fits this business purpose?

The correct approach aligns model strengths to task demands, assigning careful, accuracy-focused reasoning to vendor contract summaries where misinterpretation carries business risk, while assigning fast, versatile generation to slogan brainstorming where speed and diverse alternatives are valuable. The approach that reuses the stronger reasoning model for both tasks is conceptually sound for consistency and risk reduction, but it fails by over-applying deliberative reasoning where divergent, rapid ideation is explicitly required, sacrificing efficiency and variety. The approach that uses the fast versatile model for both tasks is a common productivity pattern for throughput, but it fails by under-provisioning reasoning for contracts, where quick passes increase the risk of overlooking nuanced obligations and precise language. The approach that splits models correctly but moves contract work outside GitHub fails by location and context, because keeping summaries where source files, version history, and collaboration live preserves traceability and reduces copy errors. An exam caveat is to read the business purpose rather than assuming stronger is always better or faster is always sufficient, since the prompt contrasts accuracy versus speed. As a practical check, confirm where the contract content resides, run the summary with the reasoning-focused choice and spot-check key terms, then time-box slogan generation with the fast choice and retain only the most promising variants for review.