A machine learning engineering team at a financial institution needs to build a scalable and auditable machine learning workflow on Google Cloud. The architecture must satisfy several key operational requirements: Standardize the end-to-end lifecycle—from data ingestion and preprocessing to model training, evaluation, and endpoint deployment—using modular, reusable components. Automatically track execution history, hyperparameters, and full artifact lineage (datasets, metrics, and model binaries) to ensure end-to-end reproducibility and compliance auditability. Minimize infrastructure management overhead by orchestrating the workflow using a serverless execution platform. Which architectural approach should the team implement?

Define modular pipeline steps using the Kubeflow Pipelines (KFP) SDK and prebuilt Google Cloud Pipeline Components, compile the workflow definition, and execute it using Vertex AI Pipelines to automatically capture lineage in Vertex ML Metadata.: What Vertex AI Pipelines and KFP are Vertex AI Pipelines is a serverless orchestration service in Google Cloud that automates, monitors, and governs end-to-end machine learning workflows. It supports domain-specific language (DSL) frameworks such as the Kubeflow Pipelines (KFP) SDK and TensorFlow Extended (TFX). Developers can construct modular components as standalone containerized steps or lightweight Python functions, which are compiled into a unified pipeline specification. How it meets the requirements Modular, reusable components: The Kubeflow Pipelines SDK and the Google Cloud Pipeline Components library provide standardized, modular factory functions for common ML operations—such as dataset creation, custom or AutoML training, model registry uploads, and endpoint deployments. Artifact lineage and auditability: When running on Vertex AI Pipelines, the platform automatically captures all component inputs, outputs, execution states, parameters, and produced artifacts in Vertex ML Metadata without requiring custom tracking scripts. Serverless orchestration: Vertex AI Pipelines executes workflow DAGs in a fully managed, serverless environment, eliminating the operational overhead of provisioning, scaling, or patching underlying compute clusters. Key advantages and capabilities Automatic lineage tracking: Captures complete directed acyclic graph (DAG) execution history and artifact provenance for regulatory auditability. Component reusability: Modular components can be shared across multiple team pipelines, accelerating development lifecycles. Native Google Cloud integration: Direct integration with services like Cloud Storage, BigQuery, Vertex AI Model Registry, and Vertex AI Endpoints. Serverless efficiency: Resources are provisioned dynamically for individual pipeline steps and released immediately upon task completion. Why this is optimal This approach directly satisfies all architectural goals by combining the modular authoring model of the KFP SDK with the managed execution and governance features of Vertex AI Pipelines and Vertex ML Metadata.

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Intermediate

Prepare and test your skills

Automatic Lineage Tracking in Vertex AI Pipelines

Section: Using Vertex AI pipelines to automate and orchestrate the ML lifecycle

...

Explanations

...

View source documentation

Keep the momentum going with these hand-picked practice scenarios

IntermediateProfessional Cloud Architect

An enterprise has deployed a multi-tier web application across Compute Engine virtual machines and Google Kubernetes Engine (GKE) clusters. Over several months of production traffic, operations teams have noticed rising infrastructure costs alongside intermittent performance bottlenecks during unexpected traffic spikes. As the lead cloud architect advising the team, you need to evaluate the current architecture against the Google Cloud Well-Architected Framework to optimize resource allocation, improve cost-efficiency, and enhance performance. Which approach should you recommend to achieve these architectural optimizations using Gemini Cloud Assist?

Gemini Cloud Assist

IntermediateProfessional Cloud Architect

Project IAM Admin Separation of Duties

Separation of duties

AdvancedProfessional Cloud Security Engineer

An enterprise organization wants to centralize Data Access audit logs generated across all child projects within a folder named Production into a dedicated project named sec-ops-logging. The security team must satisfy the following architectural and operational requirements: All Data Access audit logs originating in existing and future child projects under the Production folder must automatically route to the central destination. To eliminate unnecessary storage costs and data duplication, matching Data Access audit logs must not be ingested or stored in the child projects' _Default log buckets. Mandatory Admin Activity logs must continue to flow to the _Required log bucket within each local originating project. Which sink configuration should the security engineer implement to achieve this goal?

Configuring log exports (log sinks and aggregated sinks).

Want more questions like this?

Get a free certification question every week.

Last updated August 28, 2026

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Intermediate

Prepare and test your skills

Automatic Lineage Tracking in Vertex AI Pipelines

Section: Using Vertex AI pipelines to automate and orchestrate the ML lifecycle

A machine learning engineering team at a financial institution needs to build a scalable and auditable machine learning workflow on Google Cloud. The architecture must satisfy several key operational requirements:

Standardize the end-to-end lifecycle—from data ingestion and preprocessing to model training, evaluation, and endpoint deployment—using modular, reusable components.
Automatically track execution history, hyperparameters, and full artifact lineage (datasets, metrics, and model binaries) to ensure end-to-end reproducibility and compliance auditability.
Minimize infrastructure management overhead by orchestrating the workflow using a serverless execution platform.

Which architectural approach should the team implement?

...

Execute individual training and deployment tasks on Compute Engine virtual machines managed by cron jobs, and register model versions and metadata in Dataproc Metastore.

...

Package each pipeline step as an independent Cloud Run microservice, orchestrate step execution with Cloud Composer, and write pipeline parameters and artifact paths directly to BigQuery tables.

...

Deploy a self-managed Kubeflow cluster on Google Kubernetes Engine (GKE), deploy pipelines via the Kubeflow UI, and maintain an external Cloud SQL database for intermediate container state logging.

...

Define modular pipeline steps using the Kubeflow Pipelines (KFP) SDK and prebuilt Google Cloud Pipeline Components, compile the workflow definition, and execute it using Vertex AI Pipelines to automatically capture lineage in Vertex ML Metadata.

...

Explanations

What Vertex AI Pipelines and KFP are

Vertex AI Pipelines is a serverless orchestration service in Google Cloud that automates, monitors, and governs end-to-end machine learning workflows. It supports domain-specific language (DSL) frameworks such as the Kubeflow Pipelines (KFP) SDK and TensorFlow Extended (TFX). Developers can construct modular components as standalone containerized steps or lightweight Python functions, which are compiled into a unified pipeline specification.

How it meets the requirements

Modular, reusable components: The Kubeflow Pipelines SDK and the Google Cloud Pipeline Components library provide standardized, modular factory functions for common ML operations—such as dataset creation, custom or AutoML training, model registry uploads, and endpoint deployments.
Artifact lineage and auditability: When running on Vertex AI Pipelines, the platform automatically captures all component inputs, outputs, execution states, parameters, and produced artifacts in Vertex ML Metadata without requiring custom tracking scripts.
Serverless orchestration: Vertex AI Pipelines executes workflow DAGs in a fully managed, serverless environment, eliminating the operational overhead of provisioning, scaling, or patching underlying compute clusters.

Key advantages and capabilities

Automatic lineage tracking: Captures complete directed acyclic graph (DAG) execution history and artifact provenance for regulatory auditability.
Component reusability: Modular components can be shared across multiple team pipelines, accelerating development lifecycles.
Native Google Cloud integration: Direct integration with services like Cloud Storage, BigQuery, Vertex AI Model Registry, and Vertex AI Endpoints.
Serverless efficiency: Resources are provisioned dynamically for individual pipeline steps and released immediately upon task completion.

Why this is optimal

This approach directly satisfies all architectural goals by combining the modular authoring model of the KFP SDK with the managed execution and governance features of Vertex AI Pipelines and Vertex ML Metadata.

...

View source documentation

Keep the momentum going with these hand-picked practice scenarios

IntermediateProfessional Cloud Architect

Vertex AI Pipelines Service Account and VPC SC

Using Vertex AI pipelines to automate and orchestrate the ML lifecycle

IntermediateProfessional Cloud Architect

Event-Driven Vertex AI Pipeline Triggering

Using Vertex AI pipelines to automate and orchestrate the ML lifecycle

IntermediateProfessional Cloud Architect

Private Service Connect Published Services

Cloud-native networking (e.g., virtual private cloud [VPC], peering, firewalls, load balancers, routing, container networking, shared VPC, and Private Service Connect)

IntermediateProfessional Cloud Architect

An enterprise has deployed a multi-tier web application across Compute Engine virtual machines and Google Kubernetes Engine (GKE) clusters. Over several months of production traffic, operations teams have noticed rising infrastructure costs alongside intermittent performance bottlenecks during unexpected traffic spikes. As the lead cloud architect advising the team, you need to evaluate the current architecture against the Google Cloud Well-Architected Framework to optimize resource allocation, improve cost-efficiency, and enhance performance. Which approach should you recommend to achieve these architectural optimizations using Gemini Cloud Assist?

Gemini Cloud Assist

IntermediateProfessional Cloud Architect

Project IAM Admin Separation of Duties

Separation of duties

AdvancedProfessional Cloud Security Engineer

An enterprise organization wants to centralize Data Access audit logs generated across all child projects within a folder named Production into a dedicated project named sec-ops-logging. The security team must satisfy the following architectural and operational requirements: All Data Access audit logs originating in existing and future child projects under the Production folder must automatically route to the central destination. To eliminate unnecessary storage costs and data duplication, matching Data Access audit logs must not be ingested or stored in the child projects' _Default log buckets. Mandatory Admin Activity logs must continue to flow to the _Required log bucket within each local originating project. Which sink configuration should the security engineer implement to achieve this goal?

Configuring log exports (log sinks and aggregated sinks).

Want more questions like this?

Get a free certification question every week.

Last updated August 28, 2026

A machine learning engineering team at a financial institution needs to build a scalable and auditable machine learning workflow on Google Cloud. The architecture must satisfy several key operational requirements:

Standardize the end-to-end lifecycle—from data ingestion and preprocessing to model training, evaluation, and endpoint deployment—using modular, reusable components.
Automatically track execution history, hyperparameters, and full artifact lineage (datasets, metrics, and model binaries) to ensure end-to-end reproducibility and compliance auditability.
Minimize infrastructure management overhead by orchestrating the workflow using a serverless execution platform.