Question 790
A deployment script references a fine-tuned model name without pinning its base version, so later deployments differ. What should be locked?
Explanation
Correct Answer
Model names alone do not guarantee identical weights or behavior across future production releases.
Incorrect Answers
The alternative, Track training, evaluation, hosting, and inference costs for the tuned model lifecycle, belongs to a different technical condition: Training consumed large GPU resources but budget reports include only inference spending. There the source-specific mechanism or proof is: Total ownership cost extends beyond per-token inference charges and should inform the build-versus-buy decision. The condition asked about here is: A deployment script references a fine-tuned model name without pinning its base version, so later deployments differ. A suitable correction is Record the exact fine-tuned model artifact identifier and its base-model lineage; the targeted justification or result is: Model names alone do not guarantee identical weights or behavior across future production releases.
Confirm model-specific deployment region and SKU support before scheduling the production cutover. That operation would be relevant if: A team has an approved tuning recipe but the target Azure region lacks serving support for the selected model. Its corresponding reason or verification is: Training completion does not guarantee that the resulting model is deployable in every geography or serving tier. However the problem in this question is: A deployment script references a fine-tuned model name without pinning its base version, so later deployments differ. The requirement instead calls for Record the exact fine-tuned model artifact identifier and its base-model lineage; the question-specific check is: Model names alone do not guarantee identical weights or behavior across future production releases.
Attach dataset lineage, training job identifiers, evaluation results, and approval records to the deployed version. A separate source case supports that approach when: An auditor asks which source corpus produced the current regulated assistant. The deployment has a model ID but no training record. The supporting rationale or observable result is: Governance traceability requires evidence beyond a model display name when customized outputs are questioned. This question describes a different issue: A deployment script references a fine-tuned model name without pinning its base version, so later deployments differ. Address it through Record the exact fine-tuned model artifact identifier and its base-model lineage, with the required justification or evidence: Model names alone do not guarantee identical weights or behavior across future production releases.