AI-300 Practice Question 38: Prompts as Versioned Files in Git
Microsoft Machine Learning Operations Engineer Associate (AI-300) · Test 4 · question 8 of 10
An agent's system prompt is edited by several people directly in the portal. Recently a change made the agent's tone worse, and nobody can tell who changed the prompt, when, or what the previous wording was. The team wants every prompt change to be reviewed and released together with the application code, and to be able to return to an earlier prompt. What should they do?
Show answer and explanation
Answer:
GenAIOps treats prompts as code assets. Microsoft's training on managing prompts for agents in Foundry with GitHub covers applying version control principles to manage prompts as code assets and designing a repository structure for prompt versioning and collaboration. A prompt stored as a file in Git has a full history of who changed what and when, pull requests add the review step, and release tags identify the exact prompt that ships with a given application version, so an earlier version can be restored (option A).
- B is wrong because a list of published versions records versions but has no review step, and it is not tied to the release of the application code that the prompt belongs to. - C is wrong because a wiki page with notes is not linked to what is deployed, has no review gate, and cannot be used to deploy or restore a prompt automatically. - D is wrong because copying rows by hand invites mistakes, gives no review or release process, and the spreadsheet can drift from what is actually in the portal.
Reference: Manage prompts for agents in Microsoft Foundry with GitHub