Google Vertex AI & Gemini Study Guide — AI Intermediate

22% of the exam · domain 2 of 5 · AI Intermediate · Free Google Vertex AI & Gemini practice questions

0 of 50 topics covered
What the exam asks here — tap to tick off0 / 10 covered
Domain 2 of 5

Google Vertex AI & Gemini

This domain covers 22% of the ai-intermediate exam and tests your ability to select, configure, and operate Google Cloud's production AI stack. Questions range from choosing the right Vertex AI service for a given architecture requirement, to knowing exact API behaviors, IAM roles, evaluation methods, and tuning strategies. Expect scenario-based questions where two answers seem plausible — success depends on knowing precise service distinctions, default behaviors, and when one approach is strictly preferred over another.


Vertex AI Overview: Model Garden, Workbench, Pipelines, Matching Engine

Vertex AI is Google Cloud's unified ML platform. It consolidates model serving, training, pipelines, and vector search under a single API surface and IAM boundary.

ComponentPurposeKey Detail
Model GardenBrowse, deploy, and tune 100+ foundation modelsIncludes Google, open-source (Llama, Mistral), and third-party models
WorkbenchManaged JupyterLab notebooksTwo modes: Instances (user-managed) and Managed Notebooks (auto-managed)
PipelinesOrchestrate ML workflowsBased on Kubeflow Pipelines (KFP) v2 SDK
Matching EngineApproximate nearest neighbor (ANN) vector searchSupports dot-product, cosine, L2 distance; index types: TreeAH, Brute Force
Feature StoreServe and share ML featuresBatch and online serving
Model RegistryVersion and track trained modelsLinks to Endpoints for deployment

Matching Engine specifics the exam tests:

  • Index creation is separate from IndexEndpoint deployment — you create the index, then deploy it to an endpoint.
  • Supports streaming updates (upsert/delete without full rebuild) and batch updates.
  • TreeAH (Tree + Asymmetric Hashing) is the default for large-scale ANN; Brute Force is exact search for small datasets or ground-truth evaluation.
  • Distance measures: DOT_PRODUCT_DISTANCE, COSINE_DISTANCE, SQUARED_L2_DISTANCE, L1_DISTANCE, MANHATTAN_DISTANCE.

Common traps:

  • Confusing Matching Engine with Vertex AI Vector Search — they are the same product (Vector Search is the current product name; Matching Engine was the original name).
  • Thinking Workbench Managed Notebooks require manual kernel management — they do not; Google manages the underlying infrastructure.
  • Assuming Model Garden only hosts Google models — it hosts open-source and partner models too.

Gemini on Vertex AI: Models, Versions, and Context Caching

Gemini is Google's multimodal model family, available on Vertex AI under the google publisher in Model Garden.

ModelBest ForContext WindowKey Capability
gemini-1.5-proComplex reasoning, long documentsUp to 2M tokensBest quality, higher latency/cost
gemini-1.5-flashHigh-volume, low-latency tasksUp to 1M tokensFaster and cheaper than Pro
gemini-2.0-flashNext-gen speed + multimodalUp to 1M tokensTool use, real-time streams, image generation
gemini-2.0-proFrontier reasoningUp to 2M tokensBest coding/reasoning in 2.0 family

Context Caching:

  • Context caching stores a portion of the prompt (system instructions, large documents) server-side, so repeated calls don't re-process the same tokens.
  • Available for gemini-1.5-pro and gemini-1.5-flash.
  • Minimum cacheable token count: 32,768 tokens.
  • Cache has a configurable TTL (time-to-live); default is 1 hour, max is unspecified but configurable.
  • Billed at a reduced input token rate for cache hits; cached tokens cost less than uncached.
  • Use case: RAG pipelines where the same large document corpus is queried repeatedly.

Common traps:

  • Assuming context caching eliminates output token costs — it only reduces input token cost for the cached portion.
  • Confusing context window size with context caching — context window is the max tokens per call; caching is about reusing tokens across calls.
  • Choosing gemini-1.5-pro when cost/latency is the primary constraint — flash is the correct answer for high-throughput, cost-sensitive workloads.

Worked scenario: A customer service platform queries the same 500-page product manual with every user request. The correct architecture uses gemini-1.5-flash with context caching on the product manual, reducing per-request token cost while maintaining low latency.


Unlock with a paid plan

11 more sections (about 2,845 words) continue below. Every paid plan unlocks all AI Intermediate study guides, the full question bank and mock exams, from $4.97/month.