Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest implement choice for this specific question. Build a CI gate for prompt schema, retrieval relevance, agent tools and controlled promotion across environments. 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 chain logged under Python package version A fails to deserialize when the model serving image ships incompatible version B. — is testing Deployed model dependency drift and environment compatibility. 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 chain logged under Python package version A fails to deserialize when the model serving image ships incompatible version B. — is testing Deployed model dependency drift and environment compatibility. 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. Log the app with dependency requirements, retrieval configuration, model signature and example requests. 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 chain logged under Python package version A fails to deserialize when the model serving image ships incompatible version B. — is testing Deployed model dependency drift and environment compatibility. 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 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 — An order-status assistant needs real-time package state plus the carrier's public shipping policy. — is testing Parallel retrieval and deterministic chain postprocessing. 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. Run cases with complete and missing required input fields and verify schema, access scope and usefulness. This action primarily relates to Translate use-case requirements into pipeline inputs and outputs: Business acceptance criteria must map to concrete source inputs, generated fields, correctness measures and permission constraints. However, the described case — An order-status assistant needs real-time package state plus the carrier's public shipping policy. — is testing Parallel retrieval and deterministic chain postprocessing. 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. Run adversarial quoted-text tests and compare output structure on representative and edge inputs. This action primarily relates to Instruction hierarchy and bounded prompt examples: Few-shot examples and explicit boundaries can clarify expected outputs, but embedded source documents should not become new system instructions. However, the described case — An order-status assistant needs real-time package state plus the carrier's public shipping policy. — is testing Parallel retrieval and deterministic chain postprocessing. 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. Join authorized structured values and retrieved policy context through a controlled composition stage. This action primarily relates to Parallel retrieval and deterministic chain postprocessing: Combining structured lookup and semantic retrieval requires explicit routing, result joining, and downstream schema checks. However, the described case — A policy assistant produces unsupported answers because its chain sends only the user question to the LLM. — is testing Retriever-generator chain component boundaries. 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 assume an instruction to 'respond in JSON' replaces actual schema validation and error handling. 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 policy assistant produces unsupported answers because its chain sends only the user question to the LLM. — is testing Retriever-generator chain component boundaries. 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 helpdesk agent receives frequent negative user feedback but no monitoring process turns it into reproducible examples. — is testing Inference tables and Agent Monitoring feedback loop. 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 logging configuration, sampling policy, trace privacy, missing identifiers and audit destinations. This action primarily relates to Inference logging and production trace privacy: Inference logs and tracing permit diagnosis of real issues but must be sampled, retained and redacted safely. However, the described case — A helpdesk agent receives frequent negative user feedback but no monitoring process turns it into reproducible examples. — is testing Inference tables and Agent Monitoring feedback loop. 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 helpdesk agent receives frequent negative user feedback but no monitoring process turns it into reproducible examples. — is testing Inference tables and Agent Monitoring feedback loop. 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 — An invoice extraction agent passes generic relevance judges but loses an essential invoice currency field. — is testing MLflow GenAI tracing, built-in and custom scorers. 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 — An invoice extraction agent passes generic relevance judges but loses an essential invoice currency field. — is testing MLflow GenAI tracing, built-in and custom scorers. 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 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 — An invoice extraction agent passes generic relevance judges but loses an essential invoice currency field. — is testing MLflow GenAI tracing, built-in and custom scorers. 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 model version, vector dimensions, index schema, pipeline lineage and freshness. 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 — An invoice workflow needs exact structured amounts and dates but developers choose an unconstrained chat generator only. — is testing Specialized model versus general LLM. 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 runnable input/output schemas, prompt variables and invocation traces around the failing stage. This action primarily relates to LangChain runnable composition and invocation: Composable runnable chains pass typed values between retrieval, prompt and model stages; each binding must preserve expected input keys. However, the described case — An invoice workflow needs exact structured amounts and dates but developers choose an unconstrained chat generator only. — is testing Specialized model versus general LLM. 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 evaluation data composition, judge criteria, run configuration and sampled failures. This action primarily relates to Model evaluation with paired benchmarks: Accuracy, faithfulness, relevance and refusal behavior require task-specific scoring, and a model switch needs common test conditions. However, the described case — An invoice workflow needs exact structured amounts and dates but developers choose an unconstrained chat generator only. — is testing Specialized model versus general LLM. 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 required output type, input modality and measured task capability rather than model size alone. 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 multi-step customer agent calls Genie and Vector Search but no span shows which returned an incorrect fact. — is testing MLflow tracing in an Agent Framework workflow. 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 training/licensing terms, model-card task benchmarks, input limits and restrictions. 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 multi-step customer agent calls Genie and Vector Search but no span shows which returned an incorrect fact. — is testing MLflow tracing in an Agent Framework workflow. 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 request/response sensitive spans, redaction logs, moderation findings and business exceptions. This action primarily relates to PII masking and output moderation as complementary guardrails: Input redaction and output checks serve distinct purposes; retain only necessary identifiers and validate actions separately. However, the described case — A multi-step customer agent calls Genie and Vector Search but no span shows which returned an incorrect fact. — is testing MLflow tracing in an Agent Framework workflow. 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 precision at k before and after cleaning while checking no required policy sentences were removed. 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 team embeds PDFs directly into an unmanaged in-memory list, losing source versions and permissions. — 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. Test representative queries needing missing records and confirm either accurate retrieval or abstention. 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 team embeds PDFs directly into an unmanaged in-memory list, losing source versions and permissions. — 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 fixed evaluation queries on baseline and candidate retrieval with confidence in differences. 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 team embeds PDFs directly into an unmanaged in-memory list, losing source versions and permissions. — 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. Check that an exception and its definition are available to the generator after retrieval. This action primarily relates to Parent-child retrieval and hierarchical structure: Parent-child retrieval indexes targeted sections but expands to their broader parent context for generation. However, the described case — An internal parts bot misses exact serial number ZX-410 because embeddings match only conceptual part descriptions. — is testing Hybrid sparse and dense retrieval with filters. 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 that target retrieval returns complete condition-and-exception evidence for representative questions. 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 — An internal parts bot misses exact serial number ZX-410 because embeddings match only conceptual part descriptions. — is testing Hybrid sparse and dense retrieval with filters. 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. Run an incremental update and verify new, changed and deleted source chunks are reflected exactly once. This action primarily relates to Delta and Unity Catalog pipeline for chunk tables: A governed retrieval corpus stores chunk text, IDs, source lineage and metadata in managed Delta/Unity Catalog tables before indexing. However, the described case — An internal parts bot misses exact serial number ZX-410 because embeddings match only conceptual part descriptions. — is testing Hybrid sparse and dense retrieval with filters. 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. Validate returned IDs, relevant scores and grounded answer citations on known reference queries. 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 claims RAG prototype uses notebook variables and cannot run when served outside the developer session. — is testing MLflow pyfunc packaging for pre- and post-processing. 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. Validate tool discovery and a permitted request for both services, including denied action testing. This action primarily relates to Managed versus external versus custom MCP server integration: MCP standardizes tool discovery; managed servers reduce hosting, external services need credentials and custom servers wrap bespoke actions. However, the described case — A claims RAG prototype uses notebook variables and cannot run when served outside the developer session. — is testing MLflow pyfunc packaging for pre- and post-processing. 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 claims RAG prototype uses notebook variables and cannot run when served outside the developer session. — is testing MLflow pyfunc packaging for pre- and post-processing. 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 token distribution, overlap proportion, expected retrieval granularity and vector count. 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 — A troubleshooting guide's symptom and resolution are in separate sections when cut every 400 characters. — is testing Semantic boundaries versus fixed-window chunks. 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 troubleshooting guide's symptom and resolution are in separate sections when cut every 400 characters. — is testing Semantic boundaries versus fixed-window chunks. 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. Compare intended answer fields to current indexed sources and freshness requirements. 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 troubleshooting guide's symptom and resolution are in separate sections when cut every 400 characters. — is testing Semantic boundaries versus fixed-window chunks. 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.