Free Google Cloud Professional Machine Learning Engineer practice — 6 questions on Automating and orchestrating ML pipelines, with explanations. No sign-up.
Full 12-question mixed test →
Question 1 of 6 · Automating and orchestrating ML pipelines
A Vertex AI Pipelines job defined with the KFP SDK v2 has caching enabled by default for all components. During a debugging session, a data scientist needs to force every step to re-execute for a single pipeline run without modifying the pipeline definition file. Which approach achieves this?
The enable_caching parameter on the PipelineJob object overrides component-level caching settings for that specific run, without touching the compiled pipeline definition.
Question 2 of 6 · Automating and orchestrating ML pipelines
A retail company's ML workflow must: (1) run a Vertex AI custom training job, (2) execute a data validation step in BigQuery, and (3) trigger a legacy on-premises Hadoop MapReduce job over Cloud VPN before promoting the model, with complex branching logic depending on the Hadoop job's exit code. Which orchestration tool should manage this end-to-end workflow?
Cloud Composer (managed Airflow) provides mature operators and hooks for BigQuery, Vertex AI, and SSH/on-prem connectivity, plus native support for complex conditional branching based on task exit codes/XComs.
Question 3 of 6 · Automating and orchestrating ML pipelines
After evaluating a new model version, an ML engineer needs to designate it as the version served in production, replacing the previous production model, while keeping the old version available under its own identifier for rollback. Which action correctly accomplishes this using Vertex AI Model Registry?
Model Registry aliases are unique per Model resource; assigning "default" to the new version automatically detaches it from whichever version previously held it, and the old version remains queryable by its version ID for rollback.
Question 4 of 6 · Automating and orchestrating ML pipelines
In Vertex ML Metadata, a pipeline run produces a trained model artifact from a training dataset artifact. Which statement correctly describes how this relationship is represented in the lineage graph?
Vertex ML Metadata models lineage using Artifacts (data/model objects), Executions (steps like training), and Events (typed INPUT/OUTPUT links) connecting Executions to Artifacts, plus Contexts for grouping runs.
Question 5 of 6 · Automating and orchestrating ML pipelines
A Cloud Build pipeline compiles and pushes a new KFP pipeline template whenever code is merged to main. Before the new model version can be used for production predictions, an ML lead must manually review evaluation metrics and approve the promotion. Which design best implements this human-in-the-loop approval gate using Vertex AI capabilities?
Registering the model version without the production alias means it is not served until a human explicitly reviews metrics and attaches the alias, cleanly implementing an approval gate at the promotion boundary.
Question 6 of 6 · Automating and orchestrating ML pipelines
New labeled training data is uploaded to a Cloud Storage bucket at unpredictable intervals, sometimes multiple times per day, sometimes not for a week. The team wants the retraining Vertex AI Pipeline to start automatically within minutes of new data arriving, without polling on a fixed schedule. Which architecture best satisfies this requirement?
Cloud Storage object-finalize notifications to Pub/Sub, consumed by an Eventarc-triggered Cloud Function that calls the Vertex AI Pipelines API, is a true event-driven design that starts a run within moments of new data landing, with no polling or wasted invocations.
Ready for the real thing?
The full course: two full-length practice tests, video lessons for every exam domain, hands-on labs and detailed explanations.
$129.99$34.99 with code FREETEST33 — valid through September 7.