Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
An organization manages multiple versions of a fraud detection machine learning model in Model Registry. The engineering team wants to streamline the model release process so that downstream serving applications can automatically consume newly promoted models (such as staging or production) without needing application code or configuration updates whenever a new version ID is generated.
Which approach should the team implement in Model Registry?
Resource labels are key-value metadata pairs applied to cloud assets in Google Cloud. They are primarily used for organizational tracking, cost allocation, filtering in dashboards, and grouping resources for billing and governance purposes.
stage=production, extract its ID, and then route traffic, adding unnecessary overhead and code complexity.stage: production, creating ambiguity during deployment.The scenario required organizing models for monthly cost allocation, tracking which team owns a model, or filtering models across teams in the Google Cloud console.
In Model Registry, each model version is assigned an immutable version ID upon creation. This identifier represents a specific snapshot of model artifacts, training parameters, and metadata to maintain lineage and reproducibility.
The organization had strict compliance policies mandating the permanent deletion of corrupted or deprecated model artifacts that are no longer authorized to exist.
This approach involves creating distinct, independent parent model resources in Model Registry (e.g., fraud-model-staging and fraud-model-production) and copying or retraining artifacts into the production resource during release cycles.
The staging and production environments were hosted in completely isolated Google Cloud projects with strict Virtual Private Cloud (VPC) Service Controls and distinct security perimeters.
A model alias in Model Registry is a mutable, named pointer assigned to a specific version of a machine learning model. Similar to Git branch references or Docker tags (such as :latest or :stable), an alias allows users and automated systems to identify, deploy, or query a model version using a human-readable text string rather than an immutable, generated version ID.
staging or production can be assigned directly to specific model versions to clearly demarcate their lifecycle stages.fraud_detector@production). When a new model version is validated, moving the alias to the new version instantly redirects application traffic without modifying serving code.
default alias, ensuring standard calls without explicit versions function smoothly.Using model version aliases decouples model deployment and serving infrastructure from model retraining pipelines. Data science teams can train, test, and promote models independently while client applications consistently query stable alias endpoints.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated