Study guide
3.2 Building with Document AI, Vision, Translation & Other AI APIs
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
3.2 Building with Document AI, Vision, Translation & Other AI APIs
Key Takeaways Explain This Topic AI
Document AI processors fall into three categories: digitize (OCR), extract (custom extractor, Form Parser, Layout Parser, pretrained parsers), and classify (custom classifier and custom splitter).
Document AI Layout Parser extracts text, tables, and lists and creates context-aware chunks for retrieval in gen AI applications.
Vision API DOCUMENT_TEXT_DETECTION handles dense text and handwriting and takes precedence over TEXT_DETECTION when both are requested.
Cloud Translation Advanced adds glossaries, batch and document translation, the Translation LLM, and Adaptive Translation beyond the Basic API's standard NMT model.
Google deprecated the Video Intelligence API on September 14, 2026 and plans to shut it down on September 14, 2027.
Last updated: September 2026
Section 1.2 of the exam guide expects you to build applications with industry-specific APIs such as the Document AI API, Vision API, and Translation API. These APIs are the lowest-effort way to add AI: no training data, no model hosting, and results through a REST call or client library. Your job on the exam is to spot when a task matches one of these APIs, and when it needs customization or a foundation model instead.
Document AI
Document AI turns unstructured documents (PDFs, scans, images) into structured data. You create a processor in your project and send documents to it.
- Category Processor Use it for
- Digitize Enterprise Document OCR Text and layout from scans, with image-quality detection and deskewing
- Extract Form Parser Key-value pairs and tables from generic forms
- Extract Layout Parser Text, tables, and lists with context-aware chunks for RAG and search
Extract Custom Extractor Your own fields, using generative AI or custom models. It can be fine-tuned on your documents
Extract Pretrained parsers Invoice, Expense, Bank Statement, Pay Slip, W2, US Driver License, Identity Document Proofing
- Classify Custom Classifier Routing documents by type (claim form vs. medical record)
- Classify Custom Splitter Splitting one PDF that holds several documents
Pretrained parsers return normalized fields, such as dates and amounts in standard formats, which you can load straight into BigQuery. Document AI also supports dataset management, auto-labeling, and review workflows to improve custom processors.
Scenario: An insurer receives 50,000 mixed PDFs a day, each bundling a claim form, an invoice, and photos of damage. A good design uses Custom Splitter → Custom Classifier → Invoice Parser for invoices and Custom Extractor for claim fields, then writes to BigQuery. Documents with low confidence go to a human review step.
Vision API
The Vision API analyzes images with pre-trained models:
- Feature Output
- LABEL_DETECTION General labels ("dog", "beach") with confidence scores
- OBJECT_LOCALIZATION Multiple objects with bounding boxes
- TEXT_DETECTION OCR for sparse text in photos (signs, packaging)
DOCUMENT_TEXT_DETECTION OCR for dense text, handwriting, and PDF/TIFF files. Wins if both OCR features are requested
- FACE_DETECTION Faces and attributes (not identity recognition)
- LANDMARK_DETECTION , LOGO_DETECTION Known landmarks and brand logos
- SAFE_SEARCH_DETECTION Explicit content likelihoods for moderation
- IMAGE_PROPERTIES , CROP_HINTS , WEB_DETECTION Dominant colors, crop suggestions, web matches
If your labels are specific to your business (for example, "cracked weld" vs. "acceptable weld"), general Vision labels won't be enough. Train an AutoML image model, or use a Gemini multimodal model with examples. For scanned business documents, Google recommends Document AI over Vision OCR because it adds structure and entity extraction.
Cloud Translation
- Edition Capabilities
- Basic Plug-and-play Neural Machine Translation (NMT) for text
Advanced NMT plus the Translation LLM (TLLM) , glossaries (fixed translations for brand and domain terms), batch and document translation (preserving formatting), custom models, and Adaptive Translation , which matches your style from a small set of example translation pairs
Pick glossaries when product names or regulated terms must always translate the same way. Pick Adaptive Translation or model customization when tone and domain style matter. Use document translation for DOCX/PDF files whose formatting must be preserved.
Speech and Language APIs
Speech-to-Text transcribes audio with Chirp-family models, including telephony-tuned variants for call-center audio.
Text-to-Speech generates natural voices for IVR and accessibility.
Natural Language API provides sentiment, entity, and entity-sentiment analysis, syntax analysis, and content classification.
Video: A Deprecation to Watch
Google deprecated the Video Intelligence API on September 14, 2026 , with shutdown planned for September 14, 2027. For new video labeling, summarization, or moderation designs, plan on Gemini video understanding on Agent Platform.
API vs. Foundation Model vs. Custom Model
Question to ask If yes...
Does a pre-trained API already produce exactly the needed output (invoice fields, OCR, translation)? Use the API. It's the fastest, cheapest, and lowest-overhead choice
Is the task open-ended, like summarizing, reasoning across a document, or answering questions? Use Gemini through Agent Platform, optionally with Layout Parser chunks for grounding
Are the labels unique to your business and do you have labeled examples? AutoML (image or tabular), a Document AI custom processor, or Gemini tuning
- Do you need a custom architecture or strict control over the model? Custom training
- Worked Comparison: Three Ways to Read a Receipt
An expense app needs merchant, date, total, and tax from photographed receipts.
Approach What you get Trade-off
Vision API DOCUMENT_TEXT_DETECTION Raw text in a page, block, paragraph, word hierarchy You still write and maintain parsing rules for every receipt layout
Document AI Expense Parser Labeled, normalized fields (supplier, date, total, tax) with confidence scores Limited to the fields the parser defines. Use a Custom Extractor for extra fields
Gemini with a response schema Flexible structured JSON, including fields no parser defines You own prompt design, evaluation, and monitoring for extraction accuracy
For a standard document type, the pretrained parser is usually the best exam answer: it needs the least engineering and returns structured, normalized output. Gemini is a better fit when the documents are too varied for fixed processors or when the task goes beyond extraction, such as explaining a policy exception.
Production Design Considerations
Batch vs. online: Document AI and Translation both offer batch methods for large volumes from Cloud Storage. Use online calls for interactive apps.
Quotas: retry with exponential backoff when you exceed quota. For high-volume pipelines, spread requests over time and check quota limits before you launch.
Data governance: keep processors in regions that meet residency rules, and restrict access with IAM and VPC Service Controls (Chapter 18).
Human in the loop: send low-confidence extractions to reviewers rather than writing them straight to systems of record.
Composition: real solutions chain APIs. For example, Speech-to-Text transcribes calls, Translation normalizes the language, and Gemini summarizes and categorizes the result.