GCP Generative AI Leader Practice Question 89: Model Versioning Auto Update
Google Cloud Generative AI Leader · Test 9 · question 9 of 10
A team calls a Gemini model in production using a "latest" alias, which automatically points to the newest release available for that model line, rather than pinning a specific dated version. No application code changed, but several months later the team notices the model's output style has shifted and a few prompts behave differently than before. What most likely explains this change?
Show answer and explanation
Answer:
A "latest" alias points to the newest release for a given model line, and that release can be a stable, preview, or experimental version; Google hot-swaps the alias to the new release automatically as soon as one ships. An application that calls the alias instead of a pinned, dated version can therefore see its output style shift with no code change at all, which matches the scenario. Option A is the documented behavior that explains it.
- B is wrong because temperature is a parameter the caller sets per request; Google does not silently change a project's inference parameters. - C is wrong because a model's context window is a fixed property of that version; it does not shrink over time or with usage. - D is wrong because grounding sources are configured explicitly by the developer, such as connecting a data store or enabling Google Search grounding; they are never added automatically without a configuration change.
Reference: Gemini models