Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest implement choice for this specific question. Reject unauthorized tool requests through server-side permissions even if the model produces a valid tool call. 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 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 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. Provide a structured inventory lookup tool to the agent and ground the recommendation in its returned stock fields. This action primarily relates to Agent tool wrappers versus direct LLM responses: A tool-using agent needs explicit callable interfaces and typed tool results, whereas plain generation requires no action execution. 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 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. Route numerical KPI requests to the configured Genie Space then compose an answer from 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 — 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 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 team picks a model marked research-only and plans to deploy it for a paid product. — is testing Open model license versus managed endpoint obligations. 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. Log model/prompt/data identifiers and metrics to a run with reproducible evaluation artifacts. This action primarily relates to Experiment tracking and version reproducibility: MLflow experiments should retain prompt, model, dataset, parameters and evaluation outputs to support a defensible comparison. However, the described case — A team picks a model marked research-only and plans to deploy it for a paid product. — is testing Open model license versus managed endpoint obligations. 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. Evaluate capable long-context models on legal clauses and latency/cost acceptance thresholds. 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 team picks a model marked research-only and plans to deploy it for a paid product. — is testing Open model license versus managed endpoint obligations. 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. 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 agent receives a customer message requesting deletion of every table while only ticket lookup is authorized. — is testing Unsafe model output and jailbreak response diagnosis. 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. Grant only the tools required by the business workflow; general language understanding is not action authorization. This action primarily relates to Agent tool wrappers versus direct LLM responses: A tool-using agent needs explicit callable interfaces and typed tool results, whereas plain generation requires no action execution. However, the described case — An agent receives a customer message requesting deletion of every table while only ticket lookup is authorized. — is testing Unsafe model output and jailbreak response diagnosis. 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 — An agent receives a customer message requesting deletion of every table while only ticket lookup is authorized. — is testing Unsafe model output and jailbreak response diagnosis. 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 gateway policies, invocation identity, consumption tables, endpoint errors and supported feature availability. 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 support RAG app fails some answers, but team cannot tell whether retrieval or generation caused each error. — is testing MLflow GenAI tracing, built-in and custom scorers. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect task-appropriate quality metrics, inference cost, p95 latency and error segments. 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 support RAG app fails some answers, but team cannot tell whether retrieval or generation caused each error. — is testing MLflow GenAI tracing, built-in and custom scorers. 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 reviewer disagreement, rubric definitions, critical examples and adjudication notes. 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 support RAG app fails some answers, but team cannot tell whether retrieval or generation caused each error. — is testing MLflow GenAI tracing, built-in and custom scorers. 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. Choose asynchronous batch throughput and cost targets rather than paying for interactive latency. 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 CRM agent repeats a create-ticket tool call after a timeout, producing duplicate complaints. — is testing Agent tool schemas, least privilege and retries. 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. Join authorized structured values and retrieved policy context through a controlled composition stage. 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 CRM agent repeats a create-ticket tool call after a timeout, producing duplicate complaints. — is testing Agent tool schemas, least privilege and retries. 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 concise role instructions and representative input/output examples while keeping untrusted claim text in a delimited data section. This action primarily relates to Instruction hierarchy and bounded prompt examples: Few-shot examples and explicit boundaries can clarify expected outputs, but embedded source documents should not become new system instructions. However, the described case — A CRM agent repeats a create-ticket tool call after a timeout, producing duplicate complaints. — is testing Agent tool schemas, least privilege and retries. 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 predict entrypoint, model artifacts, dependency environment, inputs and output serialization. This action primarily relates to MLflow pyfunc packaging for pre- and post-processing: A custom MLflow pyfunc model wraps request parsing, retriever/model invocation and output formatting inside a reproducible predict interface. However, the described case — An agent must search an external research API requiring a secret, while internal company data uses managed connectors. — is testing Managed versus external versus custom MCP server integration. 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 — An agent must search an external research API requiring a secret, while internal company data uses managed connectors. — is testing Managed versus external versus custom MCP server integration. 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 agent must search an external research API requiring a secret, while internal company data uses managed connectors. — is testing Managed versus external versus custom MCP server integration. 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 model version, vector dimensions, index schema, pipeline lineage and freshness. 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 large catalog's vector storage bill rises after selecting a high-dimensional encoder with no measured gain. — is testing Embedding dimensions latency and index storage. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect required output type, input modality and measured task capability rather than model size alone. This action primarily relates to Specialized model versus general LLM: Embedding, reranking, extraction and generative models solve different stages and should be evaluated for their actual role. However, the described case — A large catalog's vector storage bill rises after selecting a high-dimensional encoder with no measured gain. — is testing Embedding dimensions latency and index storage. 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 encoder token limits, chunk length percentiles, truncation counters and source suffix omissions. 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 — A large catalog's vector storage bill rises after selecting a high-dimensional encoder with no measured gain. — is testing Embedding dimensions latency and index storage. 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 — A public browser sends a long-lived PAT directly to a model serving endpoint for each chat request. — is testing Model Serving endpoint permissions and caller identity. 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 public browser sends a long-lived PAT directly to a model serving endpoint for each chat request. — is testing Model Serving endpoint permissions and caller identity. 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 storage key design, user isolation, TTL/retention and retrieval authorization. This action primarily relates to Persistent conversation memory with authorized datastore: Transient prompt context differs from persistent user state; durable memory needs explicit storage, identity scope and retention. However, the described case — A public browser sends a long-lived PAT directly to a model serving endpoint for each chat request. — is testing Model Serving endpoint permissions and caller identity. 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. Test session resume for the same user and deny cross-user recall of private ticket details. This action primarily relates to Persistent conversation memory with authorized datastore: Transient prompt context differs from persistent user state; durable memory needs explicit storage, identity scope and retention. 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 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 a new source chunk and a retired chunk to confirm expected inclusion and removal. 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 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. Validate returned IDs, relevant scores and grounded answer citations on known reference queries. 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 verify 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 assume an instruction to 'respond in JSON' replaces actual schema validation and error handling. This action primarily relates to Structured JSON schema prompt and format compliance: A model can produce plausible prose rather than machine-readable JSON unless the output contract and validation are explicit. However, the described case — A claims assistant answers in different tones because the prompt has no consistent example or response constraints. — is testing Instruction hierarchy and bounded prompt examples. 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 absence of relevant retrieved evidence as an abstention condition, not a reason to invent missing facts. This action primarily relates to Retriever-generator chain component boundaries: A basic RAG chain separates user input, query transformation, retrieval, prompt assembly, model generation and output validation. However, the described case — A claims assistant answers in different tones because the prompt has no consistent example or response constraints. — is testing Instruction hierarchy and bounded prompt examples. 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 audit trails and constrain retries, tool permissions and approval for high-impact actions. 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 claims assistant answers in different tones because the prompt has no consistent example or response constraints. — is testing Instruction hierarchy and bounded prompt examples. 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. 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.