Databricks Certified Generative AI Engineer Associate Bundle

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.

Not the strongest implement choice for this specific question. Strip template boilerplate, repeated navigation and low-information text before embedding. 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 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 by clause and heading boundaries with a token-aware fallback to preserve the rule and exception together. This action primarily relates to Semantic boundaries versus fixed-window chunks: Headings, paragraphs and tables can require structure-aware splitting rather than arbitrary token windows. However, the described case — A 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 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 tenant identity metadata filters before or during retrieval and use hybrid ranking within that scope. 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 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 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 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 — An internal assistant sends 40,000 irrelevant tokens to the LLM for every short FAQ question. — is testing Databricks usage and token cost controls. 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 internal assistant sends 40,000 irrelevant tokens to the LLM for every short FAQ question. — is testing Databricks usage and token cost controls. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect inference table availability, payload schemas, trace IDs and user-feedback mapping. This action primarily relates to Inference tables and Agent Monitoring feedback loop: Inference tables and agent monitoring capture production request/response signals and traces for quality investigations. However, the described case — An internal assistant sends 40,000 irrelevant tokens to the LLM for every short FAQ question. — is testing Databricks usage and token cost controls. 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 task difficulty, expected concurrency, context size, throughput and model benchmark evidence. 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 supply-chain assistant must call an inventory API before recommending an available replacement part. — is testing Agent tool wrappers versus direct LLM responses. 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 parsed intent, extracted keys, authorization check and actual query filter predicates. 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 supply-chain assistant must call an inventory API before recommending an available replacement part. — is testing Agent tool wrappers versus direct LLM responses. 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 supply-chain assistant must call an inventory API before recommending an available replacement part. — is testing Agent tool wrappers versus direct LLM responses. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Keep masking rules under regression control and treat embeddings and logs as potentially sensitive too. This action primarily relates to Sensitive-field masking before embedding: Masking or tokenization can remove unnecessary PII from chunks before embedding and external model calls while retaining useful meaning. However, the described case — A public review feed contains slurs and adversarial instructions that surface in a brand-support assistant. — is testing Toxic, inaccurate and adversarial corpus cleaning. 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. Obtain appropriate rights or replace manuals with licensed public documentation before ingestion. This action primarily relates to Training and retrieval corpus license rights: Public accessibility does not automatically authorize copying, embedding or using content in commercial RAG services. However, the described case — A public review feed contains slurs and adversarial instructions that surface in a brand-support assistant. — is testing Toxic, inaccurate and adversarial corpus cleaning. 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 monitoring schemas and retention governance versioned across model deployment changes. This action primarily relates to Inference tables and Agent Monitoring feedback loop: Inference tables and agent monitoring capture production request/response signals and traces for quality investigations. However, the described case — One department floods a shared foundation-model endpoint and starves other internal agents. — is testing AI Gateway rate limits, usage tables and inference telemetry. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Use usage monitoring and budgets to detect regressions when prompts, indexes or models change. 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 — One department floods a shared foundation-model endpoint and starves other internal agents. — is testing AI Gateway rate limits, usage tables and inference telemetry. 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 hide expert disagreement by excluding difficult cases or averaging away severe failures. 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 — One department floods a shared foundation-model endpoint and starves other internal agents. — is testing AI Gateway rate limits, usage tables and inference telemetry. 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 refund agent issues credits before verifying invoice status or refund eligibility. — is testing Tool ordering and error isolation in multi-stage reasoning. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Trigger a timeout then retry and verify only one approved action persists with a trace. This action primarily relates to Agent tool schemas, least privilege and retries: Well-described tool schemas constrain parameters, and idempotent retries prevent duplicate side effects. However, the described case — A refund agent issues credits before verifying invoice status or refund eligibility. — is testing Tool ordering and error isolation in multi-stage reasoning. 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 — A refund agent issues credits before verifying invoice status or refund eligibility. — is testing Tool ordering and error isolation in multi-stage reasoning. 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. Rerank a sufficiently broad candidate pool then pass a smaller high-relevance set to the LLM. 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 — 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 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 document-aware sections plus parent-child metadata to connect symptom to resolution. This action primarily relates to Semantic boundaries versus fixed-window chunks: Headings, paragraphs and tables can require structure-aware splitting rather than arbitrary token windows. However, the described case — A 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 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. Upsert chunk rows by stable document/version/chunk identifiers and delete stale rows under change control. 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 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 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. Require evidence-to-claim matching and refuse or correct answers unsupported by retrieved clauses. 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 brainstorming app wants creative draft ideas but is incorrectly evaluated on exact-string matching to one reference. — is testing Temperature and deterministic format tradeoffs. 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. Validate account and order IDs, enforce identity scope, and retrieve the matching order status before generation. 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 brainstorming app wants creative draft ideas but is incorrectly evaluated on exact-string matching to one reference. — is testing Temperature and deterministic format tradeoffs. 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. Maintain scoped conversation state and resolve the reference to a verified invoice identifier before lookup. 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 brainstorming app wants creative draft ideas but is incorrectly evaluated on exact-string matching to one reference. — is testing Temperature and deterministic format tradeoffs. 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 cherry-pick average metrics that hide severe high-impact task 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 — A multilingual agent is proposed using a model card that reports poor performance on the target language. — is testing Model cards and task-specific limitations. 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. 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 multilingual agent is proposed using a model card that reports poor performance on the target language. — is testing Model cards and task-specific limitations. 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 conversational answer generation separated from governed computation and source-of-truth queries. This action primarily relates to Multi-agent Genie Space tool routing and governed answers: Genie Spaces can provide governed natural-language access to structured business metrics; an agent should choose authorized Genie tools over guessing SQL facts. However, the described case — A multilingual agent is proposed using a model card that reports poor performance on the target language. — is testing Model cards and task-specific limitations. 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. Document legal clearance and confirm the deployed artifact matches the approved license/version. This action primarily relates to Open model license versus managed endpoint obligations: Model availability on a hub does not itself confer commercial training, redistribution or hosting rights. However, the described case — A team switches from a 768-dimensional embedding model to a 1024-dimensional model while keeping the same vector index. — is testing Embedding model swap and reindex compatibility. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Check embedding dimensions or extracted-field validation against task-specific acceptance tests. This action primarily relates to Specialized model versus general LLM: Embedding, reranking, extraction and generative models solve different stages and should be evaluated for their actual role. However, the described case — A team switches from a 768-dimensional embedding model to a 1024-dimensional model while keeping the same vector index. — is testing Embedding model swap and reindex compatibility. 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 team switches from a 768-dimensional embedding model to a 1024-dimensional model while keeping the same vector index. — is testing Embedding model swap and reindex compatibility. 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.