Databricks Certified Generative AI Engineer Associate Bundle

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.

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 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 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. Build a compatible new index and re-embed the corpus, then test cutover against representative queries. This action primarily relates to Embedding model swap and reindex compatibility: Changed embedding dimensions or model semantics typically require re-embedding and index consistency before comparing search quality. However, the described case — A 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 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. Extract model/country fields and apply them as verified metadata filters to approved retrieval. 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 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 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 content provenance, licensing terms, rights reservations and intended distribution. This action primarily relates to Training and retrieval corpus license rights: Public accessibility does not automatically authorize copying, embedding or using content in commercial RAG services. However, the described case — A public review feed contains slurs and adversarial instructions that surface in a brand-support assistant. — is testing Toxic, inaccurate and adversarial corpus cleaning. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect source origin, prompt hierarchy, tool permissions and trace evidence of instruction-following attempts. This action primarily relates to Input guardrails against prompt-injected source documents: A document that says 'ignore your rules' is untrusted data; a robust agent must enforce instruction and tool boundaries independently. However, the described case — A public review feed contains slurs and adversarial instructions that surface in a brand-support assistant. — is testing Toxic, inaccurate and adversarial corpus cleaning. 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 filter decisions, action permissions, identity propagation and resulting audit events. This action primarily relates to Prompt safety filtering and tool allowlists: Content filters and action allowlists are complementary; a moderation score is not a substitute for authorization of external effects. However, the described case — A public review feed contains slurs and adversarial instructions that surface in a brand-support assistant. — is testing Toxic, inaccurate and adversarial corpus cleaning. 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. 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 team persists all raw conversations in an unprotected shared cache to preserve agent memory. — 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. 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 team persists all raw conversations in an unprotected shared cache to preserve agent memory. — 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. 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 team persists all raw conversations in an unprotected shared cache to preserve agent memory. — 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 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 — An internal receipt classifier must process 200 requests per second under tight GPU cost targets. — is testing Model selection by quality latency and budget. 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. Review model license and select an authorized commercial alternative before deployment. 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 — An internal receipt classifier must process 200 requests per second under tight GPU cost targets. — is testing Model selection by quality latency and budget. 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. Enable supported MLflow GenAI tracing around each model, retriever and tool operation with secret redaction. 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 — An internal receipt classifier must process 200 requests per second under tight GPU cost targets. — is testing Model selection by quality latency and budget. 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. Use a frozen relevance dataset to prevent tuning to a single cherry-picked query. 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 — PDF extraction repeats a footer classification notice inside every employee policy chunk. — is testing Boilerplate and navigation filtering in source corpora. 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 attribute an absent document to reranking failure if the first-stage search never returned it. This action primarily relates to Cross-encoder reranking after candidate retrieval: A reranker scores query-document relevance over a candidate set; it improves ordering but does not add missing documents. However, the described case — PDF extraction repeats a footer classification notice inside every employee policy chunk. — is testing Boilerplate and navigation filtering in source corpora. 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 — PDF extraction repeats a footer classification notice inside every employee policy chunk. — is testing Boilerplate and navigation filtering in source corpora. 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. Run an incremental update and verify new, changed and deleted source chunks are reflected exactly once. This action primarily relates to Delta and Unity Catalog pipeline for chunk tables: A governed retrieval corpus stores chunk text, IDs, source lineage and metadata in managed Delta/Unity Catalog tables before indexing. However, the described case — A manuals corpus produces 2.5 million vectors and exceeds the planned index capacity after 120-token chunks. — is testing Chunk size and overlap tradeoffs. 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 that target retrieval returns complete condition-and-exception evidence for representative questions. This action primarily relates to Semantic boundaries versus fixed-window chunks: Headings, paragraphs and tables can require structure-aware splitting rather than arbitrary token windows. However, the described case — A manuals corpus produces 2.5 million vectors and exceeds the planned index capacity after 120-token chunks. — is testing Chunk size and overlap tradeoffs. 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 manuals corpus produces 2.5 million vectors and exceeds the planned index capacity after 120-token chunks. — is testing Chunk size and overlap tradeoffs. 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. Pin the retrieval index version and trace reference set in experiments before comparing runs. 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 multi-step customer agent calls Genie and Vector Search but no span shows which returned an incorrect fact. — is testing MLflow tracing in an Agent Framework workflow. 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 unauthorized tool requests through server-side permissions even if the model produces a valid tool call. 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 — A multi-step customer agent calls Genie and Vector Search but no span shows which returned an incorrect fact. — is testing MLflow tracing in an Agent Framework workflow. 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. Isolate instructions from source text and reject cross-trust-boundary requests through policy/tool checks. 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 multi-step customer agent calls Genie and Vector Search but no span shows which returned an incorrect fact. — is testing MLflow tracing in an Agent Framework workflow. 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 proof-of-concept team wants a supported hosted LLM without managing GPU serving or packaging custom weights. — is testing Foundation Model API versus custom serving choices. 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 proof-of-concept team wants a supported hosted LLM without managing GPU serving or packaging custom weights. — is testing Foundation Model API versus custom serving choices. 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 proof-of-concept team wants a supported hosted LLM without managing GPU serving or packaging custom weights. — is testing Foundation Model API versus custom serving choices. 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. Apply appropriate output moderation and escalation for unsafe responses while retaining audit evidence. This action primarily relates to PII masking and output moderation as complementary guardrails: Input redaction and output checks serve distinct purposes; retain only necessary identifiers and validate actions separately. 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 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 conversational answer generation separated from governed computation and source-of-truth queries. This action primarily relates to Multi-agent Genie Space tool routing and governed answers: Genie Spaces can provide governed natural-language access to structured business metrics; an agent should choose authorized Genie tools over guessing SQL 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 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 whether the task is grounded document Q&A, extraction, tool coordination or cross-agent orchestration. 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 — An extraction model treats a quoted customer complaint as a command to ignore the required response shape. — is testing Instruction hierarchy and bounded prompt examples. 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 — An extraction model treats a quoted customer complaint as a command to ignore the required response shape. — is testing Instruction hierarchy and bounded prompt examples. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect request volume, concurrency, response deadline, token budget and evaluation quality targets. This action primarily relates to Latency, cost and retrieval targets as design requirements: A valid pipeline design has measurable quality, latency, token and throughput constraints before model selection. However, the described case — An extraction model treats a quoted customer complaint as a command to ignore the required response shape. — is testing Instruction hierarchy and bounded prompt examples. 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.