Databricks Certified Generative AI Engineer Associate Bundle

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 — An order assistant answers shipping questions without using the provided account_id, mixing orders across customers. — is testing Query-field driven prompt and retrieval filters. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. 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 order assistant answers shipping questions without using the provided account_id, mixing orders across customers. — is testing Query-field driven prompt and retrieval filters. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Never compare metrics from non-equivalent data snapshots as if they were a paired model test. 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 — An order assistant answers shipping questions without using the provided account_id, mixing orders across customers. — is testing Query-field driven prompt and retrieval filters. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest 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 — 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 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 — 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 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 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 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 reproducible pairwise experiments with confidence and segment-level result analysis. 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 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 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. Use the same quality rubrics for pre-release gates and production monitoring with separate datasets. This action primarily relates to Offline evaluation versus ongoing production monitoring: Offline test datasets catch regressions pre-release; production monitoring detects drift, real-user failures and evolving prompts. 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 verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Reproduce a slow/error case and confirm each relevant stage is observable without sensitive tokens. This action primarily relates to MLflow tracing in an Agent Framework workflow: MLflow tracing records agent steps, tool calls and latency; integration must retain child spans and inputs without leaking secrets. However, the described case — A 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 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. Choose a rubric or pairwise assessment suitable for open answers rather than exact string equality. 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 operations assistant benchmark favors a huge model on fluency, but a smaller model has higher citation correctness at lower cost. — is testing Model selection from quantitative task metrics. 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. Monitor tail latency, timeout rate and affected user experience under representative load. 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 — An operations assistant benchmark favors a huge model on fluency, but a smaller model has higher citation correctness at lower cost. — is testing Model selection from quantitative task metrics. 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 approved inference tables and trace metadata to correlate outputs with deployed model/index versions. This action primarily relates to Inference tables and Agent Monitoring feedback loop: Inference tables and agent monitoring capture production request/response signals and traces for quality investigations. However, the described case — An operations assistant benchmark favors a huge model on fluency, but a smaller model has higher citation correctness at lower cost. — is testing Model selection from quantitative task metrics. 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 task difficulty, expected concurrency, context size, throughput and model benchmark evidence. 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 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 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 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 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 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. Pass both the user question and selected passages into the prompt template before invoking the model. 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 — 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 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 — 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 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 a evaluated classification model and return a bounded label with confidence/abstention handling. This action primarily relates to Task choice: classification versus generative summarization: Classification predicts a category whereas summarization compresses meaning; the desired output determines the appropriate task. 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 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 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 deployed chatbot silently uses a different embedding model from the retrieval index built in development. — is testing RAG production bundle metadata and dependencies. 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 — A deployed chatbot silently uses a different embedding model from the retrieval index built in development. — is testing RAG production bundle metadata and dependencies. 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 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 — A deployed chatbot silently uses a different embedding model from the retrieval index built in development. — is testing RAG production bundle metadata and dependencies. 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. Use layered permissions and field-level handling instead of broad redaction that destroys task utility. 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 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 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. Mask card numbers and nonessential identity fields before ingestion and keep approved case references separately. This action primarily relates to Sensitive-field masking before embedding: Masking or tokenization can remove unnecessary PII from chunks before embedding and external model calls while retaining useful meaning. However, the described case — A 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 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 license text, model provenance, intended distribution and operational hosting constraints. 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 — Document chunks average 700 tokens but the selected embedding model only accepts 512 tokens. — is testing Embedding context window and chunk token distribution. 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 cited spans, source freshness, answer claims and missing-reference patterns. 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 — Document chunks average 700 tokens but the selected embedding model only accepts 512 tokens. — is testing Embedding context window and chunk token distribution. 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 — Document chunks average 700 tokens but the selected embedding model only accepts 512 tokens. — is testing Embedding context window and chunk token distribution. 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 proposed tool call sequence, preconditions, approval gates and partial failures. 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 support bot includes retrieved pages in responses but drops the original user's question before generation. — is testing Retriever-generator chain component boundaries. 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 tool parameter contracts, identity scopes, retry semantics and side-effect logs. 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 support bot includes retrieved pages in responses but drops the original user's question before generation. — is testing Retriever-generator chain component boundaries. 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 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 — A support bot includes retrieved pages in responses but drops the original user's question before generation. — is testing Retriever-generator chain component boundaries. 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. Rerun a controlled experiment and confirm metrics match within expected stochastic tolerance. 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 compliance summary app adds examples but stops honoring the one-line required answer format. — is testing Prompt changes evaluated against baseline. 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. Use the same quality rubrics for pre-release gates and production monitoring with separate datasets. This action primarily relates to Offline evaluation versus ongoing production monitoring: Offline test datasets catch regressions pre-release; production monitoring detects drift, real-user failures and evolving prompts. However, the described case — A compliance summary app adds examples but stops honoring the one-line required answer format. — is testing Prompt changes evaluated against baseline. 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. Check embedding dimensions or extracted-field validation against task-specific acceptance tests. 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 compliance summary app adds examples but stops honoring the one-line required answer format. — is testing Prompt changes evaluated against baseline. 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.