Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
Your team is building an automated continuous training (CT) and continuous deployment (CD) pipeline for a mission-critical tabular classification model on Google Cloud. You need to implement a solution using Vertex AI Pipelines that continuously evaluates candidate models and deploys them to production.
The pipeline implementation must meet the following operational requirements:
Which architecture and pipeline design should you implement?
Deploy the candidate model immediately to the production google.VertexEndpoint using ModelDeployOp, and configure a post-deployment ModelEvaluationForecastingOp step to automatically initiate an endpoint rollback if live inference accuracy drops below the threshold.
Author a Kubeflow pipeline with the Google Cloud Pipeline Components SDK using ModelEvaluationClassificationOp to generate evaluation metrics, log metadata to Vertex ML Metadata, and gate deployment to a google.VertexEndpoint via ModelDeployOp inside a dsl.Condition block.
Stream candidate model predictions to an AlloyDB database using an Apache Beam pipeline, calculate classification metrics inside AlloyDB SQL stored procedures, and invoke VertexAITextEmbeddings to update endpoint configurations.
Stream pipeline training metrics into Cloud Logging, configure a log-based metric to trigger an external Cloud Run function via Pub/Sub, and have the function parse logs to invoke ModelUploadOp via the REST API while bypassing Vertex ML Metadata.
Deploy the candidate model immediately to the production google.VertexEndpoint using ModelDeployOp, and configure a post-deployment ModelEvaluationForecastingOp step to automatically initiate an endpoint rollback if live inference accuracy drops below the threshold.
Author a Kubeflow pipeline with the Google Cloud Pipeline Components SDK using ModelEvaluationClassificationOp to generate evaluation metrics, log metadata to Vertex ML Metadata, and gate deployment to a google.VertexEndpoint via ModelDeployOp inside a dsl.Condition block.
This architecture uses Vertex AI Pipelines orchestrated via the Kubeflow Pipelines (KFP) SDK and Google Cloud Pipeline Components (GCPC). It integrates automated model evaluation using ModelEvaluationClassificationOp, logs all pipeline artifacts natively into Vertex ML Metadata, and enforces a quality deployment gate using native KFP conditional logic (dsl.Condition) before invoking ModelDeployOp.
StudyCerts
StudyCertsgoogle.VertexModel and google.VertexEndpoint preserve end-to-end data and model lineage.ModelEvaluationClassificationOp ingests ground-truth test data and candidate batch prediction outputs to compute standard classification metrics (such as ROC-AUC, accuracy, precision-recall, and sliced metrics).ModelDeployOp component inside a dsl.Condition block allows the pipeline DAG to dynamically evaluate whether the metric output meets or exceeds the required threshold. The model is uploaded via ModelUploadOp and deployed to the existing target google.VertexEndpoint only if the condition evaluates to true.google.VertexModel) across components without custom boilerplate.This approach aligns with Google Cloud recommended MLOps practices. It eliminates manual intervention, leverages managed components designed specifically for tabular classification evaluation, and avoids brittle external glue code or post-deployment rollback scripts.
Stream candidate model predictions to an AlloyDB database using an Apache Beam pipeline, calculate classification metrics inside AlloyDB SQL stored procedures, and invoke VertexAITextEmbeddings to update endpoint configurations.
Stream pipeline training metrics into Cloud Logging, configure a log-based metric to trigger an external Cloud Run function via Pub/Sub, and have the function parse logs to invoke ModelUploadOp via the REST API while bypassing Vertex ML Metadata.