Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  BigQuery ML — train a custom language model on company policy documents.

  Why it's wrong here

  BigQuery ML is incorrect because it is designed for traditional machine learning on structured, tabular data—like regression, classification, or time-series forecasting—using SQL queries. It does not support fine-tuning or training large language models from unstructured documents, and building a conversational AI assistant requires a transformer-based model and retrieval infrastructure, not a SQL-queryable ML service. Even custom models in BigQuery ML rely on tables and numeric features, not document text to be indexed and retrieved for grounded generation.

• ✓

  Vertex AI Agent Builder with Gemini and document-grounded search (RAG).

  Why this is correct

  Vertex AI Agent Builder is correct because it provides pre-built RAG (Retrieval-Augmented Generation) pipelines: you can ingest policy documents from sources like Google Drive or Cloud Storage, index them for semantic retrieval, and ground Gemini's responses in that private document content. This eliminates the need for ML expertise or custom model training while ensuring answers are factually tied to your policies, reducing hallucination. The service handles document chunking, vector search, and LLM orchestration out of the box, making it the ideal low-code solution for building a document Q&A assistant.

• ✗

  Cloud Natural Language API — it reads and summarizes documents automatically.

  Why it's wrong here

  Cloud Natural Language API is incorrect because it provides pre-trained analysis functions like entity extraction, sentiment analysis, and syntax parsing, not conversational AI or document retrieval. While it can inspect and label text, it cannot generate answers to new questions or fetch relevant snippets from a document corpus to support a chat interface. It also lacks the generative capabilities of Gemini needed to synthesize coherent, grounded responses, so it would fail the core requirement of an interactive Q&A assistant.

• ✗

  Cloud Translation API — it translates policy documents into the user's language.

  Why it's wrong here

  Cloud Translation API is incorrect because it only translates text between languages; it cannot understand your company policies to answer questions or perform retrieval. Translating policy documents would merely produce a foreign-language version of the text, but you still need a large language model with a retrieval mechanism (RAG) to find relevant passages and compose a conversational answer. The assistant must connect user queries to the correct policy content, which requires semantic search and LLM grounding—capabilities entirely outside machine translation.

Go deeper

Related to this question