The supplied examination page marks B . The scenario already demonstrates why model upgrades must be treated as evaluated software changes rather than automatic replacements: the new model improves one metric while introducing a regression in another.
Anthropic's official model-selection guidance recommends creating benchmark tests specific to the application's use case, testing models with the application's actual prompts and data, comparing response quality and edge-case performance, and weighing performance against operational tradeoffs. Therefore, the correct action is to adapt the multi-section system prompt to the new model's behavior and repeat the evaluation. Only after the formatting regression is eliminated—or reduced below an explicitly acceptable threshold—should the upgrade proceed.
A incorrectly assumes that an 8% reasoning improvement numerically compensates for a 3% malformed-output rate; these metrics measure different consequences and cannot simply be subtracted. C treats the known incompatibility only downstream instead of first correcting the prompt/model interaction. D permanently rejects future improvement and is inconsistent with controlled lifecycle evolution.
The engineering principle is migration through regression testing and adaptation , not blind upgrading or permanent version avoidance.
Relevant Claude Developer topics: Systems Life Cycle, model migration, regression evaluation, prompt adaptation, compatibility testing, deployment gates, and continuous evolution .
===============
