Databricks Certified Generative AI Engineer Associate Bundle

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.

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 — An agent needs governed Genie metrics plus a company-only ticket system exposed through a custom API. — is testing Managed versus external versus custom MCP server integration. 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. Sign in as two users with different UC rights and confirm their answers cannot expose each other's data. 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 — An agent needs governed Genie metrics plus a company-only ticket system exposed through a custom API. — is testing Managed versus external versus custom MCP server integration. 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 — An agent needs governed Genie metrics plus a company-only ticket system exposed through a custom API. — is testing Managed versus external versus custom MCP server integration. 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 highest dimensionality is best; maintain index compatibility when changing dimension. 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 legal contract review agent needs nuanced long-context reasoning but can tolerate higher response time. — is testing Model selection by quality latency and budget. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Reassess tokenizer and context limits when switching embedding models or input languages. This action primarily relates to Embedding context window and chunk token distribution: The embedding encoder must accept the actual tokenized chunk length; silently truncating chunks can drop relevant suffix facts. However, the described case — A legal contract review agent needs nuanced long-context reasoning but can tolerate higher response time. — is testing Model selection by quality latency and budget. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Do not treat a model hub popularity score as certification of deployment fitness. 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 legal contract review agent needs nuanced long-context reasoning but can tolerate higher response time. — is testing Model selection by quality latency and budget. 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 the business decision, data owners, actor permissions, known inputs and success criteria. 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 — An order-status assistant needs real-time package state plus the carrier's public shipping policy. — is testing Parallel retrieval and deterministic chain postprocessing. 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 — An order-status assistant needs real-time package state plus the carrier's public shipping policy. — is testing Parallel retrieval and deterministic chain postprocessing. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect request volume, concurrency, response deadline, token budget and evaluation quality targets. 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 — An order-status assistant needs real-time package state plus the carrier's public shipping policy. — is testing Parallel retrieval and deterministic chain postprocessing. 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. 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 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 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. Invoke the chain with a representative dictionary and check all intermediate variable mappings and final output. This action primarily relates to LangChain runnable composition and invocation: Composable runnable chains pass typed values between retrieval, prompt and model stages; each binding must preserve expected input keys. However, the described case — 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 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 side-by-side evaluations for baseline and candidate prompts with format, groundedness and latency metrics. 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 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 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. Log the app with dependency requirements, retrieval configuration, model signature and example requests. 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 support agent times out at peak demand because requests exceed the configured endpoint throughput. — is testing Endpoint scale concurrency and operational rollout. 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 access-controlled persistent storage with retention and sensitive-field minimization. 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 support agent times out at peak demand because requests exceed the configured endpoint throughput. — is testing Endpoint scale concurrency and operational rollout. 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. Restrict endpoint CAN QUERY access to approved principals and test permission boundaries. This action primarily relates to Model Serving endpoint permissions and caller identity: Access to a serving endpoint is governed by workspace rights and identity; caller authorization is distinct from data-source permissions. However, the described case — A support agent times out at peak demand because requests exceed the configured endpoint throughput. — is testing Endpoint scale concurrency and operational rollout. 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. Never assume diagnostics justify indefinite storage of unrestricted personal data or secrets. This action primarily relates to Inference logging and production trace privacy: Inference logs and tracing permit diagnosis of real issues but must be sampled, retained and redacted safely. However, the described case — A medical expert flags unsafe triage advice, but engineering discards the feedback because an LLM judge rates it highly. — is testing Human SME feedback rubric and reviewer calibration. It does not directly establish the 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. Revisit the choice as workload and evaluation data change instead of permanently trusting benchmark ranking. This action primarily relates to Model selection from quantitative task metrics: Select candidate LLMs by measured task success, latency, safety and token cost, not parameter count or leaderboard rank. However, the described case — A medical expert flags unsafe triage advice, but engineering discards the feedback because an LLM judge rates it highly. — is testing Human SME feedback rubric and reviewer calibration. It does not directly establish the 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 medical expert flags unsafe triage advice, but engineering discards the feedback because an LLM judge rates it highly. — is testing Human SME feedback rubric and reviewer calibration. It does not directly establish the 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 vector count, dimension, encoder throughput, per-query latency and measured quality curves. 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 legal contract review agent needs nuanced long-context reasoning but can tolerate higher response time. — is testing Model selection by quality latency and budget. 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 training/licensing terms, model-card task benchmarks, input limits and restrictions. 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 legal contract review agent needs nuanced long-context reasoning but can tolerate higher response time. — is testing Model selection by quality latency and budget. 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 evaluation data composition, judge criteria, run configuration and sampled failures. This action primarily relates to Model evaluation with paired benchmarks: Accuracy, faithfulness, relevance and refusal behavior require task-specific scoring, and a model switch needs common test conditions. However, the described case — A legal contract review agent needs nuanced long-context reasoning but can tolerate higher response time. — is testing Model selection by quality latency and budget. 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. Split by task-relevant sections and filter top passages before prompt assembly. 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 team adds 'be helpful' to a system prompt, and responses become longer but less grounded. — is testing Prompt changes evaluated against baseline. 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 adds 'be helpful' to a system prompt, and responses become longer but less grounded. — is testing Prompt changes evaluated against baseline. 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 which fields are necessary, masking false positives and any leaked sensitive fields. 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 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 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 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 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 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 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 team uses a text-generation endpoint to return a fixed-size vector for semantic similarity search. — is testing Specialized model versus general LLM. 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 team uses a text-generation endpoint to return a fixed-size vector for semantic similarity search. — is testing Specialized model versus general LLM. 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 vector count, dimension, encoder throughput, per-query latency and measured quality curves. 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 team uses a text-generation endpoint to return a fixed-size vector for semantic similarity search. — is testing Specialized model versus general LLM. 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.