Section 1: Architecting low-code AI solutions
Learning goals
- Choose between BigQuery ML and AutoML based on the business problem
- Meet requirements with the least effort by choosing among pretrained APIs, foundation models and Model Garden
- Optimize cost, latency and availability of Gemini apps
Key points
- BigQuery ML builds models with SQL (CREATE MODEL, ML.PREDICT, ML.EVALUATE) without moving data: ARIMA_PLUS (time series), K-means (clustering), logistic regression and boosted trees, remote models (Gemini) and more.
- The TRANSFORM clause applies preprocessing consistently at training and prediction. Check features with ML.FEATURE_IMPORTANCE and the like.
- AutoML builds high-quality models without code from labeled tabular, image, text and video data.
- First check whether pretrained APIs (Vision, Document AI, Translation, Speech) or foundation models suffice; if not, AutoML; custom training last.
- Optimizing Gemini cost and latency: choosing lighter models (such as Flash), context caching, batch inference, limiting output tokens, provisioned throughput.
Workplace uses
- AccountingExtract invoice fields with Document AI, and build demand forecasts with BigQuery ML's ARIMA_PLUS using only SQL.
Exam objectives (from the exam guide)
- BigQuery ML・Agent Platform AutoML でのモデルの作成(分類・回帰・予測・クラスタリング)、BigQuery ML での特徴量エンジニアリングと予測、BigQuery での Gemini のファインチューニング
- Model Garden からのモデルの評価と選択、業界別の API(Document AI・Vision・Translation)、Gemini・Imagen・Veo・MaaS のチューニング、Gemini のアプリのコスト・レイテンシ・可用性の最適化