Study guide
8.2 Choosing the Product & Deployment Strategy
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
8.2 Choosing the Product & Deployment Strategy
Key Takeaways Explain This Topic AI
Google's training-method comparison lists AutoML and BigQuery ML as needing no data science expertise, while serverless training, training clusters, and Ray require you to write the training application.
Managed Training Clusters reserve dedicated high-end accelerators (such as A100 or H100 GPUs) for large, long-running training with guaranteed capacity.
Agent Platform Pipelines turns a successful product choice into a repeatable, orchestrated workflow rather than a one-off notebook run.
Batch inference fits latency-tolerant scoring of large datasets without a deployed endpoint, while online inference needs a deployed endpoint for real-time requests.
Edge deployment fits intermittent connectivity, strict on-device latency, or data that shouldn't leave the device.
Last updated: September 2026
Section 3.1 of the exam guide also asks you to choose the product (for example, Agent Platform AutoML, BigQuery ML, and Agent Platform Pipelines) and choose the deployment strategy . These are architecture decisions made before detailed training and serving design (Chapters 9-14).
Product Choice for Building the Model
Product Expertise needed Control Choose when
BigQuery ML SQL, no data science expertise required Moderate (model options, hyperparameter tuning) Data in BigQuery, standard model types, SQL team, in-warehouse scoring
Agent Platform AutoML None (codeless) Limited (budget, early stopping, objective) Image or tabular objectives, strong accuracy with minimal ML effort
Gemini / Model Garden (prompting or tuning) Prompt design, evaluation Moderate (prompts, tuning, grounding) Language, vision, multimodal, and generative tasks
Agent Platform Serverless Training (custom training) Build the training application High (any framework, loss, architecture, machine type, container) Custom models without managing infrastructure. Good for experiments and jobs that don't need guaranteed capacity
Managed Training Clusters Build the training application Highest (reserved accelerators, networking, storage) Large, long-running, high-performance training that needs guaranteed capacity and fast job start
Ray on Agent Platform Ray and Python High (head and worker nodes, custom images, GPUs) Distributed Python workloads spanning data processing, training, and tuning
Agent Platform Pipelines Component packaging (KFP) Orchestration layer on top of the above Making any of these repeatable: data prep → train → evaluate → register → deploy
Agent Platform Pipelines isn't a training algorithm. It orchestrates BigQuery ML, AutoML, custom training, and evaluation steps. Choose it when the requirement is repeatability, automation, lineage, or retraining, which is often the case once a prototype succeeds.
Decision sequence
Can a pre-trained API or Gemini solve it? That's the least effort.
Is the data structured and already in BigQuery , and does a standard model type fit? Use BigQuery ML .
Is it an image or tabular objective, and the team wants the best accuracy with no code? Use AutoML .
Does it need a custom architecture, loss, or framework ? Use custom training (serverless first, or training clusters for large reserved-capacity jobs, or Ray for Ray-based code).
Will it be retrained or promoted repeatedly ? Wrap it in Agent Platform Pipelines .
Deployment Strategy
Strategy How predictions are delivered Choose when Google Cloud options
Batch inference Score a large dataset on a schedule and write results No real-time need: nightly propensity scores, weekly forecasts Agent Platform Batch Inference (no endpoint needed), BigQuery ML ML.PREDICT , Gemini batch inference, Dataflow RunInference
Online inference Synchronous request → response User-facing apps, real-time decisions such as fraud checks Agent Platform Endpoints (public, dedicated, or private), Cloud Run, GKE
Streaming inference Score events continuously as they arrive IoT alerts, clickstream personalization Dataflow with RunInference or calls to an endpoint
In-database scoring Predictions computed where data lives Analysts consume results in SQL and BI BigQuery ML (native or imported models, remote models)
Edge Model runs on device Offline or intermittent connectivity, ultra-low latency, data that must stay on device AutoML Edge exports (TF Lite, Edge TPU, Core ML, TensorFlow.js), custom exported models
Hybrid Precompute in batch, adjust online Large catalogs with real-time context Batch candidate generation plus online re-ranking
Choosing between batch and online
Freshness needed: if predictions can be up to a day old, batch is simpler and cheaper.
Input availability: if key inputs only exist at request time (cart contents, current location), use online inference.
Cost: online endpoints bill for provisioned replicas even when idle (unless scaled down), while batch jobs bill only while running.
Volume pattern: very large volumes on a schedule strongly favor batch.
Cost Profile of Each Strategy
Strategy What you pay for Cost trap
Batch inference Compute while the job runs Running batch jobs far more often than the business needs the scores
Online endpoint Replicas (and accelerators) for as long as the model is deployed Overprovisioned minimum replicas or idle GPU endpoints
- BigQuery ML scoring Query processing Scoring full history every day instead of only new or changed rows
- Gemini API Tokens per request Sending long, unchanged context on every call without caching
- Edge Device and app distribution effort Shipping model updates too rarely, so edge models go stale
- Rollout Considerations Decided Up Front
Versioning and rollback: register every model version (Chapter 13) so traffic can move back quickly.
Safe rollout: plan a canary or A/B split on endpoints for online models.
Monitoring: decide how you'll get ground truth and when drift monitoring starts (Chapter 19).
Retraining triggers: schedule-based, performance-based, or drift-based (Chapter 17).
Worked Scenario
An insurer wants (a) a monthly customer-lapse score for its call-center campaign list, (b) instant fraud checks when a claim is submitted in the mobile app, and (c) photo damage assessment in rural areas with poor connectivity.
- Need Product Deployment strategy
- Monthly lapse scores BigQuery ML boosted tree Batch: scheduled ML.PREDICT into a campaign table
Instant fraud check Custom XGBoost via serverless custom training, orchestrated by Pipelines Online: Agent Platform endpoint with autoscaling, canary rollouts
Damage photos offline AutoML image classification (Edge model) Edge: TF Lite model in the adjuster app, synced when connected