Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest safeguard choice for this specific question. Retest adversarial sources after adding new file types and tool connectors. 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 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 layered permissions and field-level handling instead of broad redaction that destroys task utility. 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 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 masking rules under regression control and treat embeddings and logs as potentially sensitive too. 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 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. Use a fit-for-task model, batching and usage thresholds with per-request cost monitoring. 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 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. Trace retriever and generator spans, score passage relevance and answer faithfulness separately. 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 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 authorized usage/inference tracking and per-principal attribution with clear quota alerts. This action primarily relates to AI Gateway rate limits, usage tables and inference telemetry: AI Gateway offers controlled access, supported usage tracking and rate limiting to protect shared endpoints and measure consumption. 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 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 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 regulatory standard contains nested headings, and isolated subclauses lose defined terms from the section header. — is testing Parent-child retrieval and hierarchical structure. 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 labeled query/chunk relevance, false positive hits, top-k settings and evaluation coverage. 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 regulatory standard contains nested headings, and isolated subclauses lose defined terms from the section header. — is testing Parent-child retrieval and hierarchical structure. 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 heading structure, sentence breaks, table boundaries and parent document identifiers. 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 regulatory standard contains nested headings, and isolated subclauses lose defined terms from the section header. — is testing Parent-child retrieval and hierarchical structure. 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 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 — An agent produces raw document objects but the serving client expects a JSON list of cited answers. — is testing MLflow pyfunc packaging for pre- and post-processing. 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 UC model names, signatures, version metadata, lineage and relevant ACLs. 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 — An agent produces raw document objects but the serving client expects a JSON list of cited answers. — is testing MLflow pyfunc packaging for pre- and post-processing. 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 serving endpoint permissions, token path, user/app identity and downstream Unity Catalog access. 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 — An agent produces raw document objects but the serving client expects a JSON list of cited answers. — is testing MLflow pyfunc packaging for pre- and post-processing. 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 refund agent issues credits before verifying invoice status or refund eligibility. — 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. Trace which chain stage receives the question, retriever matches, prompt context and generated answer. This action primarily relates to Retriever-generator chain component boundaries: A basic RAG chain separates user input, query transformation, retrieval, prompt assembly, model generation and output validation. However, the described case — A refund agent issues credits before verifying invoice status or refund eligibility. — 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 each source connector's contract, join keys, runtime error handling and the final prompt inputs. 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 refund agent issues credits before verifying invoice status or refund eligibility. — 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 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 claims assistant answers in different tones because the prompt has no consistent example or response constraints. — 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. Trace which chain stage receives the question, retriever matches, prompt context and generated answer. This action primarily relates to Retriever-generator chain component boundaries: A basic RAG chain separates user input, query transformation, retrieval, prompt assembly, model generation and output validation. However, the described case — A claims assistant answers in different tones because the prompt has no consistent example or response constraints. — 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. Compare requested fields, response parsing errors, structured-output support and schema validation failures. 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 claims assistant answers in different tones because the prompt has no consistent example or response constraints. — 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 encoder token limits, chunk length percentiles, truncation counters and source suffix omissions. This action primarily relates to Embedding context window and chunk token distribution: The embedding encoder must accept the actual tokenized chunk length; silently truncating chunks can drop relevant suffix facts. However, the described case — A team picks a model marked research-only and plans to deploy it for a paid product. — is testing Open model license versus managed endpoint obligations. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect evaluation data composition, judge criteria, run configuration and sampled failures. This action primarily relates to Model evaluation with paired benchmarks: Accuracy, faithfulness, relevance and refusal behavior require task-specific scoring, and a model switch needs common test conditions. However, the described case — A team picks a model marked research-only and plans to deploy it for a paid product. — is testing Open model license versus managed endpoint obligations. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect model version, vector dimensions, index schema, pipeline lineage and freshness. 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 team picks a model marked research-only and plans to deploy it for a paid product. — is testing Open model license versus managed endpoint obligations. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect 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 LangChain workflow sends a dictionary of question and context to a prompt that expects only input, raising a key error. — is testing LangChain runnable composition and invocation. 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 parsed intent, extracted keys, authorization check and actual query filter predicates. 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 LangChain workflow sends a dictionary of question and context to a prompt that expects only input, raising a key error. — is testing LangChain runnable composition and invocation. 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 experiment runs, source versions, parameter drift and metric definitions. 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 LangChain workflow sends a dictionary of question and context to a prompt that expects only input, raising a key error. — is testing LangChain runnable composition and invocation. 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. Apply moderation, require human review and restrict public-post tools to approved operators. 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 customer-support RAG source includes cardholder names and full card numbers even though questions concern card dispute policy. — is testing Sensitive-field masking before embedding. 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 customer-support RAG source includes cardholder names and full card numbers even though questions concern card dispute policy. — is testing Sensitive-field masking before embedding. 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 source text in retrieval context and use backend authorization for ticket actions. 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 customer-support RAG source includes cardholder names and full card numbers even though questions concern card dispute policy. — is testing Sensitive-field masking before embedding. 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. 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 — 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 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. Log model/prompt/data identifiers and metrics to a run with reproducible evaluation artifacts. 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 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 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 prompt names, version history, aliases, tests and active referenced URI. 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 new model signature expects messages array but the existing app sends only a prompt string. — is testing Deployed model dependency drift and environment compatibility. 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 predict entrypoint, model artifacts, dependency environment, inputs and output serialization. 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 new model signature expects messages array but the existing app sends only a prompt string. — is testing Deployed model dependency drift and environment compatibility. 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 deployment manifests, tests, aliases, index versions and rollback dependency matrix. 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 new model signature expects messages array but the existing app sends only a prompt string. — is testing Deployed model dependency drift and environment compatibility. 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.