Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest implement choice for this specific question. Deploy synchronized index definitions and validate source freshness during production cutover. 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 — An agent produces raw document objects but the serving client expects a JSON list of cited answers. — is testing MLflow pyfunc packaging for pre- and post-processing. 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 `ai_query()` against a supported endpoint in a controlled batch-inference query with result checks. This action primarily relates to SQL ai_query for governed batch inference: `ai_query()` invokes an available serving endpoint from SQL; suitability depends on supported runtimes, endpoint and workload. However, the described case — An agent produces raw document objects but the serving client expects a JSON list of cited answers. — is testing MLflow pyfunc packaging for pre- and post-processing. 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 — An agent produces raw document objects but the serving client expects a JSON list of cited answers. — is testing MLflow pyfunc packaging for pre- and post-processing. 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. Classify current turn intent and route balances to authorized structured lookup rather than policy-only search. This action primarily relates to Conversation context and intent routing: Multi-turn assistants need explicit conversational state while routing each new request to the correct tool or topic. However, the described case — A support assistant reveals hidden instructions when users ask it to ignore the normal helpdesk policy. — is testing Unsafe model output and jailbreak response diagnosis. 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. Apply appropriate output moderation and escalation for unsafe responses while retaining audit evidence. 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 support assistant reveals hidden instructions when users ask it to ignore the normal helpdesk policy. — is testing Unsafe model output and jailbreak response diagnosis. 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. Isolate instructions from source text and reject cross-trust-boundary requests through policy/tool checks. This action primarily relates to Prompt-injection defenses for retrieved context: Retrieved content is lower-trust data; embedded instructions must not trigger privileged tool calls or override assistant rules. However, the described case — A support assistant reveals hidden instructions when users ask it to ignore the normal helpdesk policy. — is testing Unsafe model output and jailbreak response diagnosis. 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. Do not mistake text masking for permission checks, lawful data use or complete safety assurance. 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 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. Keep component roles explicit so updates to a generation model do not silently alter retrieval vectors. 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 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 treat a model hub popularity score as certification of deployment fitness. 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 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 section relationships, chunk hierarchy and whether cross-references survive extraction. 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 — A support search returns five unrelated policy pages while the correct refund clause is at rank 20. — is testing Retrieval recall precision and ranking diagnostics. 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 lexical token overlap, dense distance, metadata predicates and index access control. This action primarily relates to Hybrid sparse and dense retrieval with filters: Hybrid search combines lexical exact-match and semantic similarity; metadata filtering narrows authorized relevant content. However, the described case — A support search returns five unrelated policy pages while the correct refund clause is at rank 20. — is testing Retrieval recall precision and ranking diagnostics. 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 table extraction, repeated column headings, units, row identity and exact filter fields. 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 — A support search returns five unrelated policy pages while the correct refund clause is at rank 20. — is testing Retrieval recall precision and ranking diagnostics. 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 proposed tool call sequence, preconditions, approval gates and partial failures. This action primarily relates to Tool ordering and error isolation in multi-stage reasoning: An agent should retrieve authoritative context before taking consequential actions and validate tool outcomes at each stage. However, the described case — An internal service team wants a citation-backed chat over equipment procedures without writing a custom agent framework. — is testing Agent Bricks Knowledge Assistant suitability. 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 volume, concurrency, response deadline, token budget and evaluation quality targets. 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 internal service team wants a citation-backed chat over equipment procedures without writing a custom agent framework. — is testing Agent Bricks Knowledge Assistant suitability. 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 each source connector's contract, join keys, runtime error handling and the final prompt inputs. 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 — An internal service team wants a citation-backed chat over equipment procedures without writing a custom agent framework. — is testing Agent Bricks Knowledge Assistant suitability. 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. 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 public application generates harmful abusive content after an unusual user prompt despite sanitized inputs. — is testing PII masking and output moderation as complementary guardrails. 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 mismatched user and account values and confirm zero unauthorized retrieval and correct contextual answers. This action primarily relates to Query-field driven prompt and retrieval filters: User intent and structured fields such as account_id should drive authorized SQL lookups or retrieval filters, not be ignored in free text. However, the described case — A public application generates harmful abusive content after an unusual user prompt despite sanitized inputs. — is testing PII masking and output moderation as complementary guardrails. 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 repeated generations against the task rubric and format parser to detect unwanted drift. 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 public application generates harmful abusive content after an unusual user prompt despite sanitized inputs. — is testing PII masking and output moderation as complementary guardrails. 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. Benchmark a supported index type and provision for the expected vector count, latency and update pattern. This action primarily relates to Standard versus storage-optimized Vector Search index: Index choice trades capacity, update speed, latency and storage economics; availability and feature support may vary by cloud/region. However, the described case — A legacy SQL Classic warehouse cannot run a new `ai_query()` workload and engineers assume bad model credentials. — is testing SQL ai_query for governed batch inference. 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. Pin compatible dependencies and rebuild/evaluate the serving artifact before promoting a new environment. 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 legacy SQL Classic warehouse cannot run a new `ai_query()` workload and engineers assume bad model credentials. — is testing SQL ai_query for governed batch inference. 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. Move inference calls and secrets to the server-side app, using appropriate app/user authorization. This action primarily relates to Databricks Apps user-facing agent interface and OAuth identities: Databricks Apps supports authenticated interactive frontends; app credentials and user credentials have different scopes. However, the described case — A legacy SQL Classic warehouse cannot run a new `ai_query()` workload and engineers assume bad model credentials. — is testing SQL ai_query for governed batch inference. 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. Revalidate model choice after volume or source-document shape changes materially. This action primarily relates to Model selection by quality latency and budget: Select the smallest suitable model that meets a task's accuracy and latency constraints under realistic workload, not marketing rank. However, the described case — A team uses a text-generation endpoint to return a fixed-size vector for semantic similarity search. — is testing Specialized model versus general LLM. 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. Revise few-shot examples for format compliance and rerun previously passing examples. This action primarily relates to Prompt changes evaluated against baseline: A prompt improvement should be measured against a fixed baseline set, not accepted because a few outputs sound better. However, the described case — A team uses a text-generation endpoint to return a fixed-size vector for semantic similarity search. — is testing Specialized model versus general LLM. 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. Withhold one source during testing and confirm the chain degrades safely rather than inventing a missing record. 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 monthly reporting assistant processes thousands of independent documents overnight with low urgency. — is testing Latency, cost and retrieval targets as design requirements. 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 malformed inputs and inspect whether every response satisfies the parser and required field contract. 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 monthly reporting assistant processes thousands of independent documents overnight with low urgency. — is testing Latency, cost and retrieval targets as design requirements. 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 extracted schema completeness or supervisor routing correctness on representative multi-step cases. 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 monthly reporting assistant processes thousands of independent documents overnight with low urgency. — is testing Latency, cost and retrieval targets as design requirements. 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 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 policy assistant begins making incorrect claims after the source index updates, but no live records show which index answered. — 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 policy assistant begins making incorrect claims after the source index updates, but no live records show which index answered. — 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 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 policy assistant begins making incorrect claims after the source index updates, but no live records show which index answered. — 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 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 — Hybrid search retrieves the right troubleshooting note at rank 18 yet generation uses only the first five hits. — is testing Cross-encoder reranking after candidate retrieval. 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 — Hybrid search retrieves the right troubleshooting note at rank 18 yet generation uses only the first five hits. — is testing Cross-encoder reranking after candidate retrieval. 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 — Hybrid search retrieves the right troubleshooting note at rank 18 yet generation uses only the first five hits. — is testing Cross-encoder reranking after candidate retrieval. 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.