PDE Practice Question: Automate retraining of a model when new training…

You need to automate retraining of a model when new training data becomes available every week. The training pipeline runs on Vertex AI Pipelines and is triggered by Cloud Composer. After retraining, you want to evaluate the new model against a golden dataset. If the model's accuracy improves by at least 1%, it should be automatically deployed to the staging endpoint. What is the best way to implement the decision logic?

⚠ Common exam trap

Google Cloud often tests the misconception that external services like Cloud Functions are needed for decision logic, when in fact Vertex AI Pipelines' native conditional steps are the simpler, more integrated, and recommended approach for automated model evaluation and deployment within a pipeline.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Add a conditional step in the Vertex AI Pipeline to evaluate the model and deploy if the accuracy improvement threshold is met.

Vertex AI Pipelines supports conditional execution natively via the `Condition` component, allowing you to evaluate the new model's accuracy against the golden dataset within the same pipeline and deploy only if the improvement threshold (≥1%) is met. This approach keeps the entire retraining, evaluation, and deployment workflow automated, auditable, and tightly coupled within a single orchestrated pipeline, avoiding external triggers or manual steps.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Use Cloud Functions to compare metrics and call the endpoint if conditions are met.
Why it's wrong here
A Cloud Function comparing metrics sits outside the pipeline, so it must fetch artefacts and orchestrate deployment separately, adding a component that Vertex AI Pipelines already provides through conditional steps. It is tempting because Cloud Functions suits lightweight event-driven logic, which would be correct for simple triggers rather than pipeline-internal gating.
✓
Add a conditional step in the Vertex AI Pipeline to evaluate the model and deploy if the accuracy improvement threshold is met.
Why this is correct
A conditional step inside the Vertex AI Pipeline evaluates the freshly trained model against the golden dataset and, using pipeline conditions, deploys to the staging endpoint only when accuracy improves by at least 1%. This keeps the decision logic within the pipeline that Cloud Composer already triggers.
✗
After training, run a batch prediction job on the golden dataset and compare metrics manually.
Why it's wrong here
Manual metric comparison removes the automation the scenario demands, since deployment must occur only when accuracy improves by at least 1% without human intervention. It is tempting because batch prediction on a golden dataset is the right evaluation method, and would be correct if a person were reviewing results before promotion.
✗
Use Vertex AI Experiments to log metrics and set up an alert to manually deploy.
Why it's wrong here
Vertex AI Experiments records and compares run metrics but performs no conditional deployment; an alert still requires a human to act, breaking the required automation. It is tempting because Experiments is designed for tracking and comparing model runs, which would be correct when the goal is analysis and reporting rather than automated promotion.

Go deeper

PDE Practice Question: Automate retraining of a model when new training…

Why each option matters

Option-by-option breakdown

Related to this question