Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest diagnose choice for this specific question. Inspect p95 latency, queue depth, rate limits, cost and per-version error traces. This action primarily relates to Endpoint scale concurrency and operational rollout: Serving latency and reliability depend on provisioned capacity, request concurrency, quotas and controlled rollout. However, the described case — A team promotes a new prompt without rerunning citation accuracy or tool-permission regression cases. — is testing CI/CD pipelines for retrieval and agent components. 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 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 team promotes a new prompt without rerunning citation accuracy or tool-permission regression cases. — is testing CI/CD pipelines for retrieval and agent components. 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 team promotes a new prompt without rerunning citation accuracy or tool-permission regression cases. — is testing CI/CD pipelines for retrieval and agent components. 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. Test sensitive-data leakage and harmful-output cases in both input and output stages. 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 product assistant must answer only for the model and country selected in the user form. — 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. 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 — A product assistant must answer only for the model and country selected in the user form. — 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. 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 product assistant must answer only for the model and country selected in the user form. — 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 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 developer's support chain omits the retrieved context and the LLM hallucinates policy clauses. — is testing Simple prompt-retrieval-generation chain assembly. 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 developer's support chain omits the retrieved context and the LLM hallucinates policy clauses. — is testing Simple prompt-retrieval-generation chain assembly. 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 developer's support chain omits the retrieved context and the LLM hallucinates policy clauses. — is testing Simple prompt-retrieval-generation chain assembly. 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. 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 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 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 human review for borderline filtering decisions so source cleaning does not silently erase important warnings. This action primarily relates to Toxic, inaccurate and adversarial corpus cleaning: Unreliable source text can teach unsafe behavior through retrieval; quarantine and source review matter before embeddings. 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 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. Maintain an auditable source-rights register and recheck rights when a corpus is refreshed. 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 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 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. Split by clause and heading boundaries with a token-aware fallback to preserve the rule and exception together. 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 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 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. Connect the authorized live shipment-tracking record keyed by order ID rather than guessing arrival from policy. 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 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. Score retrieved documents separately from generation using graded relevance and ranked-hit metrics. 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 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. Preserve hierarchical section IDs and supply the parent definition only when relevant. 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 — An energy tariff PDF is chunked by arbitrary text lines and rate values lose the currency and zone column. — is testing Table-aware chunking and metadata-rich retrieval. 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. Use document-aware sections plus parent-child metadata to connect symptom to resolution. 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 — An energy tariff PDF is chunked by arbitrary text lines and rate values lose the currency and zone column. — is testing Table-aware chunking and metadata-rich retrieval. 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. Parse and chunk documents, write keyed chunk rows with provenance to a governed Delta table, then index them. 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 — An energy tariff PDF is chunked by arbitrary text lines and rate values lose the currency and zone column. — is testing Table-aware chunking and metadata-rich retrieval. 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 prompt versions and rollback capability rather than overwriting the only known-good template. 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 ledger explanation app needs repeatable short outputs, but developers increase temperature to make wording more creative. — is testing Temperature and deterministic format tradeoffs. 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 ledger explanation app needs repeatable short outputs, but developers increase temperature to make wording more creative. — is testing Temperature and deterministic format tradeoffs. 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 ledger explanation app needs repeatable short outputs, but developers increase temperature to make wording more creative. — is testing Temperature and deterministic format tradeoffs. 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. Resolve the authorized production alias at runtime using a controlled refresh strategy. 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 LangChain pipeline returns an SDK message object while its API gateway expects a plain answer string. — is testing Simple prompt-retrieval-generation chain assembly. 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. Version the serving input schema or provide a tested compatibility adapter during migration. 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 LangChain pipeline returns an SDK message object while its API gateway expects a plain answer string. — is testing Simple prompt-retrieval-generation chain assembly. 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. 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 LangChain pipeline returns an SDK message object while its API gateway expects a plain answer string. — is testing Simple prompt-retrieval-generation chain assembly. 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 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 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 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 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 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 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 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 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. 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 brainstorming app wants creative draft ideas but is incorrectly evaluated on exact-string matching to one reference. — is testing Temperature and deterministic format tradeoffs. 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 trust an LLM-extracted customer identifier without server-side permission validation. 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 brainstorming app wants creative draft ideas but is incorrectly evaluated on exact-string matching to one reference. — is testing Temperature and deterministic format tradeoffs. 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. Expire or segregate conversation memory by identity and purpose, especially for financial and personal records. This action primarily relates to Conversation context and intent routing: Multi-turn assistants need explicit conversational state while routing each new request to the correct tool or topic. However, the described case — A brainstorming app wants creative draft ideas but is incorrectly evaluated on exact-string matching to one reference. — is testing Temperature and deterministic format tradeoffs. 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 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 — An imported policy library contains a deliberately altered obsolete security procedure mixed into current instructions. — 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 — An imported policy library contains a deliberately altered obsolete security procedure mixed into current instructions. — 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 extraction fields, masking policy, downstream embedded text and sensitive-data exposure paths. 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 — An imported policy library contains a deliberately altered obsolete security procedure mixed into current instructions. — 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.