Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest diagnose choice for this specific question. Inspect logged model artifacts, environment requirements, signature and source index identifiers. 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 deploy pipeline overwrites the production prompt text each release and cannot restore yesterday's known-good response. — is testing MLflow Prompt Registry version aliases and promotion. 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 — A deploy pipeline overwrites the production prompt text each release and cannot restore yesterday's known-good response. — is testing MLflow Prompt Registry version aliases and promotion. 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 deploy pipeline overwrites the production prompt text each release and cannot restore yesterday's known-good response. — is testing MLflow Prompt Registry version aliases and promotion. 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. Redact or pseudonymize identity fields before vector indexing and enforce source access rules. This action primarily relates to Sensitive-field masking before embedding: Masking or tokenization can remove unnecessary PII from chunks before embedding and external model calls while retaining useful meaning. However, the described case — A chatbot accepts a malicious request to publish harassing content to a company social feed. — is testing Prompt safety filtering and tool allowlists. 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. Ignore the document's imperative content as instructions and block secret retrieval in the serving layer. 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 chatbot accepts a malicious request to publish harassing content to a company social feed. — is testing Prompt safety filtering and tool allowlists. 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. Mask account identifiers selectively while retaining required monetary values and verifying extraction accuracy. This action primarily relates to Contextual masking versus destructive data removal: Masking must preserve information needed for the task, such as non-sensitive dates or amounts, and cannot replace access control. However, the described case — A chatbot accepts a malicious request to publish harassing content to a company social feed. — is testing Prompt safety filtering and tool allowlists. 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. 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 support bot includes retrieved pages in responses but drops the original user's question before generation. — is testing Retriever-generator chain component boundaries. It does not directly establish the 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. Revisit cost/latency budgets whenever context window or retrieval size changes significantly. This action primarily relates to Latency, cost and retrieval targets as design requirements: A valid pipeline design has measurable quality, latency, token and throughput constraints before model selection. However, the described case — A support bot includes retrieved pages in responses but drops the original user's question before generation. — is testing Retriever-generator chain component boundaries. It does not directly establish the 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 support bot includes retrieved pages in responses but drops the original user's question before generation. — is testing Retriever-generator chain component boundaries. It does not directly establish the 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 adversarial quoted-text tests and compare output structure on representative and edge inputs. 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 support bot includes retrieved pages in responses but drops the original user's question before generation. — is testing Retriever-generator chain component boundaries. It does not directly establish the 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. Simulate a failed eligibility lookup and verify no payment or booking action occurs. This action primarily relates to Tool ordering and error isolation in multi-stage reasoning: An agent should retrieve authoritative context before taking consequential actions and validate tool outcomes at each stage. However, the described case — A support bot includes retrieved pages in responses but drops the original user's question before generation. — is testing Retriever-generator chain component boundaries. It does not directly establish the 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 support bot includes retrieved pages in responses but drops the original user's question before generation. — is testing Retriever-generator chain component boundaries. It does not directly establish the 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. Inspect table extraction, repeated column headings, units, row identity and exact filter fields. This action primarily relates to Table-aware chunking and metadata-rich retrieval: Tabular rows need headers, units and column semantics preserved when transformed into retrieval documents. However, the described case — A research bot reports outdated product prices because the indexed catalog is a quarterly snapshot. — is testing Authoritative source coverage for factual answers. 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 distribution, overlap proportion, expected retrieval granularity and vector count. 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 research bot reports outdated product prices because the indexed catalog is a quarterly snapshot. — is testing Authoritative source coverage for factual answers. 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 MIME types, text-layer availability, encoding and parsing failures per source. 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 research bot reports outdated product prices because the indexed catalog is a quarterly snapshot. — is testing Authoritative source coverage for factual answers. 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. 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 troubleshooting assistant retrieves a part number but omits the note that the part is discontinued. — is testing Chunk quality evaluation and boundary splitting. 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 — A troubleshooting assistant retrieves a part number but omits the note that the part is discontinued. — is testing Chunk quality evaluation and boundary splitting. 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 — A helpdesk bot sends full payment card numbers to an external model for a simple FAQ answer. — is testing PII masking and output moderation as complementary guardrails. 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. Pin dependency and prompt schemas across releases so library updates do not silently break chain invocation. 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 helpdesk bot sends full payment card numbers to an external model for a simple FAQ answer. — is testing PII masking and output moderation as complementary guardrails. 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 — A helpdesk bot sends full payment card numbers to an external model for a simple FAQ answer. — is testing PII masking and output moderation as complementary guardrails. 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. 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 — A website crawler indexes the same cookie banner thousands of times and retrieval returns banners above actual policy. — 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. Never equate a successful embedding API call with a governed and reproducible source-data pipeline. 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 website crawler indexes the same cookie banner thousands of times and retrieval returns banners above actual policy. — 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 — A website crawler indexes the same cookie banner thousands of times and retrieval returns banners above actual policy. — 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. 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 — Document chunks average 700 tokens but the selected embedding model only accepts 512 tokens. — is testing Embedding context window and chunk token distribution. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Use the same quality rubrics for pre-release gates and production monitoring with separate datasets. This action primarily relates to Offline evaluation versus ongoing production monitoring: Offline test datasets catch regressions pre-release; production monitoring detects drift, real-user failures and evolving prompts. However, the described case — Document chunks average 700 tokens but the selected embedding model only accepts 512 tokens. — is testing Embedding context window and chunk token distribution. It does not directly establish the 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 data questions for correct Genie routing, SQL-backed values and denial of unauthorized tables. 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 — Document chunks average 700 tokens but the selected embedding model only accepts 512 tokens. — is testing Embedding context window and chunk token distribution. It does not directly establish the 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. Use an available Foundation Model API endpoint with compatible authentication, task API and quotas. This action primarily relates to Foundation Model API versus custom serving choices: Databricks Foundation Model APIs offer managed access to supported models; custom serving is suitable for specialized models or control needs. However, the described case — A claims RAG prototype uses notebook variables and cannot run when served outside the developer session. — is testing MLflow pyfunc packaging for pre- and post-processing. 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 registering a model with approving its business safety or access to all governed tables. 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 claims RAG prototype uses notebook variables and cannot run when served outside the developer session. — is testing MLflow pyfunc packaging for pre- and post-processing. 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 low-cost support search uses short chunks but the proposed model multiplies embedding dimensions by eight. — is testing Embedding dimensions latency and index storage. It does not directly establish the 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 component roles explicit so updates to a generation model do not silently alter retrieval vectors. 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 low-cost support search uses short chunks but the proposed model multiplies embedding dimensions by eight. — is testing Embedding dimensions latency and index storage. It does not directly establish the 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. Version embeddings with source and model identifiers to prevent silently mixing incompatible representations. 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 low-cost support search uses short chunks but the proposed model multiplies embedding dimensions by eight. — is testing Embedding dimensions latency and index storage. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.