Databricks Certified Generative AI Engineer Associate Practice Test Questions and Exam Dumps Part11 Q201-220

View Full Databricks Certified Generative AI Engineer Associate Exam Dumps and Practice Test Dumps

 

Question 201. Which component converts text into numerical vectors for semantic retrieval?

  1. Token filter
  2. Embedding model
  3. Reranker
  4. Output parser

Correct Answer: 2. Embedding model

Explanation:

An embedding model converts text into numerical vector representations that capture semantic characteristics of the input. In a RAG architecture, documents and user queries can be transformed into embeddings and compared using a vector similarity measure. Texts with related meanings tend to have embeddings that are closer together than unrelated texts, allowing the retrieval system to identify potentially relevant information even when the exact words differ. Choosing an appropriate embedding model is important because its training characteristics, language support, domain coverage, and vector quality can influence retrieval performance. Embeddings are therefore a foundational component of semantic search and many modern RAG implementations.

Question 202. Why is chunk overlap sometimes used when splitting documents for RAG?

  1. To preserve context that may otherwise be lost at chunk boundaries
  2. To increase model temperature
  3. To remove all duplicate information
  4. To disable vector search

Correct Answer: 1. To preserve context that may otherwise be lost at chunk boundaries

Explanation:

Chunk overlap places some repeated text between neighboring chunks so that important context spanning a boundary is less likely to be separated. Without overlap, a sentence, definition, or explanation that begins near the end of one chunk and continues into the next may become difficult to retrieve as a complete unit. A moderate overlap can improve contextual continuity and retrieval quality for certain document types. However, excessive overlap can increase storage requirements, indexing cost, and duplicate retrieval results. The appropriate overlap depends on document structure and retrieval behavior, so it should be evaluated using representative queries rather than selected arbitrarily.

Question 203. What is a key purpose of query rewriting in a RAG application?

  1. To change the model’s architecture
  2. To remove the knowledge base
  3. To transform an unclear or conversational query into a retrieval-friendly query
  4. To increase the number of model parameters

Correct Answer: 3. To transform an unclear or conversational query into a retrieval-friendly query

Explanation:

Query rewriting improves retrieval by transforming the user’s original question into a form that better represents the information needed from the knowledge base. This can be particularly useful when a user uses pronouns, abbreviations, conversational references, or ambiguous terminology. For example, a follow-up question may make sense within a conversation but lack the explicit terms required for effective retrieval. A rewriting step can incorporate relevant conversation context and produce a clearer search query. The rewritten query can then be sent to semantic, lexical, or hybrid retrieval. This approach can improve retrieval quality without changing the underlying language model or source documents.

Question 204. Which metric is primarily concerned with the proportion of retrieved documents that are relevant?

  1. Retrieval recall
  2. Token throughput
  3. Retrieval precision
  4. Generation latency

Correct Answer: 3. Retrieval precision

Explanation:

Retrieval precision measures how much of the retrieved material is relevant to the user’s query. If a system retrieves ten documents and only six are relevant, the precision is lower than if nine of those ten documents are relevant. High precision helps ensure that the context supplied to the language model contains useful information rather than large amounts of unrelated material. Retrieval recall addresses a different question: whether the system successfully found the relevant information that exists in the available collection. Evaluating both precision and recall gives a more complete understanding of retrieval performance and can guide changes to chunking, filtering, top-k values, embeddings, and reranking.

Question 205. What should be considered when selecting an embedding model for an enterprise RAG system?

  1. Only the model’s name
  2. Domain, language, retrieval quality, and operational requirements
  3. The color of the application interface
  4. Only the number of documents

Correct Answer: 2. Domain, language, retrieval quality, and operational requirements

Explanation:

Embedding model selection should consider the characteristics of the application’s data and queries rather than relying on a single model attribute. Important factors can include supported languages, domain-specific terminology, retrieval quality, vector dimensions, latency, infrastructure requirements, and cost. An embedding model that performs well on general text may behave differently on specialized enterprise content containing technical terms, product identifiers, or internal terminology. Teams should evaluate candidate models using representative queries and relevant documents. Measuring retrieval precision and recall can provide evidence about which model better fits the intended workload. This evaluation-driven approach is more reliable than selecting an embedding model solely based on popularity or benchmark results.

Question 206. What is one benefit of filtering retrieved documents by effective date?

  1. It can help prevent obsolete information from being used
  2. It increases the LLM’s parameter count
  3. It eliminates authentication
  4. It disables document indexing

Correct Answer: 1. It can help prevent obsolete information from being used

Explanation:

Effective-date metadata allows a retrieval system to distinguish between information that is currently applicable and information that has been superseded. For policy documents, procedures, contracts, product specifications, or other time-sensitive content, retrieving an older version can produce an answer that is technically based on a real document but no longer valid. Applying an effective-date filter or ranking rule can reduce this risk. Such metadata should be maintained accurately during ingestion and document updates. Date filtering works particularly well when combined with version identifiers and source-system information, giving the RAG application a clearer understanding of which documents should be considered authoritative for a particular request.

Question 207. What is the purpose of a system instruction in a generative AI application?

  1. To define high-level behavior and constraints for the model
  2. To store every document in the vector database
  3. To replace authentication
  4. To calculate network bandwidth

Correct Answer: 1. To define high-level behavior and constraints for the model

Explanation:

A system instruction establishes high-level guidance for how the language model should behave during interactions. It can specify the assistant’s role, response style, use of retrieved context, restrictions, formatting requirements, and other application-specific rules. In a RAG system, the system instruction can tell the model to answer using supplied evidence and avoid unsupported claims. Clear instructions help make model behavior more consistent across user requests, although they cannot guarantee perfect compliance. System instructions are therefore one part of application design and should be combined with retrieval controls, output validation, guardrails, evaluation, and monitoring when building a production generative AI solution.

Question 208. Why should duplicate documents be identified during knowledge-base preparation?

  1. They always increase model accuracy
  2. They can create redundant retrieval results and distort search quality
  3. They prevent all hallucinations
  4. They eliminate the need for metadata

Correct Answer: 2. They can create redundant retrieval results and distort search quality

Explanation:

Duplicate documents can cause a retrieval system to return several copies of essentially the same information. This can consume the available top-k retrieval slots and reduce the diversity of evidence supplied to the language model. Duplicates may also make retrieval metrics appear misleading because multiple results may represent the same underlying source. During ingestion, teams can use document identifiers, hashes, source metadata, or other deduplication techniques to detect repeated content. Removing or consolidating unnecessary duplicates can improve retrieval efficiency and context diversity. Deduplication is particularly valuable in enterprise knowledge bases where documents may be copied across folders, systems, or different versions of an internal repository.

Question 209. Which approach is useful for handling a long multi-turn conversation within a limited context window?

  1. Include the entire conversation indefinitely
  2. Increase temperature
  3. Summarize older conversation history while retaining relevant information
  4. Remove the current user question

Correct Answer: 3. Summarize older conversation history while retaining relevant information

Explanation:

Long conversations can eventually exceed the context capacity available to the model. One common strategy is to summarize older portions of the conversation while preserving the information needed for future turns. The application can maintain recent messages verbatim and replace older exchanges with a concise summary containing important facts, decisions, preferences, or unresolved questions. This reduces token usage while preserving conversational continuity. The summarization strategy should be evaluated carefully because an incomplete or inaccurate summary can remove information needed for later responses. For applications with particularly important context, teams may combine summarization with retrieval of relevant conversation history or stored session information.

Question 210. What is the primary purpose of a vector index in a RAG system?

  1. To store and efficiently search vector representations
  2. To generate the final natural-language response
  3. To authenticate users
  4. To create system prompts

Correct Answer: 1. To store and efficiently search vector representations

Explanation:

A vector index stores or organizes numerical vector representations so that similarity searches can be performed efficiently. In a RAG system, document chunks are commonly converted into embeddings and placed into a vector-searchable index. When a user submits a query, the query can also be embedded and compared with indexed vectors to identify semantically similar chunks. Efficient indexing becomes important as the knowledge base grows because comparing a query against every vector directly can become computationally expensive. The vector index is therefore part of the retrieval layer rather than the generation layer. Its effectiveness depends on factors such as embedding quality, indexing configuration, and search parameters.

Question 211. What can happen if the top-k retrieval value is set excessively high?

  1. The model automatically becomes more accurate
  2. The retrieved context may contain more irrelevant information and consume context capacity
  3. Authentication is disabled
  4. The embedding model is deleted

Correct Answer: 2. The retrieved context may contain more irrelevant information and consume context capacity

Explanation:

The top-k setting controls how many candidate results are returned by a retrieval operation. Setting it too high can introduce additional documents that are only weakly related to the query. These documents consume context-window space and may distract the generation model from the strongest evidence. Higher k can sometimes improve recall when relevant information is distributed across multiple documents, but there is a trade-off between coverage and relevance. Teams should therefore evaluate different values using representative queries and metrics such as retrieval precision, recall, groundedness, and final answer quality. Reranking and metadata filtering can also help select the most useful context from a larger candidate set.

Question 212. What is a key reason to separate retrieval evaluation from generation evaluation?

  1. Retrieval and generation involve different failure modes
  2. It makes the model larger
  3. It eliminates the need for test data
  4. It guarantees perfect responses

Correct Answer: 1. Retrieval and generation involve different failure modes

Explanation:

Separating retrieval and generation evaluation helps teams determine where problems originate. A poor final answer may result because the retriever failed to find the required evidence, or because the language model failed to use good evidence correctly. Retrieval-specific evaluation can examine measures such as precision and recall, while generation evaluation can assess groundedness, relevance, correctness, formatting, and other response characteristics. By evaluating these layers separately, developers can target improvements more effectively. For example, changing the prompt will not necessarily solve a retrieval recall problem. Likewise, improving retrieval may not resolve an issue where the model consistently produces unsupported statements despite receiving relevant evidence.

Question 213. Which practice helps maintain traceability between an answer and the sources used to produce it?

  1. Increasing temperature
  2. Removing document metadata
  3. Recording source identifiers and retrieval information
  4. Disabling application logs

Correct Answer: 3. Recording source identifiers and retrieval information

Explanation:

Recording source identifiers and retrieval information helps teams understand which documents or chunks contributed to a generated response. This can support debugging, auditing, user-facing citations, and evaluation of groundedness. For example, an application may retain identifiers for the documents retrieved for a particular request and associate them with the resulting response. Such traceability makes it easier to investigate whether an answer was based on an appropriate source and whether obsolete or unauthorized information was retrieved. The exact information retained should follow the application’s security and privacy requirements. Traceability is particularly useful in enterprise RAG systems where users may need to verify the basis of generated information.

Question 214. What is one advantage of structured model output for downstream applications?

  1. It provides a predictable format that software can process
  2. It removes the need for retrieval
  3. It guarantees factual correctness
  4. It automatically improves embeddings

Correct Answer: 1. It provides a predictable format that software can process

Explanation:

Structured output allows an application to request responses that follow a predefined format, such as a JSON object with specified fields. This is useful when generated content must be consumed by another software component rather than displayed only as free-form text. A predictable structure simplifies parsing, validation, storage, and integration with downstream workflows. Applications can also validate generated output against a schema and handle missing or invalid fields appropriately. Structured output does not guarantee that the values are factually correct, so content quality still requires evaluation and, where appropriate, grounding in retrieved evidence. It primarily improves the reliability of the interface between the language model and application logic.

Question 215. Why is source-document quality important for RAG performance?

  1. The model can always correct poor source data
  2. Low-quality source content can lead to poor retrieval and unsupported answers
  3. Source quality affects only the user interface
  4. Source quality is unrelated to generated responses

Correct Answer: 2. Low-quality source content can lead to poor retrieval and unsupported answers

Explanation:

RAG systems depend on their knowledge sources, so inaccurate, incomplete, duplicated, or obsolete documents can directly affect retrieval and generation quality. If the knowledge base contains incorrect information, the retrieval system may successfully retrieve that incorrect content and the language model may use it when generating an answer. Similarly, poorly structured documents can make chunking and retrieval less effective. Knowledge-base preparation should therefore include quality checks, source validation, deduplication, version handling, and appropriate metadata. Improving the generation model cannot fully compensate for unreliable source material. Maintaining high-quality source data is consequently a critical part of building a trustworthy retrieval-augmented application.

Question 216. What should a team do before deploying a major change to a production RAG system?

  1. Skip evaluation to save time
  2. Test the change against representative evaluation data
  3. Delete the previous system version
  4. Increase randomness

Correct Answer: 2. Test the change against representative evaluation data

Explanation:

Major changes to a RAG system should be evaluated before production deployment to identify potential regressions. The evaluation should use representative queries and, where possible, compare the proposed version with a documented baseline. Depending on the change, teams may examine retrieval precision, recall, groundedness, response relevance, latency, cost, and other application-specific measures. Testing can reveal whether an improvement in one area has negatively affected another. Keeping previous versions available also provides a rollback path if production monitoring reveals unexpected behavior. This controlled approach reduces deployment risk and provides objective evidence for understanding how the new configuration performs under expected workloads.

Question 217. What does response groundedness primarily assess?

  1. Whether the response is supported by available evidence
  2. Whether the application has enough servers
  3. Whether the model has the largest parameter count
  4. Whether the user has authenticated

Correct Answer: 1. Whether the response is supported by available evidence

Explanation:

Response groundedness assesses whether claims in a generated answer are supported by the information available to the model, such as retrieved documents in a RAG workflow. A grounded response should not introduce unsupported facts that cannot be justified by the supplied evidence. This metric is different from response relevance, which focuses on whether the answer addresses the user’s question, and different from retrieval recall, which examines whether relevant source material was found. Evaluating groundedness can help identify hallucination-related behavior and determine whether prompt instructions, retrieval quality, or other controls need improvement. It is especially important when applications are expected to answer from controlled enterprise knowledge sources.

Question 218. What is a practical reason to monitor latency in a production generative AI application?

  1. Latency has no effect on user experience
  2. It can reveal performance degradation and help identify slow components
  3. It determines the model’s training dataset
  4. It replaces security controls

Correct Answer: 2. It can reveal performance degradation and help identify slow components

Explanation:

Latency monitoring measures how long requests take and can help teams identify performance problems in production. In a RAG application, total latency may include query processing, embedding generation, vector search, reranking, prompt construction, model generation, and network or infrastructure overhead. Monitoring these components separately can help identify where delays originate. Latency trends can also reveal degradation after a deployment or increased workload. Maintaining acceptable response times is important for user experience and operational efficiency. Teams should consider latency together with quality and cost because optimizing response time at the expense of answer quality may not satisfy application requirements.

Question 219. Which approach can help control access to confidential documents in a RAG system?

  1. Allow every user to retrieve every document
  2. Use authorization-aware filtering during retrieval
  3. Increase temperature
  4. Remove all document metadata

Correct Answer: 2. Use authorization-aware filtering during retrieval

Explanation:

Authorization-aware retrieval ensures that users receive only information they are permitted to access. This can involve associating access-control metadata with documents or chunks and applying the user’s permissions as retrieval filters. Enforcing access restrictions at the retrieval layer is important because providing confidential content to the language model can create a security issue even if the final response does not explicitly reveal every retrieved detail. Authentication establishes the user’s identity, while authorization determines which resources that identity can access. Enterprise RAG applications should therefore integrate appropriate identity, authorization, metadata, and auditing mechanisms rather than relying solely on prompt instructions to prevent unauthorized information exposure.

Question 220. Why is continuous evaluation useful after a RAG application has been deployed?

  1. Production data and user behavior can change over time
  2. It makes monitoring unnecessary
  3. It prevents every possible failure automatically
  4. It eliminates the need for version control

Correct Answer: 1. Production data and user behavior can change over time

Explanation:

Continuous evaluation helps ensure that a RAG application continues to perform as expected after deployment. Source documents may change, new terminology may appear, retrieval indexes may evolve, prompts may be updated, and users may submit queries that were not represented in the original evaluation dataset. Monitoring and periodic evaluation can reveal quality regressions, changes in retrieval behavior, increased latency, or new failure patterns. User feedback can also provide valuable examples for expanding evaluation datasets. Combining continuous evaluation with versioning, tracing, monitoring, and controlled deployment allows teams to identify problems earlier and make evidence-based improvements while maintaining awareness of system behavior over time.