Databricks Certified Generative AI Engineer Associate Bundle

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 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 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 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 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 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 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 runnable input/output schemas, prompt variables and invocation traces around the failing stage. 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 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 which indicators are measured before deployment versus on live traffic and feedback. 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 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 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 trace context passages, token distribution, coverage of necessary conditions and retrieval rank. 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 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 scorer rubric, available trace spans, model response and known evaluation references. 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 data extraction agent has identical field-F1 across two architectures but one exceeds the production latency budget. — is testing Model selection from quantitative task metrics. 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 — A data extraction agent has identical field-F1 across two architectures but one exceeds the production latency budget. — is testing Model selection from quantitative task metrics. 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 token volumes, QPS, endpoint pricing, cache hit rate and user/workload attribution. 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 data extraction agent has identical field-F1 across two architectures but one exceeds the production latency budget. — is testing Model selection from quantitative task metrics. 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. Use an appropriately licensed deployment path or provider endpoint that permits the intended usage. 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 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. Design a precise instruction on evidence and uncertainty, then compare against baseline using the same evaluation set. 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 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 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 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 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 — 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 verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Validate tool discovery and a permitted request for both services, including denied action testing. 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 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 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 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 registered bundle in a clean environment and validate retrieval-to-generation behavior end to end. 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 production team passes around unversioned notebook checkpoints and cannot reproduce the active agent package. — is testing Unity Catalog registered model version and privileges. 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 production team passes around unversioned notebook checkpoints and cannot reproduce the active agent package. — is testing Unity Catalog registered model version and privileges. 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 production team passes around unversioned notebook checkpoints and cannot reproduce the active agent package. — is testing Unity Catalog registered model version and privileges. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Do not assume an instruction to 'respond in JSON' replaces actual schema validation and error handling. This action primarily relates to Structured JSON schema prompt and format compliance: A model can produce plausible prose rather than machine-readable JSON unless the output contract and validation are explicit. However, the described case — A 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 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. Keep instructions and examples versioned and test new patterns without allowing retrieved data to override policy. 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 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 model fluency or demo satisfaction as a substitute for measurable business acceptance 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 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 safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Call a structured order-status tool for transaction fields and retrieve policy text before composing a grounded response. This action primarily relates to Parallel retrieval and deterministic chain postprocessing: Combining structured lookup and semantic retrieval requires explicit routing, result joining, and downstream schema checks. However, the described case — A 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 implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest implement choice for this specific question. Define the equipment identifiers, failure observations and inventory query as required inputs, with approved part IDs as outputs. This action primarily relates to Translate use-case requirements into pipeline inputs and outputs: Business acceptance criteria must map to concrete source inputs, generated fields, correctness measures and permission constraints. However, the described case — A 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 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 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 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. 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 — Repeated evaluation of one agent produces conflicting reports because source-document snapshots differ. — 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. 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 — Repeated evaluation of one agent produces conflicting reports because source-document snapshots differ. — 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. Verify matched query and document vectors use the approved version and retrieval improves on held-out examples. 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 — Repeated evaluation of one agent produces conflicting reports because source-document snapshots differ. — 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. 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 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 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 equivalent retrieval tests including storage and refresh cost for candidate encoders. 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 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 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 mismatched user and account values and confirm zero unauthorized retrieval and correct contextual answers. 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 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 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 that an exception and its definition are available to the generator after retrieval. This action primarily relates to Parent-child retrieval and hierarchical structure: Parent-child retrieval indexes targeted sections but expands to their broader parent context for generation. However, the described case — A scanned JPEG safety certificate yields no extractable text in the pipeline. — is testing Format-specific document extraction and OCR needs. 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 scanned JPEG safety certificate yields no extractable text in the pipeline. — is testing Format-specific document extraction and OCR needs. 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 hit recall and answer grounding for sample chunk sizes with a fixed query set. This action primarily relates to Chunk size and overlap tradeoffs: Chunk size determines the number of vectors and coherence; overlap reduces boundary loss but increases index size and cost. However, the described case — A scanned JPEG safety certificate yields no extractable text in the pipeline. — is testing Format-specific document extraction and OCR needs. 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.