Generative AI Leader Flashcards — Free Google Cloud Generative AI Leader Generative AI Leader Study Cards

Enable Vertex AI Grounding with a custom enterprise data store containing the documentation.

Vertex AI Grounding with a custom enterprise data store is the correct approach because it allows the chatbot to retrieve and cite specific chunks from the product documentation in real time, directly reducing hallucinations by constraining responses to verified content. This method uses the underlying grounding service to query a vector-based data store (powered by Vertex AI Search) and append source references to the model's output, ensuring factual accuracy without retraining.

Ground the model with proprietary product data and brand guidelines in a retrieval-augmented generation (RAG) architecture.

Option A is correct because retrieval-augmented generation (RAG) allows the chatbot to ground its responses in the company's proprietary product data and brand guidelines, ensuring factual accuracy and brand consistency. By retrieving relevant information from a curated knowledge base at inference time, the model can provide up-to-date recommendations without requiring retraining, which is critical for a retail environment with frequently changing inventory.

Vertex AI Search with document grounding

Vertex AI Search with document grounding is correct because it allows the chatbot to ground responses in the customer's own medical documents stored in Cloud Storage, ensuring low latency through optimized indexing and retrieval, while supporting data residency controls to keep data within the EU. This service is specifically designed for enterprise search and Q&A over private document repositories, making it ideal for healthcare use cases requiring compliance and fast responses.

Apply reinforcement learning from human feedback (RLHF)

RLHF directly addresses the misalignment between the model's training objective (e.g., predicting the next token) and the desired outcome (helpful, not just polite). By using human feedback to train a reward model, the system learns to optimize for response quality and helpfulness, reducing sycophantic or overly polite but uninformative outputs.

The model has not been deployed to the specified endpoint

The error indicates that the model is not deployed to the endpoint. In Vertex AI, an endpoint is a resource that hosts one or more deployed models. If a model has not been deployed to the endpoint, any prediction request to that endpoint will fail with a 'model not found' or similar error, even if the endpoint ID and region are correct.

The top_p value is too high; reduce top_p to limit token sampling.

Repetitive outputs in a chat application after a few turns are typically caused by the model getting stuck in a loop due to high cumulative probability from top-p sampling. Reducing top_p limits the set of tokens considered at each step, forcing the model to explore less likely tokens and breaking the repetition cycle. This directly addresses the issue without sacrificing coherence, unlike temperature adjustments which affect randomness globally.

Implement retrieval-augmented generation (RAG) using the conversation dataset as a knowledge base.

Retrieval-augmented generation (RAG) directly addresses hallucinations by grounding the model's responses in factual, retrieved data from the conversation dataset. This approach allows the model to generate fluent, contextually relevant answers while reducing the risk of inventing information, as it retrieves actual support interactions as evidence before generating a response.

Use a serverless inference endpoint that scales to zero when not in use.

Option C is correct because serverless inference endpoints, such as AWS Lambda with SageMaker or Google Cloud Run, automatically scale to zero when idle, eliminating costs during periods of no traffic. This directly addresses the startup's goal of minimizing operational costs while maintaining low latency through rapid cold-start optimizations and provisioned concurrency for burst handling.

Use a retrieval-augmented generation (RAG) system that queries a live database of sensor configurations.

Option D is correct because a retrieval-augmented generation (RAG) system retrieves the most current equipment configurations directly from a live database at inference time, ensuring the generated manual reflects real-time sensor data without requiring model retraining. This approach decouples the static knowledge in the LLM from the dynamic data source, guaranteeing both accuracy and freshness while avoiding the latency and cost of continuous retraining.

Use negative prompts

Negative prompts allow the model to exclude specific concepts, styles, or elements from generated images, directly reducing the risk of replicating copyrighted or trademarked content. By explicitly telling Imagen what not to include, the agency can steer outputs away from protected works without needing to modify training data or safety filters.

Use retrieval-augmented generation (RAG) with vector search on the FAQ database.

Option A is correct because retrieval-augmented generation (RAG) with vector search allows the chatbot to dynamically retrieve the most relevant, up-to-date FAQ entries from a large database at inference time, grounding the generative model's responses in verified content without requiring retraining. This approach combines the flexibility of a pre-trained language model with the accuracy of real-time information retrieval, ensuring answers reflect the latest FAQ updates.

Reduction in content production time

Option A is correct because the primary business impact of a GenAI content generation tool is operational efficiency, measured by the reduction in content production time. This metric directly correlates to cost savings and faster time-to-market, which are key business outcomes. Unlike technical metrics, it reflects real-world value delivery.

Use pre-trained models via Google Cloud's Generative AI Studio API

Option B is correct because using pre-trained models via Google Cloud's Generative AI Studio API allows the company to leverage existing, powerful models without the high cost and time investment of custom development or fine-tuning. This approach enables rapid deployment on a limited budget by simply integrating the API into their chatbot, handling routine inquiries effectively without requiring extensive machine learning expertise or infrastructure.

Review usage patterns and optimize prompt lengths and frequencies

Option C is correct because the first step in responding to a budget overrun should be to analyze usage patterns and optimize prompt lengths and frequencies. This approach identifies inefficiencies (e.g., unnecessarily verbose prompts, excessive retries) that directly reduce token consumption and cost without disrupting critical operations. It aligns with the principle of cost optimization before making architectural or policy changes.

The embedding model is not aligned with the domain vocabulary

Option D is correct because irrelevant responses in a RAG (Retrieval-Augmented Generation) chatbot most often stem from the embedding model failing to capture domain-specific semantics. If the embedding model was trained on general text (e.g., Wikipedia) but the chatbot operates in a specialized field like legal or medical, the vector similarity search will retrieve context that is semantically distant from the user's query, leading to irrelevant answers. This is a business strategy issue because the team chose an embedding model that does not align with their domain vocabulary, undermining the entire retrieval pipeline.

Use a private Google Cloud Access and disable external internet access for the endpoint.

Option D is correct because HIPAA requires that patient data be protected from unauthorized access during transmission and deployment. Using a private Google Cloud Access endpoint with external internet access disabled ensures that the model endpoint is only reachable within the organization's VPC network, preventing data exposure over the public internet and meeting HIPAA's security rule for safeguarding electronic protected health information (ePHI).

Include a system instruction at the beginning of the prompt that specifies the desired format.

Option C is correct because system instructions are the most direct and efficient method to enforce output formatting in large language models. By placing a clear directive at the beginning of the prompt (e.g., 'Always start your response with a greeting'), the model's attention mechanism is guided to prioritize this rule during generation, without requiring retraining or hyperparameter changes.

The user needs the roles/aiplatform.deployer role

The user has an IAM role but lacks the specific permission `aiplatform.deployments.create` required to deploy a model to a Vertex AI Endpoint. The `roles/aiplatform.deployer` role includes this permission, while the user's existing role does not, causing the deployment to fail. Even if the user can use other Vertex AI services, deploying a model to an endpoint is a distinct action that requires this specific role.

To connect model outputs to verifiable sources

Grounding in Vertex AI connects model outputs to verifiable, external sources of information (such as Google Search, enterprise data sources, or third-party databases) to reduce hallucinations and improve factual accuracy. By referencing grounded sources, the model can provide citations and allow users to verify claims, which is critical for enterprise applications requiring trust and compliance.

Fine-tune the model using a balanced, representative dataset and implement output filtering

Fine-tuning on a balanced, representative dataset directly addresses the root cause of biased outputs by correcting the model's learned associations, while output filtering provides a safety net to catch residual bias. This combination is more effective than superficial fixes because it modifies the model's internal weights rather than just masking outputs.

Use a fine-tuned version of a smaller model on Vertex AI with response caching

Option D is correct because using a fine-tuned smaller model on Vertex AI with response caching reduces both cost and latency. Smaller models require fewer computational resources, and caching avoids redundant inference calls, directly addressing the company's concerns without sacrificing accuracy for the specific task.

Use model quantization

Option C is correct because model quantization reduces the precision of the model's weights (e.g., from FP32 to INT8), which decreases memory footprint and computational requirements, directly lowering inference latency for real-time applications on Vertex AI. This is a standard optimization technique for deploying large language models with minimal accuracy loss while meeting latency SLAs.