Databricks Generative AI Engineer Associate Practice Question 6: Prompt Registry Aliases
Databricks Certified Generative AI Engineer Associate · Test 1 · question 6 of 10
A team changes its agent's system prompt several times a week. Right now the prompt is a string in the agent code, so every wording change needs a full code redeploy, and there is no record of which prompt produced which behavior. They want prompt versions that cannot be changed after creation, a gated promotion to production, and one-step rollback.
Which approach meets these requirements?
Show answer and explanation
Answer:
The MLflow Prompt Registry stores prompts in Unity Catalog. It works like Git: each version is an immutable snapshot with an auto-incrementing number, and aliases are mutable pointers to versions. The agent loads prompts:/catalog.schema.name@production. Promotion means pointing the production alias at a validated version, and rollback means pointing it back at an earlier version. Neither requires a code change, and every version is kept for audit.
Option A still couples every prompt change to a code redeploy, which is the problem the team wants to remove.
Option B loses history. Overwriting the production row destroys the previous prompt, so there is no immutable version to roll back to.
Option D gives no versioning or gating. "Latest file" means any edit reaches production at the next restart with no approval step and no rollback.
Reference: Prompt Registry