Databricks Certified Generative AI Engineer Associate Bundle

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 low-cost support search uses short chunks but the proposed model multiplies embedding dimensions by eight. — is testing Embedding dimensions latency and index storage. 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 low-cost support search uses short chunks but the proposed model multiplies embedding dimensions by eight. — is testing Embedding dimensions latency and index storage. 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. Version embeddings with source and model identifiers to prevent silently mixing incompatible representations. 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 low-cost support search uses short chunks but the proposed model multiplies embedding dimensions by eight. — is testing Embedding dimensions latency and index storage. 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 grant the model blanket tool permission based only on a safe-looking input text score. This action primarily relates to Prompt safety filtering and tool allowlists: Content filters and action allowlists are complementary; a moderation score is not a substitute for authorization of external effects. However, the described case — A startup scrapes a paid technical manual site into its product RAG index despite restrictive subscription terms. — is testing Training and retrieval corpus license rights. 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. Retest adversarial sources after adding new file types and tool connectors. This action primarily relates to Input guardrails against prompt-injected source documents: A document that says 'ignore your rules' is untrusted data; a robust agent must enforce instruction and tool boundaries independently. However, the described case — A startup scrapes a paid technical manual site into its product RAG index despite restrictive subscription terms. — is testing Training and retrieval corpus license rights. 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 human review for borderline filtering decisions so source cleaning does not silently erase important warnings. This action primarily relates to Toxic, inaccurate and adversarial corpus cleaning: Unreliable source text can teach unsafe behavior through retrieval; quarantine and source review matter before embeddings. However, the described case — A startup scrapes a paid technical manual site into its product RAG index despite restrictive subscription terms. — is testing Training and retrieval corpus license rights. 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. Favor the architecture meeting field accuracy and throughput constraints rather than model size. 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 — 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 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. Add validated reference answers or use a reference-free groundedness criterion with clear scope. 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 — 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 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 — 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 implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Test a topic switch and anaphoric reference to ensure correct routing and no cross-session state bleed. 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 RAG assistant passes an internal evaluation set but receives complaints about new policy terms after launch. — is testing Offline evaluation versus ongoing production monitoring. 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 RAG assistant passes an internal evaluation set but receives complaints about new policy terms after launch. — is testing Offline evaluation versus ongoing production monitoring. 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. 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 RAG assistant passes an internal evaluation set but receives complaints about new policy terms after launch. — is testing Offline evaluation versus ongoing production monitoring. 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. Query for known synthetic sensitive strings and confirm no original identifiers appear in chunks or answers. 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 customer agent is allowed to issue account refunds but a hostile chat asks it to refund unrelated accounts. — is testing Prompt safety filtering and tool allowlists. 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 harmful queries and verify contaminated passages are blocked without discarding legitimate safety instructions. This action primarily relates to Toxic, inaccurate and adversarial corpus cleaning: Unreliable source text can teach unsafe behavior through retrieval; quarantine and source review matter before embeddings. However, the described case — A customer agent is allowed to issue account refunds but a hostile chat asks it to refund unrelated accounts. — is testing Prompt safety filtering and tool allowlists. 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. Inject the hostile PDF and verify no secret leaves the backend and no unauthorized tool is invoked. This action primarily relates to Input guardrails against prompt-injected source documents: A document that says 'ignore your rules' is untrusted data; a robust agent must enforce instruction and tool boundaries independently. However, the described case — A customer agent is allowed to issue account refunds but a hostile chat asks it to refund unrelated accounts. — is testing Prompt safety filtering and tool allowlists. 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 the prompt hierarchy, few-shot coverage, untrusted-data delimiters and observed format deviations. 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 — An IT assistant can read service status but its generic tool credentials also allow deletion of production tables. — is testing Agent tool schemas, least privilege and retries. 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 whether the task is grounded document Q&A, extraction, tool coordination or cross-agent orchestration. 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 — An IT assistant can read service status but its generic tool credentials also allow deletion of production tables. — is testing Agent tool schemas, least privilege and retries. 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 each source connector's contract, join keys, runtime error handling and the final prompt inputs. 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 — An IT assistant can read service status but its generic tool credentials also allow deletion of production tables. — is testing Agent tool schemas, least privilege and retries. 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 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 — An internal employee portal wants a Streamlit RAG chat UI over governed policy and private team data. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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 source table, index type, embedding model, index status and last successful sync. 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 — An internal employee portal wants a Streamlit RAG chat UI over governed policy and private team data. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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 serving endpoint permissions, token path, user/app identity and downstream Unity Catalog access. 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 internal employee portal wants a Streamlit RAG chat UI over governed policy and private team data. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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. Load the registered bundle in a clean environment and validate retrieval-to-generation behavior end to end. 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 new Vector Search index is created in staging but production points at its previous source table version. — is testing CI/CD pipelines for retrieval and agent components. 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 model invocation under realistic throughput and verify output schema, quota and governance constraints. 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 — A new Vector Search index is created in staging but production points at its previous source table version. — is testing CI/CD pipelines for retrieval and agent components. 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. Load an explicitly registered version and confirm its dependencies and outputs match the approved evaluation run. 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 — A new Vector Search index is created in staging but production points at its previous source table version. — is testing CI/CD pipelines for retrieval and agent components. 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 flagged passages, content provenance, approval status and observed retrieval matches. This action primarily relates to Toxic, inaccurate and adversarial corpus cleaning: Unreliable source text can teach unsafe behavior through retrieval; quarantine and source review matter before embeddings. 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 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 extraction fields, masking policy, downstream embedded text and sensitive-data exposure paths. 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 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 content provenance, licensing terms, rights reservations and intended distribution. 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 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 attribute an absent document to reranking failure if the first-stage search never returned it. 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 research bot reports outdated product prices because the indexed catalog is a quarterly snapshot. — 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. Version preprocessing rules and sample exceptions so cleansing never strips legal requirements. 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 research bot reports outdated product prices because the indexed catalog is a quarterly snapshot. — 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. Never assume embedding similarity alone is a security boundary or reliable exact identifier lookup. 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 research bot reports outdated product prices because the indexed catalog is a quarterly snapshot. — 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 implement choice for this specific question. Split read-only diagnostic tools from authorized destructive operations with separate permissions. 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 repairs workflow wants parts suggestions but does not state which serial number, failure code or stock fields matter. — is testing Translate use-case requirements into pipeline inputs and outputs. 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. Order identity verification, purchase lookup, policy check, user confirmation and transaction tool invocation. This action primarily relates to Tool ordering and error isolation in multi-stage reasoning: An agent should retrieve authoritative context before taking consequential actions and validate tool outcomes at each stage. However, the described case — A repairs workflow wants parts suggestions but does not state which serial number, failure code or stock fields matter. — is testing Translate use-case requirements into pipeline inputs and outputs. 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. Translate SLA into retrieval latency, time-to-first-token, maximum context and quality floor for candidate designs. This action primarily relates to Latency, cost and retrieval targets as design requirements: A valid pipeline design has measurable quality, latency, token and throughput constraints before model selection. However, the described case — A repairs workflow wants parts suggestions but does not state which serial number, failure code or stock fields matter. — is testing Translate use-case requirements into pipeline inputs and outputs. 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.