Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest verify choice for this specific question. Load-test p95 latency and per-request cost against realistic payload sizes and concurrency. This action primarily relates to Latency, cost and retrieval targets as design requirements: A valid pipeline design has measurable quality, latency, token and throughput constraints before model selection. However, the described case — Accounts payable needs supplier name, invoice date and line items extracted into typed columns from PDFs. — is testing Agent Bricks Information Extraction versus Multiagent Supervisor. 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 outputs against task-specific labeled examples and inspect mismatches between required and produced formats. This action primarily relates to Task choice: classification versus generative summarization: Classification predicts a category whereas summarization compresses meaning; the desired output determines the appropriate task. However, the described case — Accounts payable needs supplier name, invoice date and line items extracted into typed columns from PDFs. — is testing Agent Bricks Information Extraction versus Multiagent Supervisor. 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. Trigger a timeout then retry and verify only one approved action persists with a trace. This action primarily relates to Agent tool schemas, least privilege and retries: Well-described tool schemas constrain parameters, and idempotent retries prevent duplicate side effects. However, the described case — Accounts payable needs supplier name, invoice date and line items extracted into typed columns from PDFs. — is testing Agent Bricks Information Extraction versus Multiagent Supervisor. 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. Switch alias to a tested version and verify the active agent follows it and can roll back. This action primarily relates to MLflow Prompt Registry version aliases and promotion: Prompt Registry tracks immutable prompt versions with mutable aliases for staging and production, enabling change control and rollback. However, the described case — A policy chatbot creates vectors but never passes retrieved passages to the LLM, producing unsupported recommendations. — is testing Vector Search retrieval workflow and query integration. 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. Load the registered bundle in a clean environment and validate retrieval-to-generation behavior end to end. 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 policy chatbot creates vectors but never passes retrieved passages to the LLM, producing unsupported recommendations. — is testing Vector Search retrieval workflow and query integration. 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. Load an explicitly registered version and confirm its dependencies and outputs match the approved evaluation run. 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 policy chatbot creates vectors but never passes retrieved passages to the LLM, producing unsupported recommendations. — is testing Vector Search retrieval workflow and query integration. 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 diagnose choice for this specific question. Inspect heading structure, sentence breaks, table boundaries and parent document identifiers. This action primarily relates to Semantic boundaries versus fixed-window chunks: Headings, paragraphs and tables can require structure-aware splitting rather than arbitrary token windows. However, the described case — A legal RAG service finds semantically similar contracts from the wrong customer workspace. — is testing Hybrid sparse and dense retrieval with filters. 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 the most frequent n-grams, extracted layout artifacts and top retrieved false positives. This action primarily relates to Boilerplate and navigation filtering in source corpora: Duplicated headers, disclaimers and navigation menus contaminate embeddings and cause irrelevant hits. However, the described case — A legal RAG service finds semantically similar contracts from the wrong customer workspace. — is testing Hybrid sparse and dense retrieval with filters. 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 labeled query/chunk relevance, false positive hits, top-k settings and evaluation coverage. This action primarily relates to Retrieval recall precision and ranking diagnostics: Measure hit recall, precision, MRR or nDCG on labeled query-to-relevant-chunk pairs before tuning retrieval. However, the described case — A legal RAG service finds semantically similar contracts from the wrong customer workspace. — is testing Hybrid sparse and dense retrieval with filters. 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 safeguard choice for this specific question. Separate missing knowledge from bad generation during incident triage and refresh upstream data responsibly. This action primarily relates to Authoritative source coverage for factual answers: A RAG model cannot answer accurately if the required authoritative record is missing or stale in its index. However, the described case — A compliance RAG app splits a numbered contract clause so exclusions are separated from the obligation. — is testing Semantic boundaries versus fixed-window chunks. 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 a frozen relevance dataset to prevent tuning to a single cherry-picked query. This action primarily relates to Retrieval recall precision and ranking diagnostics: Measure hit recall, precision, MRR or nDCG on labeled query-to-relevant-chunk pairs before tuning retrieval. However, the described case — A compliance RAG app splits a numbered contract clause so exclusions are separated from the obligation. — is testing Semantic boundaries versus fixed-window chunks. 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. Version preprocessing rules and sample exceptions so cleansing never strips legal requirements. This action primarily relates to Boilerplate and navigation filtering in source corpora: Duplicated headers, disclaimers and navigation menus contaminate embeddings and cause irrelevant hits. However, the described case — A compliance RAG app splits a numbered contract clause so exclusions are separated from the obligation. — is testing Semantic boundaries versus fixed-window chunks. 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 verify choice for this specific question. Exercise failed tests and confirm release is blocked, then deploy and verify a passing version. 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 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. Load the logged pyfunc model in an isolated environment and test the declared signature on sample requests. 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 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. Load an explicitly registered version and confirm its dependencies and outputs match the approved evaluation run. 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 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. Reproduce representative task evaluation in the intended language and document limitations. 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 team picks a model marked research-only and plans to deploy it for a paid product. — is testing Open model license versus managed endpoint obligations. 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. Audit answer-supportedness using labeled trace examples and a human review of fabricated citations. This action primarily relates to Hallucinated facts and unsupported citations: Fluent responses can invent facts and citations; faithfulness must be checked against supplied evidence, not writing style. However, the described case — A team picks a model marked research-only and plans to deploy it for a paid product. — is testing Open model license versus managed endpoint obligations. 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. 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 team picks a model marked research-only and plans to deploy it for a paid product. — is testing Open model license versus managed endpoint obligations. 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. Query the relevant index with a compatible query embedding, select authorized matches and pass them to the prompt. This action primarily relates to Vector Search retrieval workflow and query integration: Semantic retrieval uses an embedding model to query a compatible index, returns ranked passages and metadata for grounded generation. However, the described case — A research archive contains hundreds of millions of mostly static embeddings and storage cost is the main constraint. — is testing Standard versus storage-optimized Vector Search index. 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 research archive contains hundreds of millions of mostly static embeddings and storage cost is the main constraint. — is testing Standard versus storage-optimized Vector Search index. 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 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 proof-of-concept team wants a supported hosted LLM without managing GPU serving or packaging custom weights. — is testing Foundation Model API versus custom serving choices. 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. Load-test typical and burst concurrency and adjust supported serving capacity or queueing strategy. This action primarily relates to Endpoint scale concurrency and operational rollout: Serving latency and reliability depend on provisioned capacity, request concurrency, quotas and controlled rollout. However, the described case — A proof-of-concept team wants a supported hosted LLM without managing GPU serving or packaging custom weights. — is testing Foundation Model API versus custom serving choices. 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. Package preprocessing, inference and postprocessing in an MLflow pyfunc model with required dependencies and signature. 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 proof-of-concept team wants a supported hosted LLM without managing GPU serving or packaging custom weights. — is testing Foundation Model API versus custom serving choices. 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. Store session state in a governed datastore keyed by the authenticated user and permitted ticket. This action primarily relates to Persistent conversation memory with authorized datastore: Transient prompt context differs from persistent user state; durable memory needs explicit storage, identity scope and retention. However, the described case — A developer's support chain omits the retrieved context and the LLM hallucinates policy clauses. — is testing Simple prompt-retrieval-generation chain assembly. 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 developer's support chain omits the retrieved context and the LLM hallucinates policy clauses. — is testing Simple prompt-retrieval-generation chain assembly. 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. Promote a tracked model version or alias while preserving the previous model version for rollback. 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 developer's support chain omits the retrieved context and the LLM hallucinates policy clauses. — is testing Simple prompt-retrieval-generation chain assembly. 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. Use Agent Bricks Information Extraction with a defined schema and review uncertain fields. This action primarily relates to Agent Bricks Information Extraction versus Multiagent Supervisor: Information Extraction maps source documents to structured fields; Multiagent Supervisor coordinates specialized capabilities for compound workflows. However, the described case — A finance controller wants a one-paragraph explanation of a long audit memo, not a risk score. — is testing Task choice: classification versus generative summarization. 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. Specify a stable array-of-objects schema, require only the specified keys and reject malformed results before rendering. This action primarily relates to Structured JSON schema prompt and format compliance: A model can produce plausible prose rather than machine-readable JSON unless the output contract and validation are explicit. However, the described case — A finance controller wants a one-paragraph explanation of a long audit memo, not a risk score. — is testing Task choice: classification versus generative summarization. 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. Assemble query-to-retriever-to-context-grounded-prompt-to-LLM stages and attach citations to retrieved passages. This action primarily relates to Retriever-generator chain component boundaries: A basic RAG chain separates user input, query transformation, retrieval, prompt assembly, model generation and output validation. However, the described case — A finance controller wants a one-paragraph explanation of a long audit memo, not a risk score. — is testing Task choice: classification versus generative summarization. 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 diagnose choice for this specific question. Inspect each judge's required inputs, reference fields, rubric and expected failure behavior. This action primarily relates to Ground-truth requirement for correctness versus reference-free judges: A correctness comparison often needs an expected answer; other judges such as format or safety can operate without a reference. However, the described case — A medical expert flags unsafe triage advice, but engineering discards the feedback because an LLM judge rates it highly. — is testing Human SME feedback rubric and reviewer calibration. 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 medical expert flags unsafe triage advice, but engineering discards the feedback because an LLM judge rates it highly. — is testing Human SME feedback rubric and reviewer calibration. 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 production trace quality, error types, latency percentiles, user feedback and alert routes. This action primarily relates to Production performance KPIs and incident thresholds: Monitoring should include answer correctness, retrieval coverage, safety, latency, drift and per-user harm indicators, not just availability. However, the described case — A medical expert flags unsafe triage advice, but engineering discards the feedback because an LLM judge rates it highly. — is testing Human SME feedback rubric and reviewer calibration. 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.