1.8 Generative Media and Models as a Service: Gemini, Imagen and Veo

Google Cloud Professional Machine Learning Engineer Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

0.1 Exam Overview, Blueprint & Certification Logistics 0.2 Study Strategy, Scenario Mechanics & 8-Week Roadmap

2 Section 1: Architecting Low-Code AI Solutions (~13%)

1.1 BigQuery ML: Model Types, SQL Syntax and In-Database Evaluation 1.2 Feature Engineering and Feature Selection in BigQuery ML 1.3 Generating Predictions with BigQuery ML 1.4 AutoML on Agent Platform: Tabular, Image, Text and Video Training 1.5 Fine-Tuning Gemini Models from BigQuery 1.6 Model Garden: Evaluating and Selecting the Right Model 1.7 Industry-Specific AI APIs: Document AI, Vision, Translate and Speech 1.8 Generative Media and Models as a Service: Gemini, Imagen and Veo 1.9 Optimizing Gemini Applications for Cost, Latency and Availability

3 Section 2: Collaborating Within and Across Teams to Manage Data and Models (~16%)

2.1 Organizing and Exploring Tabular, Text, Image and Video Data 2.2 Choosing the Preprocessing Tool: BigQuery, Dataflow, Spark and In-Memory Python 2.3 Creating and Consolidating Features in Agent Platform Feature Store 2.4 Data Privacy, PII Handling and Sensitive Information 2.5 Notebook Environments: Collaboration and Security Best Practices 2.6 Prototyping in Workbench and Colab Enterprise with PyTorch, scikit-learn and JAX 2.7 Prototyping with Model Garden Foundational and Open Models in Notebooks 2.8 Choosing the Development and Experimentation Environment 2.9 Evaluating Generative Solutions: LLM-as-a-Judge and RAG Evaluation 2.10 Experiment Tracking, Artifact Lineage and Model Registry Governance

4 Section 3: Scaling Prototypes into ML Models (~21%)

3.1 Choosing the Model Type: ARIMA, DNN, LLM and Classical Baselines 3.2 Choosing the Product: AutoML, BigQuery ML, Custom Training and Pipelines 3.3 Choosing the Deployment Strategy at Design Time 3.4 Modeling Techniques for Interpretability Requirements 3.5 Organizing Training Data on Cloud Storage and BigQuery 3.6 Ingesting Structured and Unstructured Data into Training Pipelines 3.7 Training SDKs and Services: Custom Training, Kubeflow on GKE, AutoML and Tabular Workflows 3.8 Troubleshooting ML Model Training Failures 3.9 Hyperparameter Tuning, Bayesian Optimization and Vizier 3.10 Model Evaluation Metrics, Transfer Learning and Fine-Tuning 3.11 Evaluating Compute and Accelerator Options: CPU, GPU and TPU 3.12 Distributed Training Strategies, Hardware Acceleration and Performance Optimization

5 Section 4: Serving and Scaling Models (~20%)

4.1 Batch and Online Inference: Agent Platform, Model Garden, Cloud Run and GKE 4.2 Rollout Strategies: Canary, Traffic Splitting, Shadow and Blue-Green 4.3 Tuning Models for Production: Vector Search and Model Compression 4.4 Deploying Models to Public and Private Endpoints 4.5 Choosing Serving Hardware: CPU, GPU, TPU and Edge 4.6 Scaling the Serving Backend for Throughput

6 Section 5: Automating and Orchestrating ML Pipelines (~18%)

5.1 Validating Data and Models Inside Pipelines 5.2 Agent Platform Pipelines: Kubeflow Pipelines (KFP) and TFX Architecture 5.3 Reusable Pipeline Components, Artifacts and ML Metadata Lineage 5.4 Ray on Agent Platform for Distributed Python Workloads 5.5 MLOps CI/CD Automation, Retraining Triggers and Skew Prevention

7 Section 6: Monitoring AI Solutions (~13%)

6.1 Securing AI Systems: Exfiltration, Malicious Prompting and Model Armor 6.2 Responsible AI, Explainable AI, Fairness Metrics and Model Governance 6.3 Model Monitoring: Feature Skew and Drift Detection 6.4 Operational Troubleshooting, Performance Profiling and Cost Optimization 6.5 Monitoring, Testing and Evaluating Generative AI in Production

1.8 Generative Media and Models as a Service: Gemini, Imagen and Veo

Key Takeaways Explain This Topic AI

Gemini handles multimodal understanding and text generation, Imagen generates and edits images, and Veo generates video — each with distinct tuning, latency, and billing characteristics.

Models as a service in Model Garden lets partner and open models be called through the same Agent Platform API surface, IAM model, and billing account as first-party models.

Imagen supports subject and style customization from a small set of reference images, which is the correct answer for brand-consistent image generation.

Video and image generation are long-running operations billed per generated asset or per second of output, so they belong in asynchronous workflows rather than synchronous request paths.

SynthID watermarking and safety filtering apply to generated media, and are the controls a provenance or misuse question is pointing at.

Last updated: September 2026

1.8 Generative Media and Models as a Service: Gemini, Imagen and Veo

Blueprint reference: Section 1.2, "Building solutions and tuning models for specific use cases (e.g., Gemini, Imagen, Veo, and models as a service in Model Garden)."

The exam does not ask you to write prompts. It asks you to pick the right generative family for a described business outcome and then to architect around that family's operational shape. Three of those shapes are quite different from each other.

The Three First-Party Families

Family Input Output Shape of the call Typical billing

Gemini Text, images, audio, video, PDFs Text, structured output, tool calls Synchronous, streaming supported Per input/output token

Imagen Text prompt, optional reference or mask images Images; also edit, upscale, inpaint, outpaint Short asynchronous or synchronous Per generated image

Veo Text prompt, optional conditioning image Video clips Long-running operation Per second of generated video

Gemini is the general-purpose reasoning and understanding model, and the only one of the three that natively consumes multimodal input to produce text. When a scenario says "extract fields from a scanned invoice," "answer questions about this video," or "classify this support ticket," the family is Gemini even though the input is an image or video.

Imagen produces and manipulates images. Its capabilities beyond straight text-to-image are the ones that show up in scenarios: inpainting (replace a masked region), outpainting (extend beyond the original frame), upscaling , and subject or style customization from a handful of reference images. That last one is the answer whenever the requirement is brand consistency — a specific product, mascot, or house visual style reproduced across many generated assets.

Veo generates video and behaves like a batch job. A request returns an operation handle; the client polls or receives a completion signal later. Any architecture that blocks an HTTP request on video generation is wrong.

Models as a Service

Models as a service (MaaS) means calling a partner or open model through the Agent Platform's own API surface rather than through the vendor's. The practical consequences are what the exam tests:

One IAM model. Access is granted with Google Cloud IAM rather than a separately-managed vendor API key.

One bill. Usage appears on the Google Cloud invoice, inside existing budgets and committed-spend agreements.

One network path. Traffic stays within Google Cloud's boundary rather than egressing to a third-party endpoint.

No infrastructure. Unlike deploying an open checkpoint yourself, MaaS models are managed endpoints with no accelerators to size or pay for while idle.

When a scenario complains about managing separate vendor keys, unpredictable third-party invoices, or security review of external endpoints, MaaS is the intended answer.

Tuning Across the Families

Customization means different things per family, and conflating them is a common error.

Gemini — supervised tuning on prompt/response pairs, and adapter-based tuning that produces a tuned endpoint. Teaches behaviour, format, and domain style.

Imagen — subject customization and style customization from reference images. Teaches what a thing looks like , not how to reason.

Veo — customization is primarily prompt-level and conditioning-image-level; there is no general-purpose supervised tuning workflow comparable to Gemini's.

MaaS partner models — tuning availability depends entirely on the partner; assume none unless the model card says otherwise.

• Architecting Around Long-Running Generation
• Media generation belongs in an asynchronous pattern. The reference shape: Client request
• └─> API service writes a job row (status = QUEUED) and publishes to Pub/Sub
• └─> Worker (Cloud Run) calls Imagen or Veo, receives an operation handle
• └─> Worker polls or awaits completion, writes the asset to Cloud Storage
• └─> Job row updated to READY; client notified or polls status

Three reasons this matters on the exam. First, timeouts : a synchronous HTTP request cannot wait out a video render. Second, cost control : a queue lets you apply per-user quotas and deduplicate identical requests before spending on generation. Third, retries : generation failures are common enough that idempotent job records beat naive client retries, which otherwise pay twice for the same asset.

Provenance and Safety on Generated Media

Two controls appear in governance-flavoured questions:

SynthID embeds an imperceptible watermark into generated images and video, allowing later verification that an asset was AI-generated. This is the answer to "how do we prove which assets our systems produced" and to internal misuse-detection requirements.

Safety filters screen both prompts and generated output. Configurable thresholds control blocking behaviour, and requests can be rejected at the prompt stage rather than after paying for generation.

For text-based generative applications, Model Armor adds prompt-injection and jailbreak screening on top of content safety filtering; that control is covered with the rest of Section 6.

Choosing the Family: A Fast Decision Table

• Requirement Family
• Understand or answer questions about an image, PDF, audio clip, or video Gemini

Produce marketing images that match a brand's existing product photography Imagen with subject/style customization

• Remove an object from an existing photo Imagen inpainting
• Extend a photo to a wider aspect ratio for a banner Imagen outpainting
• Generate a short promotional video clip from a script Veo
• Call a third-party frontier model on the Google Cloud bill with IAM-based access MaaS in Model Garden

Run a specific open checkpoint with weights under your control inside your VPC Self-deployed open model (not MaaS)

Exam Traps

Using Imagen to "understand" an image. Understanding is Gemini; Imagen generates and edits.

Synchronous video generation. Veo is a long-running operation.

Assuming partner models can be tuned. Check the model card.

Confusing MaaS with self-deployment. MaaS has no endpoint to size; self-deployment does.

Forgetting per-asset billing. Image and video generation is not billed per token, so token-based cost controls do not apply.