Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest implement choice for this specific question. Call a structured order-status tool for transaction fields and retrieve policy text before composing a grounded response. 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 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. Configure a Knowledge Assistant over approved documents and validate source attribution and group permissions. 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 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 the equipment identifiers, failure observations and inventory query as required inputs, with approved part IDs as outputs. 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 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. 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 — An internal parts bot misses exact serial number ZX-410 because embeddings match only conceptual part descriptions. — is testing Hybrid sparse and dense retrieval with filters. 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 a frozen relevance dataset to prevent tuning to a single cherry-picked query. This action primarily relates to Retrieval recall precision and ranking diagnostics: Measure hit recall, precision, MRR or nDCG on labeled query-to-relevant-chunk pairs before tuning retrieval. However, the described case — An internal parts bot misses exact serial number ZX-410 because embeddings match only conceptual part descriptions. — is testing Hybrid sparse and dense retrieval with filters. 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. Choose coherent chunks large enough to keep cause and remedy together without exceeding embedding limits. 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 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 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. 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 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 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. 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 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. Recheck license and data handling when replacing proprietary with open-weight models. 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 declares a new assistant better but cannot identify which prompt or model version generated the winning score. — is testing Experiment tracking and version reproducibility. 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 use persuasive phrasing or a citation marker as evidence that a generated statement is true. 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 team declares a new assistant better but cannot identify which prompt or model version generated the winning score. — is testing Experiment tracking and version reproducibility. 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 team declares a new assistant better but cannot identify which prompt or model version generated the winning score. — is testing Experiment tracking and version reproducibility. 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. 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 — A product assistant must answer only for the model and country selected in the user form. — is testing Query-field driven prompt and retrieval filters. 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. Increase coherent chunk context or parent expansion, then compare answer coverage to the earlier chunking strategy. 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 product assistant must answer only for the model and country selected in the user form. — is testing Query-field driven prompt and retrieval filters. 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 the page as untrusted evidence and enforce tool authorization and destination allowlists on the server. This action primarily relates to Prompt-injection defenses for retrieved context: Retrieved content is lower-trust data; embedded instructions must not trigger privileged tool calls or override assistant rules. However, the described case — An employee asks first about leave policy, then about their leave balance, and the chain keeps searching policy text only. — is testing Conversation context and intent routing. 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. Retain a sampling and redaction policy for traces rather than logging raw secrets in production. 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 — An employee asks first about leave policy, then about their leave balance, and the chain keeps searching policy text only. — is testing Conversation context and intent routing. 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 query embedding provenance, index schema, similarity results and selected context window. 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 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 — 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 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 — 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 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. Design a precise instruction on evidence and uncertainty, then compare against baseline using the same evaluation set. This action primarily relates to Prompt changes evaluated against baseline: A prompt improvement should be measured against a fixed baseline set, not accepted because a few outputs sound better. 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 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. Review model license and select an authorized commercial alternative before deployment. 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 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 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 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 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 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 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 policy assistant begins making incorrect claims after the source index updates, but no live records show which index answered. — is testing Inference tables and Agent Monitoring feedback loop. 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 policy assistant begins making incorrect claims after the source index updates, but no live records show which index answered. — is testing Inference tables and Agent Monitoring feedback loop. 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 risk-based alert thresholds and sample protected user segments, not a single global average. 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 policy assistant begins making incorrect claims after the source index updates, but no live records show which index answered. — is testing Inference tables and Agent Monitoring feedback loop. 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. 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 search result includes fake 'system message' text requesting the assistant reveal private SQL results. — is testing Prompt-injection defenses for retrieved context. 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. Reproduce a slow/error case and confirm each relevant stage is observable without sensitive tokens. 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 search result includes fake 'system message' text requesting the assistant reveal private SQL results. — is testing Prompt-injection defenses for retrieved context. 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 mismatched user and account values and confirm zero unauthorized retrieval and correct contextual answers. 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 search result includes fake 'system message' text requesting the assistant reveal private SQL results. — is testing Prompt-injection defenses for retrieved context. 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. Differentiate direct identifiers from permissible temporal fields and apply purpose-specific protection. This action primarily relates to Contextual masking versus destructive data removal: Masking must preserve information needed for the task, such as non-sensitive dates or amounts, and cannot replace access control. However, the described case — A retrieved internal wiki page embeds a fake system instruction to grant an attacker access to all support tickets. — is testing Input guardrails against prompt-injected source documents. 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. Review license and reuse conditions and use authorized sources or link without copying protected text. 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 retrieved internal wiki page embeds a fake system instruction to grant an attacker access to all support tickets. — is testing Input guardrails against prompt-injected source documents. 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. Mask card numbers and nonessential identity fields before ingestion and keep approved case references separately. 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 retrieved internal wiki page embeds a fake system instruction to grant an attacker access to all support tickets. — is testing Input guardrails against prompt-injected source documents. 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.