Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest verify choice for this specific question. Check answer fidelity, citation paths and forbidden document access across test identities. This action primarily relates to Agent Bricks Knowledge Assistant suitability: A governed knowledge assistant grounds conversational responses in curated documents and access-controlled retrieval. However, the described case — A CRM agent repeats a create-ticket tool call after a timeout, producing duplicate complaints. — is testing Agent tool schemas, least privilege and retries. 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 cases with complete and missing required input fields and verify schema, access scope and usefulness. 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 CRM agent repeats a create-ticket tool call after a timeout, producing duplicate complaints. — is testing Agent tool schemas, least privilege and retries. 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 malformed inputs and inspect whether every response satisfies the parser and required field contract. 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 CRM agent repeats a create-ticket tool call after a timeout, producing duplicate complaints. — is testing Agent tool schemas, least privilege and retries. 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. Deploy an authenticated Databricks App backend that invokes the agent and enforces user-specific data permissions. This action primarily relates to Databricks Apps user-facing agent interface and OAuth identities: Databricks Apps supports authenticated interactive frontends; app credentials and user credentials have different scopes. However, the described case — A 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 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 place MCP API keys in prompts or browser code, and review third-party tool trust boundaries. 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 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 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 query embedding provenance, index schema, similarity results and selected context window. This action primarily relates to Vector Search retrieval workflow and query integration: Semantic retrieval uses an embedding model to query a compatible index, returns ranked passages and metadata for grounded generation. 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 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 table, index type, embedding model, index status and last successful sync. This action primarily relates to Databricks Vector Search index from governed Delta data: A vector index serves embeddings of chunked records maintained in a Unity Catalog governed Delta source table. 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 diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect runtime invocation order, prompt input names, stage outputs and errors. This action primarily relates to Simple prompt-retrieval-generation chain assembly: A minimal chain composes a retriever, prompt, LLM and output parser, preserving required variables and failure states. However, the described case — 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 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 repeatable attack cases and verify restricted content and destructive operations remain inaccessible. This action primarily relates to Unsafe model output and jailbreak response diagnosis: User-provided instructions may attempt to bypass agent policies or cause data leakage; classification and tool boundaries need separate tests. 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 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 — 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 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. Inject adversarial retrieved passages and verify they cannot cause unauthorized actions or data disclosure. 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 — 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 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 an explicitly registered version and confirm its dependencies and outputs match the approved evaluation run. This action primarily relates to Unity Catalog registered model version and privileges: MLflow-logged models can be registered in Unity Catalog, with governed names, permissions and traceable version lineage. However, the described case — A team has a clean chunk table but no searchable index for semantic passage retrieval. — is testing Databricks Vector Search index from governed Delta data. 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 team has a clean chunk table but no searchable index for semantic passage retrieval. — is testing Databricks Vector Search index from governed Delta data. 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 — A team has a clean chunk table but no searchable index for semantic passage retrieval. — is testing Databricks Vector Search index from governed Delta data. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Determine whether output is fixed fields, document answers or orchestration of multiple tasks with tool calls. This action primarily relates to Agent Bricks Information Extraction versus Multiagent Supervisor: Information Extraction maps source documents to structured fields; Multiagent Supervisor coordinates specialized capabilities for compound workflows. However, the described case — A travel agent books a flight before checking ticket rules and traveler approval. — is testing Tool ordering and error isolation in multi-stage reasoning. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect the prompt hierarchy, few-shot coverage, untrusted-data delimiters and observed format deviations. This action primarily relates to Instruction hierarchy and bounded prompt examples: Few-shot examples and explicit boundaries can clarify expected outputs, but embedded source documents should not become new system instructions. However, the described case — A travel agent books a flight before checking ticket rules and traveler approval. — is testing Tool ordering and error isolation in multi-stage reasoning. 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. Identify whether the output is a category, extractive field, free-form summary or grounded answer. 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 travel agent books a flight before checking ticket rules and traveler approval. — is testing Tool ordering and error isolation in multi-stage reasoning. 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. 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 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 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. Deploy synchronized index definitions and validate source freshness during production cutover. 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 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 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. 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 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 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. 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 — An Agent Framework service reports only end-to-end duration, hiding which tool call causes a 12-second delay. — is testing MLflow tracing in an Agent Framework workflow. 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. Inject adversarial retrieved passages and verify they cannot cause unauthorized actions or data disclosure. 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 — An Agent Framework service reports only end-to-end duration, hiding which tool call causes a 12-second delay. — is testing MLflow tracing in an Agent Framework workflow. 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 representative task evaluation in the intended language and document limitations. 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 Agent Framework service reports only end-to-end duration, hiding which tool call causes a 12-second delay. — is testing MLflow tracing in an Agent Framework workflow. 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. 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 wants to reuse the same retrieval stage with two different LLMs while benchmarking quality. — is testing LangChain runnable composition and invocation. 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. Benchmark candidates against accuracy, p95 latency and cost per classified receipt before selecting one. 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 team wants to reuse the same retrieval stage with two different LLMs while benchmarking quality. — is testing LangChain runnable composition and invocation. 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. Validate account and order IDs, enforce identity scope, and retrieve the matching order status before generation. 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 wants to reuse the same retrieval stage with two different LLMs while benchmarking quality. — is testing LangChain runnable composition and invocation. 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 warehouse type, runtime compatibility, endpoint status, SQL arguments and batch size. This action primarily relates to SQL ai_query for governed batch inference: `ai_query()` invokes an available serving endpoint from SQL; suitability depends on supported runtimes, endpoint and workload. However, the described case — A 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 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 package lockfile, model signature, serving logs and API contract differences. This action primarily relates to Deployed model dependency drift and environment compatibility: Models logged in experiments can fail in serving if Python dependencies or inference signatures differ between build and target. 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 diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect auth model, frontend token handling, backend endpoint calls and user-level data controls. This action primarily relates to Databricks Apps user-facing agent interface and OAuth identities: Databricks Apps supports authenticated interactive frontends; app credentials and user credentials have different scopes. However, the described case — A 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 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. Select chunk granularity by measured retrieval results, not solely by minimizing index records. 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 legal RAG service finds semantically similar contracts from the wrong customer workspace. — is testing Hybrid sparse and dense retrieval with 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. Separate missing knowledge from bad generation during incident triage and refresh upstream data responsibly. This action primarily relates to Authoritative source coverage for factual answers: A RAG model cannot answer accurately if the required authoritative record is missing or stale in its index. However, the described case — A legal RAG service finds semantically similar contracts from the wrong customer workspace. — is testing Hybrid sparse and dense retrieval with 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. Route documents by actual format and flag low-confidence extraction rather than silently indexing blank text. This action primarily relates to Format-specific document extraction and OCR needs: Extract text with a parser suited to source format; image-only scans require OCR rather than HTML or plain-text parsing. However, the described case — A legal RAG service finds semantically similar contracts from the wrong customer workspace. — is testing Hybrid sparse and dense retrieval with 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.