A bank can swap the model behind a Foundry deployment, and nothing records who made the swap. What should the architect require before that deployment is used in production?
Select an answer to reveal the explanation.
Short Explanation
A lock that changes hands without a signature line cannot tell you who held the key. Before production, you require an audit trail recording who changed the model on the Foundry deployment. A longer system prompt naming the model its author hopes is still in use is not a record of a later swap.
Full Explanation
Model changes need an audit trail before a deployment serves production traffic. If someone swaps the model behind a Foundry deployment and no record identifies who did it, the bank cannot reliably explain a change in answers; recording who changed the model is therefore a production requirement. A longer system prompt naming the model its author hopes is in use is wishful text, not a record of a later swap. A chat-satisfaction score measures whether people liked an answer, not who changed the deployment or whether its underlying model changed. A weekly note asking developers what they remember relies on recollection and can fail if the person who made the swap is unavailable or forgets. Exam caveat: the audit trail should cover production changes; a sandbox experiment can use a lighter record if it cannot be promoted unseen. Practical check: swap the model in a non-production deployment and confirm the record identifies who made the change and which model replaced which, then require the same record for the production deployment. A missing person’s name or model identifier is a failed check, even if the new model still answers a sample prompt.