Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest safeguard choice for this specific question. Do not present nearest neighbors as verified answers without evidence validation and permission checks. This action primarily relates to Vector Search retrieval workflow and query integration: Semantic retrieval uses an embedding model to query a compatible index, returns ranked passages and metadata for grounded generation. However, the described case — A team promotes a new prompt without rerunning citation accuracy or tool-permission regression cases. — is testing CI/CD pipelines for retrieval and agent components. 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. Enforce reproducible environment manifests and API compatibility checks in CI/CD. 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 team promotes a new prompt without rerunning citation accuracy or tool-permission regression cases. — is testing CI/CD pipelines for retrieval and agent components. 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. Treat index freshness as a monitored dependency of source-document correctness. This action primarily relates to Databricks Vector Search index from governed Delta data: A vector index serves embeddings of chunked records maintained in a Unity Catalog governed Delta source table. However, the described case — A team promotes a new prompt without rerunning citation accuracy or tool-permission regression cases. — is testing CI/CD pipelines for retrieval and agent components. 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 request logging or gateway authentication as proof that underlying data access is authorized. 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 chatbot owner demands exact reference-match scoring for open-ended helpfulness with many valid phrasings. — is testing Ground-truth requirement for correctness versus reference-free judges. 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 — A chatbot owner demands exact reference-match scoring for open-ended helpfulness with many valid phrasings. — is testing Ground-truth requirement for correctness versus reference-free judges. 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 — A chatbot owner demands exact reference-match scoring for open-ended helpfulness with many valid phrasings. — is testing Ground-truth requirement for correctness versus reference-free judges. 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 CI gate for prompt schema, retrieval relevance, agent tools and controlled promotion across environments. This action primarily relates to CI/CD pipelines for retrieval and agent components: Production promotions should test source index, prompt, model packaging and tool behavior independently before release. However, the described case — An agent needs governed Genie metrics plus a company-only ticket system exposed through a custom API. — is testing Managed versus external versus custom MCP server integration. 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. Compare storage-optimized versus standard options, supported limits and actual query latency before selection. 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 — An agent needs governed Genie metrics plus a company-only ticket system exposed through a custom API. — is testing Managed versus external versus custom MCP server integration. 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 needs governed Genie metrics plus a company-only ticket system exposed through a custom API. — is testing Managed versus external versus custom MCP server integration. 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 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 benefits RAG assistant cites a real policy page but its claimed deadline does not appear in the cited passage. — is testing Hallucinated facts and unsupported citations. 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 benefits RAG assistant cites a real policy page but its claimed deadline does not appear in the cited passage. — is testing Hallucinated facts and unsupported citations. 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 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 benefits RAG assistant cites a real policy page but its claimed deadline does not appear in the cited passage. — is testing Hallucinated facts and unsupported citations. 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 warehouse type, runtime compatibility, endpoint status, SQL arguments and batch size. 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 — A research archive contains hundreds of millions of mostly static embeddings and storage cost is the main constraint. — is testing Standard versus storage-optimized Vector Search index. 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 logged model artifacts, environment requirements, signature and source index identifiers. This action primarily relates to RAG production bundle metadata and dependencies: A deployable RAG application needs tracked model code, retriever config, embedding model, dependency versions, signature and example input. However, the described case — A research archive contains hundreds of millions of mostly static embeddings and storage cost is the main constraint. — is testing Standard versus storage-optimized Vector Search index. 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 server type, endpoint URL, supported auth, tool declarations and available scopes. This action primarily relates to Managed versus external versus custom MCP server integration: MCP standardizes tool discovery; managed servers reduce hosting, external services need credentials and custom servers wrap bespoke actions. However, the described case — A research archive contains hundreds of millions of mostly static embeddings and storage cost is the main constraint. — is testing Standard versus storage-optimized Vector Search index. 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. 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 long regulation section exceeds an encoder's limit and the final exception is never embedded. — is testing Embedding context window and chunk token distribution. 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 long regulation section exceeds an encoder's limit and the final exception is never embedded. — is testing Embedding context window and chunk token distribution. 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 representative requests and record quality versus p95 latency and cost tradeoffs. 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 long regulation section exceeds an encoder's limit and the final exception is never embedded. — is testing Embedding context window and chunk token distribution. 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 logged model artifacts, environment requirements, signature and source index identifiers. 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 — New policies appear in Delta but a manually managed embedding index still returns retired versions. — is testing Databricks Vector Search index from governed Delta data. 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 — New policies appear in Delta but a manually managed embedding index still returns retired versions. — is testing Databricks Vector Search index from governed Delta data. 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 UC model names, signatures, version metadata, lineage and relevant ACLs. 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 — New policies appear in Delta but a manually managed embedding index still returns retired versions. — is testing Databricks Vector Search index from governed Delta data. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect evaluation data composition, judge criteria, run configuration and sampled failures. This action primarily relates to Model evaluation with paired benchmarks: Accuracy, faithfulness, relevance and refusal behavior require task-specific scoring, and a model switch needs common test conditions. However, the described case — 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 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 vector count, dimension, encoder throughput, per-query latency and measured quality curves. 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 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 adversarial prompt examples, tool permissions and whether refusals are enforced outside the model. 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 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. 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 simple meeting recap bot is configured with payment and email tools despite only needing a text summary. — is testing Agent tool wrappers versus direct LLM responses. 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. Enforce policy-layer refusals and prevent disclosure through prompt and output checks without relying on wording alone. 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 — A simple meeting recap bot is configured with payment and email tools despite only needing a text summary. — is testing Agent tool wrappers versus direct LLM responses. 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 simple meeting recap bot is configured with payment and email tools despite only needing a text summary. — is testing Agent tool wrappers versus direct LLM responses. 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 cited spans, source freshness, answer claims and missing-reference patterns. 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 customer success supervisor agent must answer revenue questions from governed sales tables and draft a recommendation. — is testing Multi-agent Genie Space tool routing and governed answers. 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 nested traces, span order, tool duration and captured payload security. This action primarily relates to MLflow tracing in an Agent Framework workflow: MLflow tracing records agent steps, tool calls and latency; integration must retain child spans and inputs without leaking secrets. However, the described case — A customer success supervisor agent must answer revenue questions from governed sales tables and draft a recommendation. — is testing Multi-agent Genie Space tool routing and governed answers. 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 customer success supervisor agent must answer revenue questions from governed sales tables and draft a recommendation. — is testing Multi-agent Genie Space tool routing and governed answers. 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. 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.