Building, fitting, and scoring a model with SQL alone
BigQuery ML lets you create, train, and evaluate machine learning models directly in BigQuery using standard SQL, eliminating the need to export data to a separate ML platform. Models are created with CREATE MODEL statements, trained on data via SELECT queries, and evaluated using built-in functions like ML.EVALUATE. This keeps data, training, and prediction all within BigQuery's serverless environment.
Must-know
- The CREATE MODEL statement defines the model type via OPTIONS (e.g.,
model_type='linear_reg', 'logistic_reg', 'kmeans', 'boosted_tree_classifier') and specifies the label column for supervised models. - Training data is supplied via the AS SELECT clause of CREATE MODEL, so any query result (joins, filters, transformations) can become training input.
- ML.EVALUATE returns model-specific metrics (e.g., precision, recall, ROC AUC for classification; RMSE, R² for regression) and can be run against a held-out evaluation set or the training data if none is specified.
- ML.PREDICT is used to generate predictions on new data using a trained model, returning predicted labels/values alongside input features.
- BigQuery ML automatically splits data into training and evaluation sets when no explicit split is provided, but you can control this via options like
DATA_SPLIT_METHOD. - Model training and prediction incur BigQuery processing costs based on bytes processed (or flat-rate slots), and some model types (e.g., DNN, boosted trees, AutoML-backed models) may have different pricing or resource behavior than simple linear/logistic models.
A data analyst at a retail company wants to use BigQuery ML to predict whether a customer will cancel their subscription (a binary outcome: yes or no) based on historical account activity stored in a BigQuery table. Which model_type should the analyst specify in the CREATE MODEL statement?
What you have tried across GCP ADP's objectives, not a readiness score.
Data Preparation and Ingestion
- When to load first and when to transform first, and what sits between the two
- Picking a way to move existing data into Google Cloud
- Judging whether a dataset is trustworthy enough to build on
- Fixing messy records before they reach a report
- Telling CSV, JSON, Parquet, Avro, and relational tables apart, and where each fits
- Picking how to pull data out of a source system
- Matching a workload to the right storage or database service
- Getting files and tables loaded with a CLI, a transfer service, or a client library
Data Analysis and Presentation
- Writing BigQuery SQL that answers a reporting question
- Exploring and charting data inside a hosted notebook
- Turning a question from the business into an analysis that settles it
- Building a dashboard and getting it in front of the right people
- Deciding whether a job calls for Looker or for Looker Studio
- Editing LookML to change what a model exposes
- Spotting a problem worth solving with BigQuery ML or AutoML
- Calling a hosted Google language model straight from BigQuery
- Sequencing a machine learning project from raw data to served predictions
- Building, fitting, and scoring a model with SQL alone
- Running predictions against a model you already trained
- Keeping trained models catalogued in one place
Data Pipeline Orchestration
- Matching a transformation job to Dataproc, Dataflow, Dataform, or a managed alternative
- Weighing whether the transform belongs before or after the load
- Assembling the services a simple transformation pipeline needs
- Putting a query on a schedule and keeping it running
- Watching a Dataflow job and spotting where it stalls
- Reading logs and metrics to work out what a pipeline actually did
- Choosing what should drive a multi-step workflow
- Streaming messages into BigQuery as they arrive rather than in batches
- Wiring a trigger so one event starts the next step
Data Management
- Granting only the access a person or service actually needs
- Controlling who can read a bucket, and what uniform access changes
- Sharing a dataset with another team or company without copying it
- Matching a storage class to how often the data gets read
- Expiring old data automatically so it stops costing money
- Picking somewhere to park data that must be kept but is rarely read
- Comparing the managed backup and restore options across services
- Working out when a second copy is worth what it costs
- Regions, dual-regions, multi-regions, and zones as redundancy choices
- Deciding who should hold the encryption keys
- What a key management service does for creating, rotating, and revoking keys
- Protecting data on the wire versus data sitting on a disk
Coverage checked against the published exam guide on Aug 12, 2026.
These are independent practice questions, written against this certification's published exam guide. They are not the certification vendor's own questions, and not the real exam.