A batch inference workflow loads a model with a URI like models:/prod.ml_team.fraud_detection@Champion. Why is this alias-based pattern useful in a Champion/Challenger process?
Answer & explanation
Correct answer: A
WHY A: Alias-based model URIs let inference jobs target a stable deployment label rather than a fixed version, so promotion can occur by alias reassignment alone.
WHY NOT B: Alias changes do not force retraining; the alias simply points at another registered version.
WHY NOT C: Aliases are mutable by design and can be reassigned to a different version of the same model.
WHY NOT D: Batch inference can use alias-based model URIs; they are executable references, not documentation.
WHY NOT E: Aliases do not run per-record champion-challenger comparisons during prediction; the URI resolves to one version.