Databricks Certified Generative AI Engineer Associate Bundle

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.

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 — 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 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 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 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 — 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 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. 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 — An employee policy question needs a short deductible clause plus the adjacent exception paragraph. — is testing Parent-child retrieval and hierarchical structure. 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 — An employee policy question needs a short deductible clause plus the adjacent exception paragraph. — is testing Parent-child retrieval and hierarchical structure. 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 candidate-set recall, relevance scores, top-k cutoffs and added ranking latency. This action primarily relates to Cross-encoder reranking after candidate retrieval: A reranker scores query-document relevance over a candidate set; it improves ordering but does not add missing documents. However, the described case — An employee policy question needs a short deductible clause plus the adjacent exception paragraph. — is testing Parent-child retrieval and hierarchical structure. 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. Simulate quality and latency threshold breaches and confirm responsible owners receive alerts. 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 production team logs raw access tokens and complete customer chats when adding observability. — is testing Inference logging and production trace privacy. 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 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 production team logs raw access tokens and complete customer chats when adding observability. — is testing Inference logging and production trace privacy. 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 production team logs raw access tokens and complete customer chats when adding observability. — is testing Inference logging and production trace privacy. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Use 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 — An extraction model treats a quoted customer complaint as a command to ignore the required response shape. — is testing Instruction hierarchy and bounded prompt examples. 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. Define a schema-constrained prompt with field types, required keys and strict structured-output validation at the consumer. 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 — An extraction model treats a quoted customer complaint as a command to ignore the required response shape. — is testing Instruction hierarchy and bounded prompt examples. 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. Retrieve schedule and fare restrictions, solicit explicit confirmation, then invoke booking and record confirmation. 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 extraction model treats a quoted customer complaint as a command to ignore the required response shape. — is testing Instruction hierarchy and bounded prompt examples. 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 treat model fluency or demo satisfaction as a substitute for measurable business acceptance criteria. 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 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 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 use a document-answering assistant as an autonomous transaction engine without explicit tools and approvals. 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 — 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 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 authoritative structured values separate from explanatory unstructured content in the final answer. 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 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 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. Build a compatible new index and re-embed the corpus, then test cutover against representative queries. This action primarily relates to Embedding model swap and reindex compatibility: Changed embedding dimensions or model semantics typically require re-embedding and index consistency before comparing search quality. However, the described case — A large catalog's vector storage bill rises after selecting a high-dimensional encoder with no measured gain. — is testing Embedding dimensions latency and index storage. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

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

Not the strongest implement choice for this specific question. Select a suitable embedding model rather than treating generated prose as a numeric embedding. This action primarily relates to Specialized model versus general LLM: Embedding, reranking, extraction and generative models solve different stages and should be evaluated for their actual role. However, the described case — A large catalog's vector storage bill rises after selecting a high-dimensional encoder with no measured gain. — is testing Embedding dimensions latency and index storage. It does not directly establish the 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. 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 travel agent meets its average response time but p99 exceeds 30 seconds during peak traffic. — is testing Production performance KPIs and incident thresholds. 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 travel agent meets its average response time but p99 exceeds 30 seconds during peak traffic. — is testing Production performance KPIs and incident thresholds. 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. Re-evaluate previously disputed cases and confirm inter-rater agreement improves after calibration. This action primarily relates to Human SME feedback rubric and reviewer calibration: Domain experts should use a shared rubric, calibrate disagreements and maintain adjudicated examples to improve model evaluation. However, the described case — A travel agent meets its average response time but p99 exceeds 30 seconds during peak traffic. — is testing Production performance KPIs and incident thresholds. 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 — A RAG benchmark reports fluent final answers but no evidence of whether the right passage was retrieved. — is testing Retrieval recall precision and ranking diagnostics. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Compare hit recall and answer grounding for sample chunk sizes with a fixed query set. This action primarily relates to Chunk size and overlap tradeoffs: Chunk size determines the number of vectors and coherence; overlap reduces boundary loss but increases index size and cost. However, the described case — A RAG benchmark reports fluent final answers but no evidence of whether the right passage was retrieved. — is testing Retrieval recall precision and ranking diagnostics. 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 both rare identifiers and paraphrased questions with strict cross-tenant non-disclosure checks. 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 RAG benchmark reports fluent final answers but no evidence of whether the right passage was retrieved. — is testing Retrieval recall precision and ranking diagnostics. 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. Connect the authorized live shipment-tracking record keyed by order ID rather than guessing arrival from policy. 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 parts catalog stores component numbers as strings while retrieval loses manufacturer and model columns. — is testing Table-aware chunking and metadata-rich retrieval. 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. Limit parent expansion to an appropriate token budget to avoid irrelevant context dilution. 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 parts catalog stores component numbers as strings while retrieval loses manufacturer and model columns. — is testing Table-aware chunking and metadata-rich retrieval. 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. 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 compliance agent needs both a Unity Catalog table result and an approved policy passage for each answer. — 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. 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 compliance agent needs both a Unity Catalog table result and an approved policy passage for each answer. — 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. 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 — A compliance agent needs both a Unity Catalog table result and an approved policy passage for each answer. — 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.