About the Professional Machine Learning Engineer exam

The Google Cloud Professional Machine Learning Engineer certification validates that you can build, evaluate, productionize, and optimize AI solutions using Google Cloud capabilities. The exam covers six Domains: architecting low-code AI solutions; collaborating within and across teams to manage data and models; scaling prototypes into ML models; serving and scaling models; automating and orchestrating ML pipelines; and monitoring AI solutions. Expect scenarios built around Gemini Enterprise Agent Platform, BigQuery ML, and responsible AI practices.

Professional Machine Learning Engineer exam domains

Exam Study Guide

Developing ML models using BigQuery ML or AutoML on Gemini Enterprise Agent Platform

Building models with low-code tools means matching the business goal, data location, and latency need to the right training environment. BigQuery ML trains with SQL where warehouse data already lives, Vertex AI AutoML automates architecture search and tuning, and custom training on Gemini Enterprise Agent Platform handles everything else. Data flows from storage to training through the BigQuery Storage API, BigQuery I/O connector, or Cloud Storage sharded reads, and the correct choice preserves data locality while avoiding custom code when a predefined routine is enough.

Continue with this study guide: Developing ML models using BigQuery ML or AutoML on Gemini Enterprise Agent Platform

Building AI solutions using Google Cloud AI APIs or foundational models

Evaluating and selecting a model from Gemini Enterprise Agent Platform Model Garden is the process of matching task requirements, evaluation evidence, and deployment constraints to an optimal low-code AI solution. The candidate model receives prompts and produces responses, the Gen AI evaluation service measures those responses, and the serving configuration determines whether latency, throughput, cost, and accuracy targets are met. A model is an optimal fit only when task type, input and output handling, and serving compatibility all align.

Continue with this study guide: Building AI solutions using Google Cloud AI APIs or foundational models

Exam Study Guide

Tracking and running ML experiments

Choosing the development and experimentation environment is the decision between fast interactive prototyping and managed, reproducible execution with the right accelerator. Interactive work uses Cloud Data Fusion and Dataflow notebooks to test logic quickly, while managed execution uses Dataflow pipelines, Gemini Enterprise Agent Platform Pipelines, or self-managed Kubeflow Pipelines on Google Kubernetes Engine (GKE) to capture runs, lineage, and scale. Framework code flows from the development container through the runtime to central processing units (CPUs), graphics processing units (GPUs), or Cloud tensor processing units (TPUs), so container, machine type, and accelerator choice control performance and reproducibility.

Continue with this study guide: Tracking and running ML experiments

Model prototyping using notebooks (e.g., Gemini Enterprise Agent Platform Workbench and Colab Enterprise)

Collaborative and secure notebook development on Google Cloud separates per-user experimentation from governed promotion to production. Traffic flows from the notebook environment to BigQuery, Cloud Storage, Vertex AI Feature Store, and Vertex AI training and serving services, with Identity and Access Management (IAM), Virtual Private Cloud (VPC), and VPC Service Controls checking every hop. Vertex AI Workbench provides per-user development instances, Colab Enterprise provides a managed collaborative option, and Vertex ML Metadata, Git, container images, Cloud Build, and Vertex AI Pipelines connect prototyping to tracked deployment.

Continue with this study guide: Model prototyping using notebooks (e.g., Gemini Enterprise Agent Platform Workbench and Colab Enterprise)

Exploring and preprocessing data for ML

Organizing different data types for machine learning means placing tabular data in BigQuery and unstructured data in Cloud Storage so distributed trainers and serving systems can load each type at high throughput. Source data flows from online service logs, on-device images, or web-scraped documents into a dedicated training store that is separate from production systems. The training store uses columnar tables for tabular data and large binary containers for unstructured data, so repeated experimentation reads do not contend with production writes and latency requirements. Serialization follows the training framework, with sharded TFRecord files for TensorFlow and Avro files for other frameworks.

Continue with this study guide: Exploring and preprocessing data for ML

Exam Study Guide

Building models given the task considering cost, complexity, latency, and scalability

Choosing the model type means matching data structure, problem formulation, and operational limits to the model family that can learn and serve the task. Ordered timestamped numbers point to forecasting, high-volume high-dimensional data points to deep neural networks, and text or combined media points to large language and multimodal models.

Continue with this study guide: Building models given the task considering cost, complexity, latency, and scalability

Choosing appropriate hardware for training

Evaluation of compute and accelerator options is the process of matching a machine learning workload to central processing units (CPUs), graphics processing units (GPUs), or Tensor Processing Units (TPUs) based on math patterns, batch size, cost, and operational constraints. On Google Cloud, training traffic flows from job queues and autoscalers to colocated accelerator hosts, and the choice of processor, machine series, orchestration system, and pricing model determines throughput, stability, and price per training hour.

Continue with this study guide: Choosing appropriate hardware for training

Training models

Organizing training data on Google Cloud means separating operational sources from training-optimized copies in BigQuery and Cloud Storage, then registering those copies as versioned Vertex AI Datasets. Data flows from source systems such as service logs, devices, or web documents into BigQuery tables or Cloud Storage containers, then into a managed dataset that records schema, statistics, and lineage to custom-trained models. This separation protects production performance while giving training jobs high-throughput, reproducible inputs that can be reused across AutoML, custom training, and pipeline jobs.

Continue with this study guide: Training models

Exam Study Guide

Scaling online model serving

Agent Platform Feature Store is a managed service that centralizes machine learning features in BigQuery for offline training and in a FeatureOnlineStore for low-latency online inference. Data flows from batch and streaming sources into BigQuery tables or views, then from BigQuery into the online store through FeatureView sync operations, then from the online store to real-time applications. BigQuery remains the durable source of truth with full history, while the online store holds materialized latest values optimized for serving.

Continue with this study guide: Scaling online model serving

Serving models

Batch and online inference on Google Cloud separate large asynchronous jobs from real-time serving. Vertex AI Batch Prediction provisions temporary compute to score large datasets and writes results to storage, while Gemini Enterprise Agent Platform, Cloud Run, and Google Kubernetes Engine (GKE) serve live requests behind autoscaled endpoints. Batch optimizes for throughput and cost per prediction, and online optimizes for latency, availability, and accelerator obtainability. Generative models and agents add a third pattern where a foundation model from Model Garden is deployed to a dedicated endpoint and grounded with retrieved data.

Continue with this study guide: Serving models

Exam Study Guide

Automating model retraining

An appropriate retraining policy is a controlled rule that decides what data a model relearns from, how prior learning is reused, and when a new version replaces production. The policy combines a data window with a computation mode and constrains both by label latency, feature freshness, and Cloud compute budget. The goal is sustained performance without training on incomplete labels, stale features, or unbounded cost.

Continue with this study guide: Automating model retraining

Developing end-to-end ML pipelines

Validating data and models is the practice of proving that input data is correct and that a model is accurate, fair, and ready for production load. Vertex AI Model Evaluation runs evaluations alone or as a pipeline component, compares model versions on defined metrics and datasets, and logs results to Vertex ML Metadata for lineage and tracking. A model moves to production only when it meets predictive thresholds, satisfies operational limits, and performs similarly across sensitive data slices.

Continue with this study guide: Developing end-to-end ML pipelines

Exam Study Guide

Identifying risks to AI solutions

Building secure AI systems is the layered defense that stops model weights, training data, and prompts from leaving authorized boundaries or being manipulated by attacker text. The defense combines network perimeters, private connectivity, least-privilege identity, encryption, audit logging, data de-identification, and prompt screening. Traffic flows from users and pipelines through enforcement points to VPC Service Controls perimeters, identity checks, and model screening before it reaches Vertex AI endpoints and data stores.

Continue with this study guide: Identifying risks to AI solutions

Monitoring, testing, and troubleshooting AI solutions

Continuous evaluation on the Gemini Enterprise Agent Platform is the automated system that samples live serving traffic and scores it against baselines to detect drift and protect production reliability. Vertex AI Model Monitoring compares request-response payloads from an Endpoint against training and production baselines, evaluates quantitative thresholds, and exports violations to Cloud Monitoring and Pub/Sub for response. This closed loop turns statistical change into an operational incident before accuracy collapses.

Continue with this study guide: Monitoring, testing, and troubleshooting AI solutions

About the Professional Machine Learning Engineer exam

Professional Machine Learning Engineer exam domains

Exam Study Guide

Professional Machine Learning Engineer: Google Cloud Certification

About the Professional Machine Learning Engineer exam

Professional Machine Learning Engineer at a glance

Professional Machine Learning Engineer exam domains

Developing ML models using BigQuery ML or AutoML on Gemini Enterprise Agent Platform

Building AI solutions using Google Cloud AI APIs or foundational models

Tracking and running ML experiments

Model prototyping using notebooks (e.g., Gemini Enterprise Agent Platform Workbench and Colab Enterprise)

Exploring and preprocessing data for ML

Building models given the task considering cost, complexity, latency, and scalability

Choosing appropriate hardware for training

Training models

Scaling online model serving

Serving models

Automating model retraining

Developing end-to-end ML pipelines

Identifying risks to AI solutions

Monitoring, testing, and troubleshooting AI solutions

Professional Machine Learning Engineer: Google Cloud Certification

About the Professional Machine Learning Engineer exam

Professional Machine Learning Engineer at a glance

Professional Machine Learning Engineer exam domains

Developing ML models using BigQuery ML or AutoML on Gemini Enterprise Agent Platform

Building AI solutions using Google Cloud AI APIs or foundational models

Tracking and running ML experiments

Model prototyping using notebooks (e.g., Gemini Enterprise Agent Platform Workbench and Colab Enterprise)

Exploring and preprocessing data for ML

Building models given the task considering cost, complexity, latency, and scalability

Choosing appropriate hardware for training

Training models

Scaling online model serving

Serving models

Automating model retraining

Developing end-to-end ML pipelines

Identifying risks to AI solutions

Monitoring, testing, and troubleshooting AI solutions

Professional Machine Learning Engineer: Google Cloud Certification

About the Professional Machine Learning Engineer exam

Professional Machine Learning Engineer at a glance

Professional Machine Learning Engineer exam domains

1Architecting low-code AI solutions~13%

1.1Developing ML models using BigQuery ML or AutoML on Gemini Enterprise Agent Platform

1.2Building AI solutions using Google Cloud AI APIs or foundational models

2Collaborating within and across teams to manage data and models~16%

2.1Tracking and running ML experiments

2.2Model prototyping using notebooks (e.g., Gemini Enterprise Agent Platform Workbench and Colab Enterprise)

2.3Exploring and preprocessing data for ML

3Scaling prototypes into ML models~21%

3.1Building models given the task considering cost, complexity, latency, and scalability

3.2Choosing appropriate hardware for training

3.3Training models

4Serving and scaling models~20%

4.1Scaling online model serving

4.2Serving models

5Automating and orchestrating ML pipelines~18%

5.1Automating model retraining

5.2Developing end-to-end ML pipelines

6Monitoring AI solutions~13%

6.1Identifying risks to AI solutions

6.2Monitoring, testing, and troubleshooting AI solutions

Professional Machine Learning Engineer: Google Cloud Certification

About the Professional Machine Learning Engineer exam

Professional Machine Learning Engineer at a glance

Professional Machine Learning Engineer exam domains

1Architecting low-code AI solutions~13%

1.1Developing ML models using BigQuery ML or AutoML on Gemini Enterprise Agent Platform

1.2Building AI solutions using Google Cloud AI APIs or foundational models

2Collaborating within and across teams to manage data and models~16%

2.1Tracking and running ML experiments

2.2Model prototyping using notebooks (e.g., Gemini Enterprise Agent Platform Workbench and Colab Enterprise)

2.3Exploring and preprocessing data for ML

3Scaling prototypes into ML models~21%

3.1Building models given the task considering cost, complexity, latency, and scalability

3.2Choosing appropriate hardware for training

3.3Training models

4Serving and scaling models~20%

4.1Scaling online model serving

4.2Serving models

5Automating and orchestrating ML pipelines~18%

5.1Automating model retraining

5.2Developing end-to-end ML pipelines

6Monitoring AI solutions~13%

6.1Identifying risks to AI solutions

6.2Monitoring, testing, and troubleshooting AI solutions

Developing ML models using BigQuery ML or AutoML on Gemini Enterprise Agent Platform

Building AI solutions using Google Cloud AI APIs or foundational models

Tracking and running ML experiments

Model prototyping using notebooks (e.g., Gemini Enterprise Agent Platform Workbench and Colab Enterprise)

Exploring and preprocessing data for ML

Building models given the task considering cost, complexity, latency, and scalability

Choosing appropriate hardware for training

Training models

Scaling online model serving

Serving models

Automating model retraining

Developing end-to-end ML pipelines

Identifying risks to AI solutions

Monitoring, testing, and troubleshooting AI solutions

Developing ML models using BigQuery ML or AutoML on Gemini Enterprise Agent Platform

Building AI solutions using Google Cloud AI APIs or foundational models

Tracking and running ML experiments

Model prototyping using notebooks (e.g., Gemini Enterprise Agent Platform Workbench and Colab Enterprise)

Exploring and preprocessing data for ML

Building models given the task considering cost, complexity, latency, and scalability

Choosing appropriate hardware for training

Training models

Scaling online model serving

Serving models

Automating model retraining

Developing end-to-end ML pipelines

Identifying risks to AI solutions

Monitoring, testing, and troubleshooting AI solutions