Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest verify choice for this specific question. Run paired experiments with consistent evaluation data and evaluate cost-quality Pareto tradeoffs. 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 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 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 a missing-ground-truth record to verify the judge abstains or uses the appropriate alternate scorer. 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 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 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. Benchmark per-answer cost and quality on representative traffic before promoting optimizations. 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 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 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 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 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 allowed and denied principals against both endpoint invocation and protected retrieval data. This action primarily relates to Model Serving endpoint permissions and caller identity: Access to a serving endpoint is governed by workspace rights and identity; caller authorization is distinct from data-source permissions. 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 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 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 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-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 HR help desk says it wants 'AI answers' without specifying which employee documents users may see. — is testing Translate use-case requirements into pipeline inputs and outputs. 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. Inspect a full trace to confirm retrieved evidence and user intent reach the model and that citations point to real chunks. 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 — An HR help desk says it wants 'AI answers' without specifying which employee documents users may see. — is testing Translate use-case requirements into pipeline inputs and outputs. 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 answer fidelity, citation paths and forbidden document access across test identities. This action primarily relates to Agent Bricks Knowledge Assistant suitability: A governed knowledge assistant grounds conversational responses in curated documents and access-controlled retrieval. However, the described case — An HR help desk says it wants 'AI answers' without specifying which employee documents users may see. — is testing Translate use-case requirements into pipeline inputs and outputs. 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 fraud triage team needs a fixed risk category for each ticket, not a newly written customer letter. — is testing Task choice: classification versus generative summarization. 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. Inspect a full trace to confirm retrieved evidence and user intent reach the model and that citations point to real chunks. 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 fraud triage team needs a fixed risk category for each ticket, not a newly written customer letter. — is testing Task choice: classification versus generative summarization. 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 fraud triage team needs a fixed risk category for each ticket, not a newly written customer letter. — is testing Task choice: classification versus generative summarization. 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. Enable approved inference tracing/logging with request IDs, redaction and retrieval metadata. 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 support RAG app fails some answers, but team cannot tell whether retrieval or generation caused each error. — is testing MLflow GenAI tracing, built-in and custom scorers. 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. Add validated reference answers or use a reference-free groundedness criterion with clear scope. 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 support RAG app fails some answers, but team cannot tell whether retrieval or generation caused each error. — is testing MLflow GenAI tracing, built-in and custom scorers. 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. Limit retrieved context by relevance and compare answer faithfulness before switching to a smaller endpoint. 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 support RAG app fails some answers, but team cannot tell whether retrieval or generation caused each error. — is testing MLflow GenAI tracing, built-in and custom scorers. 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 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 300-page maintenance manual is cut into tiny fragments and the retrieved snippet omits the cause-and-remedy pair. — is testing Chunk size and overlap tradeoffs. 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 MIME types, text-layer availability, encoding and parsing failures per source. 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 — A 300-page maintenance manual is cut into tiny fragments and the retrieved snippet omits the cause-and-remedy pair. — is testing Chunk size and overlap tradeoffs. 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 300-page maintenance manual is cut into tiny fragments and the retrieved snippet omits the cause-and-remedy pair. — is testing Chunk size and overlap tradeoffs. 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. Inspect a full trace to confirm retrieved evidence and user intent reach the model and that citations point to real chunks. 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 claims assistant answers in different tones because the prompt has no consistent example or response constraints. — is testing Instruction hierarchy and bounded prompt examples. 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 claims assistant answers in different tones because the prompt has no consistent example or response constraints. — is testing Instruction hierarchy and bounded prompt examples. 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 — A claims assistant answers in different tones because the prompt has no consistent example or response constraints. — is testing Instruction hierarchy and bounded prompt examples. 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. Inspect a full trace to confirm retrieved evidence and user intent reach the model and that citations point to real chunks. 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 — 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 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. 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 — 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 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 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 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. A/B test chunk segmentation on frozen questions and verify evidence sufficiency and prompt-budget compliance. 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 — A ledger explanation app needs repeatable short outputs, but developers increase temperature to make wording more creative. — is testing Temperature and deterministic format tradeoffs. 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 unavailable-inventory case to verify the assistant checks tool output and does not fabricate stock. This action primarily relates to Agent tool wrappers versus direct LLM responses: A tool-using agent needs explicit callable interfaces and typed tool results, whereas plain generation requires no action execution. However, the described case — A ledger explanation app needs repeatable short outputs, but developers increase temperature to make wording more creative. — is testing Temperature and deterministic format tradeoffs. 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 reproducible pairwise experiments with confidence and segment-level result analysis. 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 — A ledger explanation app needs repeatable short outputs, but developers increase temperature to make wording more creative. — is testing Temperature and deterministic format tradeoffs. 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 package lockfile, model signature, serving logs and API contract differences. 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 prototype RAG agent works on one notebook cluster but fails because its deployment package omits the vector search client dependency. — is testing RAG production bundle metadata and dependencies. 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 capacity caps, sync behavior, qps, p95 latency and expected update cost. 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 prototype RAG agent works on one notebook cluster but fails because its deployment package omits the vector search client dependency. — is testing RAG production bundle metadata and dependencies. 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 auth model, frontend token handling, backend endpoint calls and user-level data controls. 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 prototype RAG agent works on one notebook cluster but fails because its deployment package omits the vector search client dependency. — is testing RAG production bundle metadata and dependencies. 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 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 — Repeated evaluation of one agent produces conflicting reports because source-document snapshots differ. — is testing Experiment tracking and version reproducibility. 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. Keep the retriever as an independent runnable stage and swap model components under the same interface. 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 — Repeated evaluation of one agent produces conflicting reports because source-document snapshots differ. — is testing Experiment tracking and version reproducibility. 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. Reject unauthorized tool requests through server-side permissions even if the model produces a valid tool call. This action primarily relates to Unsafe model output and jailbreak response diagnosis: User-provided instructions may attempt to bypass agent policies or cause data leakage; classification and tool boundaries need separate tests. However, the described case — Repeated evaluation of one agent produces conflicting reports because source-document snapshots differ. — is testing Experiment tracking and version reproducibility. 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.