The official Google Cloud Certified Professional Machine Learning Engineer syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
Developing ML models using BigQuery ML or AutoML on Gemini Enterprise Agent Platform
Pick the model type from the problem: LOGISTIC_REG, BOOSTED_TREE_* or AUTOML_CLASSIFIER to classify; LINEAR_REG or the regressors for continuous values; KMEANS to segment without labels; MATRIX_FACTORIZATION for recommendations; ARIMA_PLUS (univariate, many series with TIME_SERIES_ID_COL) or ARIMA_PLUS_XREG (with external variables) to forecast. ARIMA_PLUS is the cheap, fast baseline against AutoML neural forecasting.
BigQuery ML preprocesses automatically (mean imputation, standardization, one-hot encoding and TIMESTAMP component extraction). For your own rules use the TRANSFORM clause with functions such as ML.IMPUTER, ML.QUANTILE_BUCKETIZE or ML.FEATURE_CROSS: training statistics are reused in ML.PREDICT, avoiding training-serving skew. ML.TRANSFORM, TRANSFORM_ONLY models, ML.FEATURE_IMPORTANCE and ML.GLOBAL_EXPLAIN help inspect and select features.
Manual feature preprocessing ↗Automatic feature preprocessing ↗
ML.PREDICT scores tables or queries in batch inside BigQuery without moving data, accepts THRESHOLD for binary models and applies the TRANSFORM clause automatically. ARIMA_PLUS uses ML.FORECAST, ML.EXPLAIN_PREDICT adds per-row attributions and ML.RECOMMEND serves matrix factorization. For online inference, register the model in Model Registry and deploy it to an endpoint; imported ONNX and remote models also use ML.PREDICT.
The ML.PREDICT function ↗Manage BigQuery ML models in Gemini Enterprise Agent Platform ↗
AutoML splits tabular data into training, validation and test sets: random 80/10/10 by default, chronological with a Time column for time-dependent data, or manual to segregate, for example, stores. Pick the objective from the problem (AUC PR for the rare class, log loss required for multi-class), use a weight column for important rows and Tabular Workflows when you need control over each step.
Data splits for tabular data ↗Train a classification or regression model ↗
Supervised tuning of Gemini from BigQuery uses CREATE MODEL ... REMOTE WITH CONNECTION, OPTIONS(ENDPOINT = ...) and an AS SELECT clause with prompt and label columns (or PROMPT_COL and INPUT_LABEL_COLS). MAX_ITERATIONS is converted to epochs, DATA_SPLIT_METHOD holds out evaluation data for early stopping, and ML.EVALUATE compares the baseline with the tuned model. Tune when prompting is not enough and you have labeled examples.
The CREATE MODEL statement for fine-tuning Gemini models ↗Use tuning and evaluation to improve model performance ↗
Building AI solutions using Google Cloud AI APIs or foundational models
Model Garden gathers foundation, fine-tunable and task-specific models from Google, partners and open sources. Use MaaS for prototyping, variable traffic and minimal operations; self-deploy for custom weights, predictable high volume, hardware control or rules that forbid multi-tenant services. Compare candidates with the Gen AI evaluation service on your data, restrict models with an organization policy and review models flagged as suspicious.
Document AI works through processors: Enterprise Document OCR to digitize, Form Parser, Layout Parser, Custom Extractor and pretrained parsers (invoices, expenses) to extract, and Custom Classifier or Custom Splitter to classify. Vision API offers OCR, labels, logos, objects and SafeSearch. Cloud Translation Advanced adds glossaries, adaptive translation and document translation that preserves formatting.
Start with prompting and tune only when it is not enough: supervised fine-tuning fits formatting, classification or extraction with hundreds of examples; preference tuning fits chosen/rejected pairs after a supervised step; reinforcement learning fine-tuning fits verifiable reasoning. Model Garden offers open models as a serverless managed API (MaaS) or self-deployed in your project; Veo generates video.
Context caching cuts cost and latency for repeated content: implicit caching is automatic (put common content first) and explicit caching guarantees the discount and controls expiration. Batch inference suits non-urgent jobs. Provisioned Throughput reserves capacity at a fixed cost; Priority PayGo adds consistency without commitment; the global endpoint improves availability but does not guarantee data residency.