Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest verify choice for this specific question. Check embedding dimensions or extracted-field validation against task-specific acceptance tests. This action primarily relates to Specialized model versus general LLM: Embedding, reranking, extraction and generative models solve different stages and should be evaluated for their actual role. However, the described case — A large catalog's vector storage bill rises after selecting a high-dimensional encoder with no measured gain. — is testing Embedding dimensions latency and index storage. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Verify matched query and document vectors use the approved version and retrieval improves on held-out examples. This action primarily relates to Embedding model swap and reindex compatibility: Changed embedding dimensions or model semantics typically require re-embedding and index consistency before comparing search quality. However, the described case — A large catalog's vector storage bill rises after selecting a high-dimensional encoder with no measured gain. — is testing Embedding dimensions latency and index storage. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Embed test chunks with relevant facts at the end and confirm they remain retrievable. This action primarily relates to Embedding context window and chunk token distribution: The embedding encoder must accept the actual tokenized chunk length; silently truncating chunks can drop relevant suffix facts. However, the described case — A large catalog's vector storage bill rises after selecting a high-dimensional encoder with no measured gain. — is testing Embedding dimensions latency and index storage. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Use suitably low variability and an explicit output schema, preserving deterministic financial calculations outside LLM. This action primarily relates to Temperature and deterministic format tradeoffs: Decoding settings can affect variability and cost but cannot replace validation, grounding or application logic. However, the described case — A low-cost support search uses short chunks but the proposed model multiplies embedding dimensions by eight. — is testing Embedding dimensions latency and index storage. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Select a candidate with measured language coverage and document residual risk on target-language samples. This action primarily relates to Model cards and task-specific limitations: A model card records intended uses, supported language/context, safety limitations and evaluation scope relevant to selection. However, the described case — A low-cost support search uses short chunks but the proposed model multiplies embedding dimensions by eight. — is testing Embedding dimensions latency and index storage. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Evaluate a schema-following extraction model or specialized workflow with validation for required fields. This action primarily relates to Specialized model versus general LLM: Embedding, reranking, extraction and generative models solve different stages and should be evaluated for their actual role. However, the described case — A low-cost support search uses short chunks but the proposed model multiplies embedding dimensions by eight. — is testing Embedding dimensions latency and index storage. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Increase coherent chunk context or parent expansion, then compare answer coverage to the earlier chunking strategy. This action primarily relates to Chunk quality evaluation and boundary splitting: Retrieval failure can arise from overly small chunks that omit needed context or overly large chunks that dilute relevance. However, the described case — Document chunks average 700 tokens but the selected embedding model only accepts 512 tokens. — is testing Embedding context window and chunk token distribution. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Select a suitable embedding model rather than treating generated prose as a numeric embedding. This action primarily relates to Specialized model versus general LLM: Embedding, reranking, extraction and generative models solve different stages and should be evaluated for their actual role. However, the described case — Document chunks average 700 tokens but the selected embedding model only accepts 512 tokens. — is testing Embedding context window and chunk token distribution. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Build a compatible new index and re-embed the corpus, then test cutover against representative queries. This action primarily relates to Embedding model swap and reindex compatibility: Changed embedding dimensions or model semantics typically require re-embedding and index consistency before comparing search quality. However, the described case — Document chunks average 700 tokens but the selected embedding model only accepts 512 tokens. — is testing Embedding context window and chunk token distribution. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Register the MLflow model as a named Unity Catalog model version and grant only approved use/manage rights. This action primarily relates to Unity Catalog registered model version and privileges: MLflow-logged models can be registered in Unity Catalog, with governed names, permissions and traceable version lineage. However, the described case — A deployed agent hardcodes prompt version 1, so validated updates never reach the application. — is testing MLflow Prompt Registry version aliases and promotion. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Version the serving input schema or provide a tested compatibility adapter during migration. This action primarily relates to Deployed model dependency drift and environment compatibility: Models logged in experiments can fail in serving if Python dependencies or inference signatures differ between build and target. However, the described case — A deployed agent hardcodes prompt version 1, so validated updates never reach the application. — is testing MLflow Prompt Registry version aliases and promotion. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Bind question and retrieval context into a complete prompt before invoking the model and parsing output. This action primarily relates to Simple prompt-retrieval-generation chain assembly: A minimal chain composes a retriever, prompt, LLM and output parser, preserving required variables and failure states. However, the described case — A deployed agent hardcodes prompt version 1, so validated updates never reach the application. — is testing MLflow Prompt Registry version aliases and promotion. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Split the section at legal boundaries and preserve exceptions rather than allowing implicit truncation. This action primarily relates to Embedding context window and chunk token distribution: The embedding encoder must accept the actual tokenized chunk length; silently truncating chunks can drop relevant suffix facts. However, the described case — A legal contract review agent needs nuanced long-context reasoning but can tolerate higher response time. — is testing Model selection by quality latency and budget. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Benchmark lower-cost dimension options and choose one meeting retrieval recall and latency goals. This action primarily relates to Embedding dimensions latency and index storage: Embedding width affects index storage and computation, and larger dimensions do not automatically improve task relevance. However, the described case — A legal contract review agent needs nuanced long-context reasoning but can tolerate higher response time. — is testing Model selection by quality latency and budget. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Select a candidate with measured language coverage and document residual risk on target-language samples. This action primarily relates to Model cards and task-specific limitations: A model card records intended uses, supported language/context, safety limitations and evaluation scope relevant to selection. However, the described case — A legal contract review agent needs nuanced long-context reasoning but can tolerate higher response time. — is testing Model selection by quality latency and budget. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Version the serving input schema or provide a tested compatibility adapter during migration. This action primarily relates to Deployed model dependency drift and environment compatibility: Models logged in experiments can fail in serving if Python dependencies or inference signatures differ between build and target. However, the described case — A deploy pipeline overwrites the production prompt text each release and cannot restore yesterday's known-good response. — is testing MLflow Prompt Registry version aliases and promotion. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Bundle compatible index/embedding identifiers and validate query-embedding compatibility at initialization. This action primarily relates to RAG production bundle metadata and dependencies: A deployable RAG application needs tracked model code, retriever config, embedding model, dependency versions, signature and example input. However, the described case — A deploy pipeline overwrites the production prompt text each release and cannot restore yesterday's known-good response. — is testing MLflow Prompt Registry version aliases and promotion. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Evaluate a custom serving endpoint with model packaging and scaling suitable to the checkpoint. This action primarily relates to Foundation Model API versus custom serving choices: Databricks Foundation Model APIs offer managed access to supported models; custom serving is suitable for specialized models or control needs. However, the described case — A deploy pipeline overwrites the production prompt text each release and cannot restore yesterday's known-good response. — is testing MLflow Prompt Registry version aliases and promotion. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Favor the architecture meeting field accuracy and throughput constraints rather than model size. This action primarily relates to Model selection from quantitative task metrics: Select candidate LLMs by measured task success, latency, safety and token cost, not parameter count or leaderboard rank. However, the described case — A finance team cannot attribute escalating LLM spend to teams because requests have no workload identity. — is testing AI Gateway rate limits, usage tables and inference telemetry. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Use usage monitoring and budgets to detect regressions when prompts, indexes or models change. This action primarily relates to Databricks usage and token cost controls: Reduce LLM spend through token budgets, caching, smaller appropriate models and AI Gateway quotas while preserving acceptance quality. However, the described case — A finance team cannot attribute escalating LLM spend to teams because requests have no workload identity. — is testing AI Gateway rate limits, usage tables and inference telemetry. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect gateway policies, invocation identity, consumption tables, endpoint errors and supported feature availability. This action primarily relates to AI Gateway rate limits, usage tables and inference telemetry: AI Gateway offers controlled access, supported usage tracking and rate limiting to protect shared endpoints and measure consumption. However, the described case — A chatbot owner demands exact reference-match scoring for open-ended helpfulness with many valid phrasings. — is testing Ground-truth requirement for correctness versus reference-free judges. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect token volumes, QPS, endpoint pricing, cache hit rate and user/workload attribution. This action primarily relates to Databricks usage and token cost controls: Reduce LLM spend through token budgets, caching, smaller appropriate models and AI Gateway quotas while preserving acceptance quality. However, the described case — A chatbot owner demands exact reference-match scoring for open-ended helpfulness with many valid phrasings. — is testing Ground-truth requirement for correctness versus reference-free judges. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect inference table availability, payload schemas, trace IDs and user-feedback mapping. This action primarily relates to Inference tables and Agent Monitoring feedback loop: Inference tables and agent monitoring capture production request/response signals and traces for quality investigations. However, the described case — A chatbot owner demands exact reference-match scoring for open-ended helpfulness with many valid phrasings. — is testing Ground-truth requirement for correctness versus reference-free judges. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Compare usefulness and privacy leakage metrics on held-out documents before and after selective masking. This action primarily relates to Contextual masking versus destructive data removal: Masking must preserve information needed for the task, such as non-sensitive dates or amounts, and cannot replace access control. However, the described case — A chatbot accepts a malicious request to publish harassing content to a company social feed. — is testing Prompt safety filtering and tool allowlists. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Query for known synthetic sensitive strings and confirm no original identifiers appear in chunks or answers. This action primarily relates to Sensitive-field masking before embedding: Masking or tokenization can remove unnecessary PII from chunks before embedding and external model calls while retaining useful meaning. However, the described case — A chatbot accepts a malicious request to publish harassing content to a company social feed. — is testing Prompt safety filtering and tool allowlists. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Test harmful queries and verify contaminated passages are blocked without discarding legitimate safety instructions. This action primarily relates to Toxic, inaccurate and adversarial corpus cleaning: Unreliable source text can teach unsafe behavior through retrieval; quarantine and source review matter before embeddings. However, the described case — A chatbot accepts a malicious request to publish harassing content to a company social feed. — is testing Prompt safety filtering and tool allowlists. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Sample pages/images against extracted text and check structured fields and layout fidelity. This action primarily relates to Format-specific document extraction and OCR needs: Extract text with a parser suited to source format; image-only scans require OCR rather than HTML or plain-text parsing. However, the described case — After an ingestion rerun, duplicate chunks multiply because the pipeline only appends without source identity. — is testing Delta and Unity Catalog pipeline for chunk tables. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Retrieve rare table values and confirm the matching row, units and header context are intact. This action primarily relates to Table-aware chunking and metadata-rich retrieval: Tabular rows need headers, units and column semantics preserved when transformed into retrieval documents. However, the described case — After an ingestion rerun, duplicate chunks multiply because the pipeline only appends without source identity. — is testing Delta and Unity Catalog pipeline for chunk tables. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Compare hit recall and answer grounding for sample chunk sizes with a fixed query set. This action primarily relates to Chunk size and overlap tradeoffs: Chunk size determines the number of vectors and coherence; overlap reduces boundary loss but increases index size and cost. However, the described case — After an ingestion rerun, duplicate chunks multiply because the pipeline only appends without source identity. — is testing Delta and Unity Catalog pipeline for chunk tables. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Never rely on interactive notebook state or unpinned runtime packages when promoting a served model. This action primarily relates to MLflow pyfunc packaging for pre- and post-processing: A custom MLflow pyfunc model wraps request parsing, retriever/model invocation and output formatting inside a reproducible predict interface. However, the described case — A deployed chatbot silently uses a different embedding model from the retrieval index built in development. — is testing RAG production bundle metadata and dependencies. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Do not equate registering a model with approving its business safety or access to all governed tables. This action primarily relates to Unity Catalog registered model version and privileges: MLflow-logged models can be registered in Unity Catalog, with governed names, permissions and traceable version lineage. However, the described case — A deployed chatbot silently uses a different embedding model from the retrieval index built in development. — is testing RAG production bundle metadata and dependencies. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Require approval/rollback for prompt and index changes that alter user-facing model behavior. This action primarily relates to CI/CD pipelines for retrieval and agent components: Production promotions should test source index, prompt, model packaging and tool behavior independently before release. However, the described case — A deployed chatbot silently uses a different embedding model from the retrieval index built in development. — is testing RAG production bundle metadata and dependencies. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.