Q: 18
You are tasked with deploying a versioned prompt for a customer-facing generative AI application. The
prompts are iteratively improved based on feedback, and you need to ensure that each version of the
prompt is tracked and accessible for rollback in case a newer version produces worse results. Which
strategy would best ensure that all prompt versions are stored and easily retrievable, while minimizing
disruption to the current deployment?
Options
Discussion
Option D is right here. Git gives proper version tracking, easy rollbacks, and is the standard for change management. I saw similar questions focus on auditability and minimal disruption-Git ticks those boxes. Pretty sure that's what they're looking for, but happy to hear if someone disagrees.
D. nice clear scenario to test real-world control for versioning and trackability.
Be respectful. No spam.
