How do you version prompts and models so you can roll back safely?
Deployment and LLMOps · Pro 1
Short answer
Treat prompts, model names and parameters as versioned configuration in the repository or a prompt registry, with each production request logging which versions it used. Pin exact model versions rather than aliases that change underneath you. Release changes behind a flag or as a canary, compare metrics with the previous version, and keep the old version ready to switch back.
Deeper answer
Providers update and retire models, so an alias such as 'latest' can change behaviour without any change on your side. Pinning plus a scheduled upgrade, run through your evals, keeps changes deliberate.
Registries such as MLflow's prompt registry or a simple versioned file work; what matters is that any answer in production can be traced to the exact prompt and model that produced it.
What a strong answer covers
- Prompts and settings versioned
- Pins exact model versions
- Logs versions per request
- Canary or flag releases with comparison
- Quick rollback
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- Why pin model versions?
- What would you log to trace an answer back to its prompt?
Common mistakes
- Editing prompts directly in production
- Using moving model aliases
Learn it
- When would you serve predictions in batch, and when online?
- How would you set up CI/CD for an LLM application?
- What is the difference between data parallelism and model parallelism?
- Why does experiment tracking matter, and what do you record?
- Your model scored well offline but performed badly after launch. What could explain it?
- Explain Kubernetes pods, deployments and services, and why you would use Kubernetes for AI apps.
- What is the KV cache, and why can it cause out-of-memory errors when serving an LLM?
- How would you load test an LLM feature and set a latency budget?
- Your model provider has an outage during peak hours. What should already be in place?
- How do you manage API keys and secrets across environments?
- How do you detect and handle model drift in production?
- A bank wants your AI system but says no data may leave its network. What are the options?
- Why does an LLM reply have a wait before the first word and then a different speed after it?
- What is quantisation, and what are the trade-offs?
- When would you use a semantic cache for an LLM app, and what can go wrong?
- How would you serve an LLM feature as an API for a web app?
- How would you serve a model that is too big for one GPU, and how would you scale it to more users?
- How would you add single sign-on to an enterprise AI assistant?
- What would you capture in traces for an LLM application?
- Why use Docker for an AI application?
- What does an LLM gateway do, and when do you need one?
- Why use vLLM to serve an open-weight model instead of a simple Hugging Face script?