Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest verify choice for this specific question. Load-test representative search traffic and benchmark index freshness versus storage/serving 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 legacy SQL Classic warehouse cannot run a new `ai_query()` workload and engineers assume bad model credentials. — is testing SQL ai_query for governed batch inference. 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. Exercise failed tests and confirm release is blocked, then deploy and verify a passing version. This action primarily relates to CI/CD pipelines for retrieval and agent components: Production promotions should test source index, prompt, model packaging and tool behavior independently before release. However, the described case — A legacy SQL Classic warehouse cannot run a new `ai_query()` workload and engineers assume bad model credentials. — is testing SQL ai_query for governed batch inference. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Load the logged pyfunc model in an isolated environment and test the declared signature on sample requests. 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 legacy SQL Classic warehouse cannot run a new `ai_query()` workload and engineers assume bad model credentials. — is testing SQL ai_query for governed batch inference. 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. Compare both models on the same held-out support questions, citations, cost and safety cases. 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 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 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. Select a suitable embedding model rather than treating generated prose as a numeric embedding. 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 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 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. Select a candidate with measured language coverage and document residual risk on target-language samples. 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 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 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. 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 agent endpoint gets accuracy complaints but serving logs capture only HTTP status, hiding response content and retrieval IDs. — is testing Inference logging and production trace privacy. 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 equate an LLM judge score with unquestionable ground truth; calibrate against reviewed labels. This action primarily relates to MLflow GenAI tracing, built-in and custom scorers: MLflow GenAI traces capture components, and scorers/judges can evaluate a full answer or individual retrieval and tool spans. However, the described case — An agent endpoint gets accuracy complaints but serving logs capture only HTTP status, hiding response content and retrieval IDs. — is testing Inference logging and production trace privacy. 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 verify choice for this specific question. Document legal clearance and confirm the deployed artifact matches the approved license/version. This action primarily relates to Open model license versus managed endpoint obligations: Model availability on a hub does not itself confer commercial training, redistribution or hosting rights. However, the described case — A 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 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 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 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. Embed test chunks with relevant facts at the end and confirm they remain retrievable. 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 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. 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 corporate help desk must answer policy questions from a vetted HR handbook and cite the passage used. — is testing Agent Bricks Knowledge Assistant suitability. 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. Assemble query-to-retriever-to-context-grounded-prompt-to-LLM stages and attach citations to retrieved passages. 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 corporate help desk must answer policy questions from a vetted HR handbook and cite the passage used. — is testing Agent Bricks Knowledge Assistant suitability. 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 corporate help desk must answer policy questions from a vetted HR handbook and cite the passage used. — is testing Agent Bricks Knowledge Assistant suitability. 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. Split the section at legal boundaries and preserve exceptions rather than allowing implicit truncation. 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 maintenance chatbot fabricates a firmware version not found in its manual index. — is testing Hallucinated facts and unsupported citations. 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. Treat the page as untrusted evidence and enforce tool authorization and destination allowlists on the server. This action primarily relates to Prompt-injection defenses for retrieved context: Retrieved content is lower-trust data; embedded instructions must not trigger privileged tool calls or override assistant rules. However, the described case — A maintenance chatbot fabricates a firmware version not found in its manual index. — is testing Hallucinated facts and unsupported citations. 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 maintenance chatbot fabricates a firmware version not found in its manual index. — is testing Hallucinated facts and unsupported citations. 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. Run a fixed request through each stage and assert the final API schema and reference grounding. 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 customer helpdesk agent loses the selected ticket ID whenever a user starts a new session, despite needing session continuity. — is testing Persistent conversation memory with authorized datastore. 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 allowed and denied principals against both endpoint invocation and protected retrieval data. 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 customer helpdesk agent loses the selected ticket ID whenever a user starts a new session, despite needing session continuity. — is testing Persistent conversation memory with authorized datastore. 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. Switch alias to a tested version and verify the active agent follows it and can roll back. This action primarily relates to MLflow Prompt Registry version aliases and promotion: Prompt Registry tracks immutable prompt versions with mutable aliases for staging and production, enabling change control and rollback. However, the described case — A customer helpdesk agent loses the selected ticket ID whenever a user starts a new session, despite needing session continuity. — is testing Persistent conversation memory with authorized datastore. 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. 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 live call-center assistant must respond under three seconds and keep per-call model cost bounded. — is testing Latency, cost and retrieval targets as design requirements. 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 select a generative model solely for fluency when the business requires reproducible classification rules. 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 — A live call-center assistant must respond under three seconds and keep per-call model cost bounded. — is testing Latency, cost and retrieval targets as design requirements. 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 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 vendor proposes to copy managed model weights into an on-prem product contrary to provider terms. — is testing Open model license versus managed endpoint obligations. 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 — A vendor proposes to copy managed model weights into an on-prem product contrary to provider terms. — is testing Open model license versus managed endpoint obligations. 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 vendor proposes to copy managed model weights into an on-prem product contrary to provider terms. — is testing Open model license versus managed endpoint obligations. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Do not cherry-pick average metrics that hide severe high-impact task 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 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 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. Revalidate model choice after volume or source-document shape changes materially. This action primarily relates to Model selection by quality latency and budget: Select the smallest suitable model that meets a task's accuracy and latency constraints under realistic workload, not marketing rank. However, the described case — A 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 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 tune chunk length on one successful demo; measure evidence recall and grounded answer performance. 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 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 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 — 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.