CCDV-F practice question 1 of 10

Your Claude application is deployed to development, staging, and production environments. Each environment uses a different model version, different prompt versions, and different plugin dependencies, but the configuration is currently scattered across environment variables, hardcoded values, and undocumented setup scripts. How would you manage the configuration?

Full set: 95 questions
Answer options
A: Use the latest available model version everywhere and stop pinning model versions, on the grounds that pinning adds maintenance overhead the team should aim to reduce.
B: Move all configuration into hardcoded application code to reduce reliance on external configuration sources that are difficult to track over time.
C: Consolidate the configuration into a version-controlled system documenting model version pinning, prompt versioning, and plugin dependencies for each environment. Correct answer
D: Standardize all environments to use the same configuration values to eliminate the differences between development, staging, and production.
Correct Answer:
C. Consolidate the configuration into a version-controlled system documenting model version pinning, prompt versioning, and plugin dependencies for each environment.
Explanation

In LLM application development (LLMOps), it is a critical best practice to treat prompts, model versions, and tool dependencies as code. Consolidating these configurations into a version-controlled system ensures reproducibility, traceability, and safe deployments across different environments. Pinning specific model versions (e.g., claude-3-5-sonnet-20240620) is essential to prevent unexpected behavior changes caused by silent model updates. Versioning prompts and dependencies allows teams to track performance changes systematically and rollback safely if a deployment in staging or production fails.

Why Incorrect

A: Failing to pin model versions leads to unpredictable behavior in production, as underlying model updates can break carefully tuned prompts and workflows. B: Hardcoding configurations violates standard software engineering practices, making updates difficult and increasing the risk of exposing sensitive environment details. D: Forcing all environments to use the exact same configuration defeats the purpose of having separate development and staging environments for testing new models or prompts.

References

1. Anthropic Official Documentation, "Productionizing your application", Section: Model versioning and pinning (docs.anthropic.com/en/docs/build-with-claude/production-deployment).

2. Anthropic Official Documentation, "Prompt management", Section: Version control for prompts.

Scroll to Top