Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest implement choice for this specific question. Benchmark lower-cost dimension options and choose one meeting retrieval recall and latency goals. This action primarily relates to Embedding dimensions latency and index storage: Embedding width affects index storage and computation, and larger dimensions do not automatically improve task relevance. However, the described case — A code assistant looks fast in demos but has low pass rate on the organization's test suite. — is testing Model evaluation with paired benchmarks. 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. Reject unsupported suitability assumptions and benchmark clinical-document handling with proper controls. This action primarily relates to Model cards and task-specific limitations: A model card records intended uses, supported language/context, safety limitations and evaluation scope relevant to selection. However, the described case — A code assistant looks fast in demos but has low pass rate on the organization's test suite. — is testing Model evaluation with paired benchmarks. 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 code assistant looks fast in demos but has low pass rate on the organization's test suite. — is testing Model evaluation with paired benchmarks. 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 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 website crawler indexes the same cookie banner thousands of times and retrieval returns banners above actual policy. — is testing Boilerplate and navigation filtering in source corpora. 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. Compare fixed evaluation queries on baseline and candidate retrieval with confidence in differences. 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 — A website crawler indexes the same cookie banner thousands of times and retrieval returns banners above actual policy. — is testing Boilerplate and navigation filtering in source corpora. 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. Verify that target retrieval returns complete condition-and-exception evidence for representative questions. This action primarily relates to Semantic boundaries versus fixed-window chunks: Headings, paragraphs and tables can require structure-aware splitting rather than arbitrary token windows. However, the described case — A website crawler indexes the same cookie banner thousands of times and retrieval returns banners above actual policy. — is testing Boilerplate and navigation filtering in source corpora. 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. Specify authorized user identity, question, relevant policy source and a cited answer or abstention as I/O contract. 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 compliance agent needs both a Unity Catalog table result and an approved policy passage for each answer. — is testing Parallel retrieval and deterministic chain postprocessing. 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 compliance agent needs both a Unity Catalog table result and an approved policy passage for each answer. — is testing Parallel retrieval and deterministic chain postprocessing. 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. Separate low-trust quoted input from higher-priority task instructions and include an example that preserves the schema. 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 compliance agent needs both a Unity Catalog table result and an approved policy passage for each answer. — is testing Parallel retrieval and deterministic chain postprocessing. 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 each judge's required inputs, reference fields, rubric and expected failure behavior. 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 — One department floods a shared foundation-model endpoint and starves other internal agents. — is testing AI Gateway rate limits, usage tables and inference telemetry. 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 — One department floods a shared foundation-model endpoint and starves other internal agents. — is testing AI Gateway rate limits, usage tables and inference telemetry. 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 production trace quality, error types, latency percentiles, user feedback and alert routes. 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 — One department floods a shared foundation-model endpoint and starves other internal agents. — is testing AI Gateway rate limits, usage tables and inference telemetry. 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 auth model, frontend token handling, backend endpoint calls and user-level data controls. This action primarily relates to Databricks Apps user-facing agent interface and OAuth identities: Databricks Apps supports authenticated interactive frontends; app credentials and user credentials have different scopes. However, the described case — A team persists all raw conversations in an unprotected shared cache to preserve agent memory. — is testing Persistent conversation memory with authorized datastore. 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 runtime invocation order, prompt input names, stage outputs and errors. This action primarily relates to Simple prompt-retrieval-generation chain assembly: A minimal chain composes a retriever, prompt, LLM and output parser, preserving required variables and failure states. However, the described case — A team persists all raw conversations in an unprotected shared cache to preserve agent memory. — is testing Persistent conversation memory with authorized datastore. 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 — A team persists all raw conversations in an unprotected shared cache to preserve agent memory. — is testing Persistent conversation memory with authorized datastore. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Run `mlflow.genai.evaluate()` on a fixed set with documented built-in and custom scorer outputs. 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 deployed claims assistant has 99.99% uptime but increasing incorrect eligibility advice. — is testing Production performance KPIs and incident thresholds. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Run paired experiments with consistent evaluation data and evaluate cost-quality Pareto tradeoffs. This action primarily relates to Model selection from quantitative task metrics: Select candidate LLMs by measured task success, latency, safety and token cost, not parameter count or leaderboard rank. However, the described case — A deployed claims assistant has 99.99% uptime but increasing incorrect eligibility advice. — is testing Production performance KPIs and incident thresholds. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Test a missing-ground-truth record to verify the judge abstains or uses the appropriate alternate scorer. This action primarily relates to Ground-truth requirement for correctness versus reference-free judges: A correctness comparison often needs an expected answer; other judges such as format or safety can operate without a reference. However, the described case — A deployed claims assistant has 99.99% uptime but increasing incorrect eligibility advice. — is testing Production performance KPIs and incident thresholds. 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 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 — A monthly reporting assistant processes thousands of independent documents overnight with low urgency. — is testing Latency, cost and retrieval targets as design requirements. 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 — A monthly reporting assistant processes thousands of independent documents overnight with low urgency. — is testing Latency, cost and retrieval targets as design requirements. 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 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 — A monthly reporting assistant processes thousands of independent documents overnight with low urgency. — is testing Latency, cost and retrieval targets as design requirements. 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. Apply moderation, require human review and restrict public-post tools to approved operators. 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 knowledge assistant embeds HR leave requests containing national IDs not needed for policy answers. — is testing Sensitive-field masking before embedding. 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. 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 knowledge assistant embeds HR leave requests containing national IDs not needed for policy answers. — is testing Sensitive-field masking before embedding. 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. Isolate source text in retrieval context and use backend authorization for ticket actions. 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 knowledge assistant embeds HR leave requests containing national IDs not needed for policy answers. — is testing Sensitive-field masking before embedding. It does not directly establish the implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Use `ai_query()` against a supported endpoint in a controlled batch-inference query with result checks. This action primarily relates to SQL ai_query for governed batch inference: `ai_query()` invokes an available serving endpoint from SQL; suitability depends on supported runtimes, endpoint and workload. However, the described case — A chat frontend embeds a service-principal secret directly into JavaScript to call the agent endpoint. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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. Store session state in a governed datastore keyed by the authenticated user and permitted ticket. 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 chat frontend embeds a service-principal secret directly into JavaScript to call the agent endpoint. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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 the managed Genie connector alongside a narrowly scoped custom MCP server for ticket actions. This action primarily relates to Managed versus external versus custom MCP server integration: MCP standardizes tool discovery; managed servers reduce hosting, external services need credentials and custom servers wrap bespoke actions. However, the described case — A chat frontend embeds a service-principal secret directly into JavaScript to call the agent endpoint. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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 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 medical appointment chatbot replaces all dates with redaction tokens, making scheduling answers impossible. — is testing Contextual masking versus destructive data removal. 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 filter decisions, action permissions, identity propagation and resulting audit events. 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 medical appointment chatbot replaces all dates with redaction tokens, making scheduling answers impossible. — is testing Contextual masking versus destructive data removal. 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 origin, prompt hierarchy, tool permissions and trace evidence of instruction-following attempts. 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 medical appointment chatbot replaces all dates with redaction tokens, making scheduling answers impossible. — is testing Contextual masking versus destructive data removal. 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 requires real external state, permitted action or just text transformation. 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 support assistant reveals hidden instructions when users ask it to ignore the normal helpdesk policy. — is testing Unsafe model output and jailbreak response diagnosis. 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 decoding parameters, expected output variance, schema requirements and task acceptance criteria. This action primarily relates to Temperature and deterministic format tradeoffs: Decoding settings can affect variability and cost but cannot replace validation, grounding or application logic. However, the described case — A support assistant reveals hidden instructions when users ask it to ignore the normal helpdesk policy. — is testing Unsafe model output and jailbreak response diagnosis. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect parsed intent, extracted keys, authorization check and actual query filter predicates. This action primarily relates to Query-field driven prompt and retrieval filters: User intent and structured fields such as account_id should drive authorized SQL lookups or retrieval filters, not be ignored in free text. However, the described case — A support assistant reveals hidden instructions when users ask it to ignore the normal helpdesk policy. — is testing Unsafe model output and jailbreak response diagnosis. 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.