Courseiva
hardMultiple Select

Automated Retraining Pipelines

Which THREE should be considered when setting up an automated retraining pipeline using Vertex AI Pipelines and Cloud Composer? (Choose THREE.)

Quick Answer

The answer is monitoring for data drift to trigger retraining, along with setting performance thresholds for model deployment and using Cloud Composer to orchestrate the pipeline schedule. Data drift detection is critical because it ensures retraining is initiated only when the underlying data distribution has shifted, preventing unnecessary compute costs and model staleness. Once retraining is triggered, Vertex AI Pipelines must evaluate the new model against predefined performance thresholds—such as accuracy or precision—and conditionally deploy it only if it meets or exceeds the current production model’s metrics, avoiding regressions. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding of MLOps lifecycle management, specifically how to combine Vertex AI’s evaluation capabilities with Cloud Composer’s DAG-based scheduling. A common trap is assuming retraining should run on a fixed calendar schedule rather than being event-driven by drift. Memory tip: “Drift triggers, thresholds gate, Composer orchestrates.”

⚠ Common exam trap

Google Cloud often tests the misconception that hyperparameter tuning must be part of every retraining run, but in practice it is a separate, infrequent optimization step to avoid excessive compute costs and pipeline latency.

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

✓

Setting performance thresholds for new models to decide deployment

Option A is correct because an automated retraining pipeline needs defined performance thresholds (e.g., accuracy, AUC, or RMSE gates) so that a newly trained model is only promoted to deployment when it demonstrably beats or meets the required metric, preventing regression in production. Option C is correct because Vertex AI Pipelines runs training, tuning, and evaluation steps on billable compute, so resource allocation choices such as machine type, accelerator (GPU/TPU) usage, and pipeline caching directly control cost and must be planned for a sustainable retraining cadence. Option E is correct because the trigger for retraining is typically data drift or concept drift detected via Vertex AI Model Monitoring, which emits alerts that Cloud Composer DAGs can consume to launch the pipeline, making drift monitoring a core design consideration. Option B is not required: hyperparameter tuning need not run on every retraining cycle, since it is expensive and often only needed when the model or data distribution changes materially. Option D is not relevant: the frequency of code commits reflects developer workflow, not the operational triggers or resource decisions of an automated retraining pipeline.

Answer analysis

Option-by-option breakdown

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

  • ✓

    Setting performance thresholds for new models to decide deployment

    Why this is correct

    Automated retraining produces candidate models that must be gated before deployment; defining performance thresholds lets the pipeline compare each new model against the incumbent and promote it only when metrics justify replacement, preventing silent quality regressions in production.

  • ✗

    Including hyperparameter tuning in every retraining run

    Why it's wrong here

    Hyperparameter tuning searches for optimal model parameters, not pipeline orchestration, so mandating it in every retraining run multiplies cost and runtime without addressing scheduling or data refresh. It is tempting because tuning genuinely improves model accuracy, and it would be correct when retraining is infrequent and accuracy gains justify the extra compute.

  • ✓

    Optimizing resource allocation to control costs

    Why this is correct

    Vertex AI Pipelines and Cloud Composer consume compute and orchestration charges per run, so right-sizing machine types, tuning parallel steps and scheduling retraining frequency controls recurring cost. This addresses the operational constraint of sustaining automated retraining economically at scale.

  • ✗

    Frequency of code commits to the repository

    Why it's wrong here

    Commit frequency reflects development velocity, not retraining triggers; pipelines should retrain on data drift, new labelled data or performance degradation. It is tempting because frequent commits suggest changing model code, but Vertex AI Pipelines and Cloud Composer schedule on data and metric thresholds instead.

  • ✓

    Monitoring for data drift to trigger retraining

    Why this is correct

    Data drift monitoring detects when incoming feature distributions diverge from training data, supplying the trigger condition that initiates retraining. Without drift detection the pipeline either retrains blindly on a fixed schedule or stagnates, so this directly satisfies the requirement for automation.

About these practice questions

Courseiva writes every PMLE question from scratch — 775 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

3 more ways this is tested on PMLE

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A data scientist wants to automate the retraining of a model when new data arrives in Cloud Storage. Which Google Cloud service is most appropriate for orchestrating this workflow?

easy
  • A.Cloud Run
  • B.Vertex AI Predictions
  • C.Cloud Scheduler
  • ✓ D.Cloud Composer
  • E.Cloud Functions

Why D: Cloud Composer (D) is the most appropriate service for orchestrating a retraining workflow because it is a fully managed workflow orchestration service built on Apache Airflow. It allows you to define a Directed Acyclic Graph (DAG) that triggers model retraining when new data arrives in Cloud Storage, handling dependencies, scheduling, and monitoring across multiple steps such as data validation, training, and deployment.

Variation 2. An MLOps team wants to automate the retraining of a model each time new data arrives in a BigQuery table. What is the most efficient Google Cloud service to orchestrate this pipeline?

easy
  • A.Cloud Composer with an Airflow DAG
  • B.Dataflow pipeline with a periodic trigger
  • C.Cloud Functions triggered by BigQuery events
  • ✓ D.Vertex AI Pipelines with a schedule trigger

Why D: Vertex AI Pipelines is purpose-built for orchestrating ML workflows, including model retraining. It integrates natively with BigQuery for data ingestion and supports schedule triggers to automate retraining upon new data arrival, making it the most efficient and managed option for this ML-specific task.

Variation 3. An ML team is designing an automated pipeline to retrain a recommendation model every day using new user interaction data stored in BigQuery. The pipeline must be cost-efficient, scalable, and require minimal manual intervention. Which two approaches should they consider?

medium
  • A.Deploy a custom Kubernetes cron job on GKE to run the training script directly.
  • B.Use Cloud Composer (Airflow) to schedule the pipeline with a DAG.
  • ✓ C.Use Cloud Scheduler to publish a Pub/Sub message daily, which triggers a Cloud Function that starts the Vertex AI Pipeline.
  • D.Use Dataflow to continuously read from BigQuery and trigger training when new data arrives.
  • ✓ E.Use Vertex AI Pipelines to define the workflow and preemptible VMs for training to reduce cost.

Why C: Cloud Scheduler triggers a Pub/Sub message that invokes a Cloud Function, which starts a Vertex AI Pipeline. This serverless approach is cost-efficient (no idle compute), scales automatically, and requires minimal manual intervention. Option E is correct because Vertex AI Pipelines natively orchestrates ML workflows, and using preemptible VMs reduces training costs by up to 80% while maintaining scalability.

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This PMLE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMLE exam.