Study guide
3.1 Training Models with Agent Platform AutoML
Google Cloud Professional Machine Learning Engineer PMLE
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & the Agent Platform Map
1.1 PMLE Exam Facts, Policies & the June 2026 Blueprint 1.2 From Vertex AI to Gemini Enterprise Agent Platform: The Product Name Map
2 Chapter 2: Low-Code ML with BigQuery ML
2.1 Choosing, Training & Predicting with BigQuery ML Models 2.2 Feature Engineering & Feature Selection in BigQuery ML 2.3 Fine-Tuning & Evaluating Gemini Models from BigQuery
3 Chapter 3: AutoML & Google Cloud AI APIs
3.1 Training Models with Agent Platform AutoML 3.2 Building with Document AI, Vision, Translation & Other AI APIs
4 Chapter 4: Foundation Models in Model Garden
4.1 Evaluating & Selecting Models in Model Garden 4.2 Building & Tuning Solutions with Gemini, Imagen, Veo & MaaS 4.3 Optimizing Gemini Applications for Cost, Latency & Availability
5 Chapter 5: Exploring, Preprocessing & Protecting Data
5.1 Organizing & Exploring Tabular, Text & Image Data 5.2 Choosing a Preprocessing Tool: BigQuery, Dataflow, Spark or Python 5.3 Creating & Consolidating Features in Agent Platform Feature Store 5.4 Protecting PII & Sensitive Data in ML Workflows
6 Chapter 6: Notebooks, Prototyping & Experiment Tracking
6.1 Workbench vs. Colab Enterprise: Secure, Collaborative Notebooks 6.2 Prototyping with PyTorch, scikit-learn, JAX & Model Garden in Notebooks 6.3 Experiment Environments, Tracking & Lineage with Experiments and ML Metadata
7 Chapter 7: Evaluating Predictive & Generative AI Solutions
7.1 Evaluation Metrics for Predictive Models 7.2 Evaluating Gen AI: Computation Metrics, Rubrics & LLM-as-a-Judge
8 Chapter 8: Choosing the Modeling Approach
8.1 Choosing the Model Type: ARIMA, Trees, DNNs & LLMs 8.2 Choosing the Product & Deployment Strategy 8.3 Modeling Techniques for Interpretability Requirements
9 Chapter 9: Training Data & Training SDKs
9.1 Organizing & Ingesting Training Data from Cloud Storage & BigQuery 9.2 Custom Training on Agent Platform: Containers, Jobs & Worker Pools 9.3 Kubeflow on GKE, AutoML & Tabular Workflows as Training Choices
10 Chapter 10: Troubleshooting, Hyperparameter Tuning & Fine-Tuning
10.1 Troubleshooting ML Training Failures 10.2 Hyperparameter Tuning on Agent Platform 10.3 Fine-Tuning Foundation Models & When to Tune
11 Chapter 11: Training Hardware & Distributed Training
11.1 Choosing CPUs, GPUs & TPUs for Training 11.2 Distributed Training: Data & Model Parallelism
12 Chapter 12: Deploying Models for Inference
12.1 Batch vs. Online Inference on Agent Platform 12.2 Serving Beyond Agent Platform Endpoints: Model Garden, Cloud Run & GKE 12.3 Prebuilt & Custom Serving Containers
13 Chapter 13: Model Versions, Rollouts & Inference Logic
13.1 Organizing & Versioning Models in Model Registry 13.2 Rollout Strategies: A/B Tests, Canaries & Traffic Splits 13.3 Inference Preprocessing & Postprocessing
14 Chapter 14: Scaling Online Serving
14.1 Serving Features Online with Feature Store 14.2 Public, Dedicated & Private Endpoints 14.3 Serving Hardware & Autoscaling for Throughput 14.4 Tuning Models for Production Training & Serving
15 Chapter 15: End-to-End ML Pipelines
15.1 Validating Data & Models in Pipelines 15.2 Agent Platform Pipelines with KFP: Components, Templates & Caching 15.3 Ensuring Consistent Preprocessing Between Training & Serving
16 Chapter 16: Orchestration with Managed Airflow & Ray
16.1 Orchestrating ML Workflows with Managed Service for Apache Airflow 16.2 Ray on Agent Platform for Distributed ML Workloads
17 Chapter 17: Automating Retraining & CI/CD/CT
17.1 Choosing a Retraining Policy 17.2 CI/CD/CT for ML with Cloud Build
18 Chapter 18: Securing AI Systems, Responsible AI & Explainability
18.1 Protecting AI Systems from Data & Model Exfiltration 18.2 Defending Gen AI Apps: Safety Filters, Model Armor & Regex Guardrails 18.3 Responsible AI: Detecting & Monitoring Bias 18.4 Model Explainability on Agent Platform
19 Chapter 19: Monitoring AI Solutions
19.1 Configuring Model Monitoring on Agent Platform 19.2 Training-Serving Skew, Data Drift, Concept Drift & Attribution Drift 19.3 Monitoring, Testing & Evaluating Gen AI Solutions in Production
3.1 Training Models with Agent Platform AutoML
Key Takeaways Explain This Topic AI
Agent Platform AutoML supports image classification, image object detection, tabular classification and regression, and tabular forecasting.
AutoML tabular datasets need 1,000 to 100,000,000 rows, 2 to 1,000 columns, and no more than 100 GB of data.
By default, AutoML tabular training randomly assigns 80% of rows to training, 10% to validation, and 10% to test.
AUC ROC is the default optimization objective for binary classification, log loss is the only objective for multi-class classification, and RMSE is the default for regression.
Google recommends about 1,000 training images per label for AutoML image classification, with a minimum of 10.
Last updated: September 2026
AutoML on Agent Platform trains models without model code. You prepare labeled data, create a managed dataset , pick an objective, set a training budget, and AutoML handles preprocessing, architecture search, hyperparameter tuning, and ensembling. The exam tests whether AutoML fits the scenario and which settings matter.
What AutoML Supports Today
- Data type Objectives
- Image Classification (single-label or multi-label), object detection
- Tabular Classification and regression, forecasting
AutoML Text and AutoML Video are retired. For text classification, entity extraction, sentiment, or video understanding, the current low-code answer is a Gemini model with prompting, plus supervised tuning if needed (Chapter 4).
The AutoML Workflow
Prepare training data that looks like production data.
Create a managed dataset from BigQuery or CSV (tabular) or from image files in Cloud Storage with an import file (JSON Lines or CSV).
Train by choosing the objective, target column or labels, data split, optimization objective, and budget.
Evaluate the metrics AutoML produces on the test split.
Get inferences online (deploy to an endpoint) or in batch (no endpoint needed).
Interpret results , for example with feature importance for tabular models.
Tabular Data Requirements
- Requirement Classification and regression
- Size 100 GB or smaller
- Columns At least 2 and at most 1,000 (target plus at least one feature)
- Rows At least 1,000 and at most 100,000,000
- Target Required. No null values. Categorical or numerical
- Sources BigQuery table or view ( bq://project.dataset.table ), or CSV files (each ≤10 GB, ≤100 GB total)
- Row weights Optional numeric weight column, 0-10,000
If the BigQuery table or Cloud Storage bucket is in a different project, grant the Agent Platform Service Agent access to it.
Data splits
By default, AutoML randomly assigns 80% / 10% / 10% of rows to training, validation, and test. The split is deterministic, so retraining on the same data gives the same split. Change the default when:
Data is time-sensitive (and you aren't forecasting): use a chronological split on a time column so the test set holds the most recent rows.
Production will score unseen groups (such as new stores): use a manual split column with TRAIN , VALIDATE , and TEST values so no group appears in more than one split.
Classes are imbalanced : AutoML doesn't stratify, so make sure the test split has enough minority examples.
AutoML uses the validation split to steer trials. It then reports final metrics from a model trained on training + validation and scored on test. The model you serve is trained on all three splits so it uses as much data as possible.
Optimization objectives
- Model type Objective (API value) Choose it when
- Binary classification AUC ROC ( maximize-au-roc ), default You need good separation between classes
- Binary classification AUC PR ( maximize-au-prc ) The positive class is rare and matters most
Binary classification Precision at recall / Recall at precision The business fixes one metric (for example, "at least 90% recall")
Classification (any) Log loss ( minimize-log-loss ) You need well-calibrated probabilities. It is the only objective for multi-class
- Regression RMSE ( minimize-rmse ), default Large errors should be penalized heavily
- Regression MAE ( minimize-mae ) Outliers should have less influence
- Regression RMSLE ( minimize-rmsle ) Relative error matters and values span a wide range
The training budget is set in milli node hours (1,000 milli node hours = 1 node hour). Early stopping ends training once more trials stop helping.
Forecasting with AutoML
AutoML forecasting uses neural network training methods: TiDE (Time series Dense Encoder), Temporal Fusion Transformer (TFT) , AutoML (L2L) , and Seq2Seq+ . Key settings:
Time column and time series identifier column (for example, sku_id ).
Data granularity (for example, daily), plus optional holiday regions for holiday effects (daily granularity).
Forecast horizon: how far ahead to predict. Context window: how far back the model looks. Both are counted in units of granularity.
Covariates: columns available at forecast time (planned promotions, holidays, price) versus unavailable at forecast time (actual weather, competitor sales).
Hierarchical forecasting to keep forecasts consistent across groups (for example, SKU, store, and region totals).
For a fast statistical baseline, BigQuery ML ARIMA_PLUS trains much faster than neural forecasting. Tabular Workflow for Forecasting exposes every pipeline step when you need more control (Chapter 9).
Image Data Requirements
Training formats: JPEG, GIF, PNG, BMP, ICO, up to 30 MB per image. Prediction formats: JPEG, GIF, PNG, WEBP, BMP, TIFF, ICO, up to 1.5 MB, sent base64-encoded.
Classification: Google recommends about 1,000 images per label , with a minimum of 10 . Keep the most common label at most 100× more frequent than the least common, and consider a None_of_the_above label.
Object detection: at least 10 annotated images per label, with bounding boxes at least 0.01 × the image side length. Google recommends about 1,000 annotations per label.
Grant the Agent Platform Service Agent Storage Object Viewer on the source bucket.
Make training images match production conditions. Blurry security-camera frames call for blurry training images.
Cloud vs. edge image models
Cloud models are served on Agent Platform endpoints. Edge models run on devices and come in variants tuned for low latency ( MOBILE_TF_LOW_LATENCY_1 ), general purpose ( MOBILE_TF_VERSATILE_1 ), and higher accuracy ( MOBILE_TF_HIGH_ACCURACY_1 ). You can export edge models as TF Lite , Edge TPU TF Lite , a container (TF SavedModel), Core ML (iOS/macOS), or TensorFlow.js . Choose edge when the device has intermittent connectivity or needs on-device latency.
AutoML vs. BigQuery ML vs. Custom Training
- Situation Best fit
- Tabular data in BigQuery, SQL team, standard model, batch scoring BigQuery ML
- Tabular or image data, little ML expertise, want strong accuracy with no model code Agent Platform AutoML
- Custom architecture, custom loss, specific framework, or unsupported objective Custom training (Chapter 9)
- Text or video understanding Gemini prompting and tuning, not AutoML