Study guide

3.2 Google Cloud's AI and ML Solutions

Google Cloud Digital Leader Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 How to Prepare & Use This Guide 1.3 What Changed in the August 12, 2026 Exam Update

2 Digital Transformation with Google Cloud

1.1 Why Cloud Technology Is Transforming Business 1.2 Fundamental Cloud Concepts 1.3 Cloud Computing Models and Shared Responsibility 1.4 Agentic AI, Open Standards, and Google Cloud's Differentiators

3 Exploring Data Transformation with Google Cloud

2.1 The Value of Data 2.2 Google Cloud Data Management Solutions 2.3 Making Data Useful and Accessible 2.4 Data Types, the Data Supply Chain, and Interoperability

4 Innovating with Google Cloud Artificial Intelligence

3.1 AI and ML Fundamentals 3.2 Google Cloud's AI and ML Solutions 3.3 Building and Using Google Cloud AI and ML Solutions 3.4 Gemini, the Agent Platform, and the AI Hypercomputer

5 Modernize Infrastructure and Applications with Google Cloud — Part 1

4.1 Cloud Modernization and Migration 4.2 Computing in the Cloud 4.3 Serverless Computing

6 Modernize Infrastructure and Applications with Google Cloud — Part 2

4.4 Containers in the Cloud 4.5 The Value of APIs 4.6 Hybrid and Multi-Cloud

7 Trust and Security with Google Cloud

5.1 Trust and Security in the Cloud 5.2 Google's Trusted Infrastructure 5.3 Google Cloud's Trust Principles and Compliance 5.4 Google Threat Intelligence, Security Command Center, and Google SecOps 5.5 Securing the AI Stack: AI Protection, Model Armor, and Zero Trust

8 Scaling with Google Cloud Operations

6.1 Financial Governance and Managing Cloud Costs 6.2 Operational Excellence and Reliability at Scale 6.3 Sustainability with Google Cloud 6.4 Cloud Observability, SLIs, SLOs, and the Four Golden Signals

3.2 Google Cloud's AI and ML Solutions

Key Takeaways Explain This Topic AI

Google Cloud offers a three-tier AI/ML portfolio: pre-trained APIs for off-the-shelf intelligence, AutoML for custom models without ML coding, and custom model training on Vertex AI for data-science teams

The four selection axes are speed of deployment, effort required, potential for differentiation, and required ML expertise

Pre-trained APIs are fastest and lowest-effort but offer the least differentiation because every customer uses the same model

AutoML balances moderate speed and effort with higher differentiation because models are trained on your own labeled data

Custom models on Vertex AI require the most expertise and effort but deliver the strongest competitive differentiation when you have a data-science team and unique data

Last updated: August 2026

Selecting a Google Cloud AI/ML Solution: The Three Tiers

Google Cloud organizes its AI/ML portfolio into three tiers, ordered from lowest to highest customization and effort:

Pre-trained APIs — Ready-to-use models Google has already trained on massive datasets. You call an endpoint; no training, no data labeling. Examples: Vision API, Natural Language API, Translation API, Speech-to-Text, Text-to-Speech.

AutoML — You upload your own labeled data and Google trains a custom model with AutoML's automated model-selection and hyperparameter tuning. No ML coding required; you get a model tailored to your domain.

Custom models on Vertex AI — Your data-science team writes the model code, chooses the architecture, and controls training, tuning, and deployment. Maximum control and differentiation, maximum expertise required.

The exam expects you to recognize a use case's tier and justify it along four axes.

The Four Selection Axes

Domain 3 names four decision dimensions explicitly. Memorize them.

Axis Pre-trained API AutoML Custom (Vertex AI)

Speed of deployment Fastest (call an API today) Fast (hours to days of labeling + training) Slowest (weeks to months of development)

Effort Lowest — no ML work Moderate — label data, evaluate models Highest — full ML engineering lifecycle

Differentiation Lowest — same model every customer uses Higher — model learns your data Highest — bespoke architecture and features

Required ML expertise None (developer-level) Minimal (analyst-level) Significant (data scientist / ML engineer)

A simple mnemonic: speed and low effort trade against differentiation and expertise. Pre-trained APIs win on speed/effort and lose on differentiation; custom models are the opposite.

Matching Use Cases to Tiers

The decision logic the exam tests:

Use pre-trained APIs when the task is generic and off-the-shelf intelligence is enough. Examples: extracting text from receipts (OCR via Vision API), translating a website (Translation API), detecting sentiment in support tickets (Natural Language API), transcribing call center audio (Speech-to-Text). No unique data advantage; you need results now.

Use AutoML when you have your own labeled data and a generic model underperforms, but you do not have a deep ML team. Examples: classifying your company's specific product defects from photos, tagging your specialized document types, classifying custom support categories. You differentiate on data without needing ML engineers.

Use custom models on Vertex AI when the problem is core to your competitive advantage, your data and features are unique, and you have a data-science team that can architect and tune models. Examples: a fraud model with proprietary feature engineering, a recommendation system tuned to your catalog and user behavior, a forecasting model with custom time-series logic.

Tradeoffs in Practice

A common exam pattern asks which product to choose given a scenario. The reasoning pattern:

Identify the differentiation need. Is this a commodity task (translation, OCR) or a proprietary one (your fraud signature)? Commodity → pre-trained. Proprietary → AutoML or custom.

Check the team. No ML expertise → pre-trained API or AutoML. Dedicated data scientists → custom on Vertex AI.

Check the data. Generic, no labels → pre-trained. Labeled, domain-specific → AutoML. Unique, large, with engineered features → custom.

Check the timeline. Needed this week → pre-trained. Acceptable in days/weeks → AutoML. Months available → custom.

Worked Examples

Scenario A: A bank wants to transcribe customer call audio to text for compliance. Generic speech recognition is sufficient and no in-house NLP team exists. → Speech-to-Text API (pre-trained).

Scenario B: An agricultural company has millions of labeled photos of its crop varieties and wants a classifier that distinguishes its proprietary hybrids. No ML engineers on staff. → AutoML Vision (custom model on your data, no coding).

Scenario C: A payments company has a proprietary feature pipeline, a team of ML engineers, and wants a fraud model that outperforms off-the-shelf offerings to gain competitive advantage. → Custom model on Vertex AI .

Why the Tiers Exist Together

The tiers are not a quality ranking — they are a fit ranking. A pre-trained API is the right answer when it solves the problem; building a custom model when an API would do is wasted effort. Conversely, relying on a generic API for a core differentiator cedes competitive ground. The exam rewards matching the tier to the business context, not assuming "custom is best."

Key Takeaways

Three tiers: pre-trained APIs, AutoML, custom models on Vertex AI — ordered by customization and effort.

Four axes: speed, effort, differentiation, required expertise.

Pre-trained APIs win on speed and effort, lose on differentiation.

AutoML wins on the balance — custom model on your data without ML coding.

Custom on Vertex AI wins on differentiation, demands the most expertise.

Match the tier to the use case: commodity task → API; proprietary data, no ML team → AutoML; core differentiator with data-science team → custom.