Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest implement choice for this specific question. Restrict endpoint CAN QUERY access to approved principals and test permission boundaries. 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 — An analyst must classify millions of rows overnight inside a governed Databricks SQL pipeline. — is testing SQL ai_query for governed batch inference. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Use an available Foundation Model API endpoint with compatible authentication, task API and quotas. This action primarily relates to Foundation Model API versus custom serving choices: Databricks Foundation Model APIs offer managed access to supported models; custom serving is suitable for specialized models or control needs. However, the described case — An analyst must classify millions of rows overnight inside a governed Databricks SQL pipeline. — is testing SQL ai_query for governed batch inference. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Combine semantic index search with model/tenant metadata filters and select source chunks for grounding. 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 — An analyst must classify millions of rows overnight inside a governed Databricks SQL pipeline. — is testing SQL ai_query for governed batch inference. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Trace retriever and generator spans, score passage relevance and answer faithfulness separately. This action primarily relates to MLflow GenAI tracing, built-in and custom scorers: MLflow GenAI traces capture components, and scorers/judges can evaluate a full answer or individual retrieval and tool spans. 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 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. Choose the candidate meeting the agreed citation-quality threshold and p95 latency with lower cost. 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 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 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. Escalate domain-expert evidence, revise the rubric and add the case to a protected regression set. 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 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 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. Expire or segregate conversation memory by identity and purpose, especially for financial and personal records. 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 — An engineer changes the source chunking but keeps old stored embeddings and assumes retrieval reflects the new boundaries. — is testing Embedding model swap and reindex compatibility. 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. Pin dependency and prompt schemas across releases so library updates do not silently break chain invocation. 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 — An engineer changes the source chunking but keeps old stored embeddings and assumes retrieval reflects the new boundaries. — is testing Embedding model swap and reindex compatibility. 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. Reassess tokenizer and context limits when switching embedding models or input languages. 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 — An engineer changes the source chunking but keeps old stored embeddings and assumes retrieval reflects the new boundaries. — is testing Embedding model swap and reindex compatibility. 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. Add groundedness and policy-error monitoring with escalation thresholds alongside latency. 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 batch classification job spikes costs because every row invokes a large general-purpose model. — is testing Databricks usage and token cost controls. 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. Build a custom code-based scorer checking required currency and amount fields alongside general quality judges. This action primarily relates to MLflow GenAI tracing, built-in and custom scorers: MLflow GenAI traces capture components, and scorers/judges can evaluate a full answer or individual retrieval and tool spans. However, the described case — A batch classification job spikes costs because every row invokes a large general-purpose model. — is testing Databricks usage and token cost controls. 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. Collect permitted feedback alongside inference traces and feed reviewed failures into a regression dataset. 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 batch classification job spikes costs because every row invokes a large general-purpose model. — is testing Databricks usage and token cost controls. 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. Choose the candidate meeting the agreed citation-quality threshold and p95 latency with lower cost. 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 medical expert flags unsafe triage advice, but engineering discards the feedback because an LLM judge rates it highly. — is testing Human SME feedback rubric and reviewer calibration. 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 a fit-for-task model, batching and usage thresholds with per-request cost monitoring. 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 medical expert flags unsafe triage advice, but engineering discards the feedback because an LLM judge rates it highly. — is testing Human SME feedback rubric and reviewer calibration. 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. 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 medical expert flags unsafe triage advice, but engineering discards the feedback because an LLM judge rates it highly. — is testing Human SME feedback rubric and reviewer calibration. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Revalidate model choice after volume or source-document shape changes materially. This action primarily relates to Model selection by quality latency and budget: Select the smallest suitable model that meets a task's accuracy and latency constraints under realistic workload, not marketing rank. However, the described case — A 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 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. Never trust an LLM-extracted customer identifier without server-side permission validation. 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 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 safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Keep component roles explicit so updates to a generation model do not silently alter retrieval vectors. This action primarily relates to Specialized model versus general LLM: Embedding, reranking, extraction and generative models solve different stages and should be evaluated for their actual role. However, the described case — A 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 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 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 — An Agent Framework service reports only end-to-end duration, hiding which tool call causes a 12-second delay. — is testing MLflow tracing in an Agent Framework workflow. 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 agent routing to Genie, space permissions, metric definitions and tool-returned values. 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 — An Agent Framework service reports only end-to-end duration, hiding which tool call causes a 12-second delay. — is testing MLflow tracing in an Agent Framework workflow. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect request/response sensitive spans, redaction logs, moderation findings and business exceptions. 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 — An Agent Framework service reports only end-to-end duration, hiding which tool call causes a 12-second delay. — is testing MLflow tracing in an Agent Framework workflow. 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. Do not equate an LLM judge score with unquestionable ground truth; calibrate against reviewed labels. This action primarily relates to MLflow GenAI tracing, built-in and custom scorers: MLflow GenAI traces capture components, and scorers/judges can evaluate a full answer or individual retrieval and tool spans. 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 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. Never assume diagnostics justify indefinite storage of unrestricted personal data or secrets. 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 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 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 — 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 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. Route documents by actual format and flag low-confidence extraction rather than silently indexing blank text. 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 — An order-support assistant knows return policy but cannot answer delivery ETA because shipment status is absent. — is testing Authoritative source coverage for factual answers. 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. Maintain row provenance and reject extraction transformations that detach numerical values from headers. 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 — An order-support assistant knows return policy but cannot answer delivery ETA because shipment status is absent. — is testing Authoritative source coverage for factual answers. 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. Select chunk granularity by measured retrieval results, not solely by minimizing index records. 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 — An order-support assistant knows return policy but cannot answer delivery ETA because shipment status is absent. — is testing Authoritative source coverage for factual answers. 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. Compare precision at k before and after cleaning while checking no required policy sentences were removed. This action primarily relates to Boilerplate and navigation filtering in source corpora: Duplicated headers, disclaimers and navigation menus contaminate embeddings and cause irrelevant hits. However, the described case — A regulatory standard contains nested headings, and isolated subclauses lose defined terms from the section header. — is testing Parent-child retrieval and hierarchical structure. 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 representative queries needing missing records and confirm either accurate retrieval or abstention. 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 regulatory standard contains nested headings, and isolated subclauses lose defined terms from the section header. — is testing Parent-child retrieval and hierarchical structure. 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. Sample pages/images against extracted text and check structured fields and layout fidelity. 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 regulatory standard contains nested headings, and isolated subclauses lose defined terms from the section header. — is testing Parent-child retrieval and hierarchical structure. 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. 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 troubleshooting guide's symptom and resolution are in separate sections when cut every 400 characters. — is testing Semantic boundaries versus fixed-window chunks. 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. Combine keyword matching and vector similarity with model/tenant filters and calibrated score fusion. 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 troubleshooting guide's symptom and resolution are in separate sections when cut every 400 characters. — is testing Semantic boundaries versus fixed-window chunks. 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. Remove repeated footer noise while preserving meaningful classification metadata separately. 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 troubleshooting guide's symptom and resolution are in separate sections when cut every 400 characters. — is testing Semantic boundaries versus fixed-window chunks. 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.