CCDV-F practice › Applications & Integration · Question 41 of 92
Applications & Integration
An integration hardcodes the model reference as a rolling alias in production. What risk does this introduce?
Show answer and explanation
Answer: B — Behaviour can change without any deploy when the alias resolves to a new version
This is the model-changes-under-you property unique to LLM systems — traditional software only changes when you deploy. Pinning an exact version is the control.
Keep going
More Applications & Integration questions
- A compliance requirement states claim data must never leave the hospital's network…
- A response comes back with stop_reason of 'refusal'. What should production code do?
- A team is choosing between calling Claude directly and going through a third-party…
- A product spec says: 'Clinicians must be able to upload a scanned referral letter and…
- A requirement states claim data may not leave the hospital network, and separately that…