Databricks Certified Generative AI Engineer Associate Bundle

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 uses a text-generation endpoint to return a fixed-size vector for semantic similarity search. — is testing Specialized model versus general LLM. 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 uses a text-generation endpoint to return a fixed-size vector for semantic similarity search. — is testing Specialized model versus general LLM. 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 vector count, dimension, encoder throughput, per-query latency and measured quality curves. This action primarily relates to Embedding dimensions latency and index storage: Embedding width affects index storage and computation, and larger dimensions do not automatically improve task relevance. However, the described case — A team uses a text-generation endpoint to return a fixed-size vector for semantic similarity search. — is testing Specialized model versus general LLM. 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 training/licensing terms, model-card task benchmarks, input limits and restrictions. 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 code assistant looks fast in demos but has low pass rate on the organization's test suite. — is testing Model evaluation with paired benchmarks. 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 which indicators are measured before deployment versus on live traffic and feedback. 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 — A code assistant looks fast in demos but has low pass rate on the organization's test suite. — is testing Model evaluation with paired benchmarks. 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 code assistant looks fast in demos but has low pass rate on the organization's test suite. — is testing Model evaluation with paired benchmarks. 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. Do not cherry-pick average metrics that hide severe high-impact task 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 — Repeated evaluation of one agent produces conflicting reports because source-document snapshots differ. — is testing Experiment tracking and version reproducibility. 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. Retain a sampling and redaction policy for traces rather than logging raw secrets in production. 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 — Repeated evaluation of one agent produces conflicting reports because source-document snapshots differ. — is testing Experiment tracking and version reproducibility. 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 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 — Repeated evaluation of one agent produces conflicting reports because source-document snapshots differ. — is testing Experiment tracking and version reproducibility. 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. Retrieve rare table values and confirm the matching row, units and header context are intact. 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 — An order-support assistant knows return policy but cannot answer delivery ETA because shipment status is absent. — is testing Authoritative source coverage for factual answers. 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 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 — An order-support assistant knows return policy but cannot answer delivery ETA because shipment status is absent. — is testing Authoritative source coverage for factual answers. 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. Sample pages/images against extracted text and check structured fields and layout fidelity. 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 — An order-support assistant knows return policy but cannot answer delivery ETA because shipment status is absent. — is testing Authoritative source coverage for factual answers. 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. Review license and reuse conditions and use authorized sources or link without copying protected text. 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 financial invoice extractor masks every number, including legitimate tax amounts and invoice totals. — is testing Contextual masking versus destructive data removal. 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. 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 financial invoice extractor masks every number, including legitimate tax amounts and invoice totals. — is testing Contextual masking versus destructive data removal. 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. Filter toxic or instruction-like content and use reviewed trusted source subsets for customer-facing retrieval. 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 financial invoice extractor masks every number, including legitimate tax amounts and invoice totals. — is testing Contextual masking versus destructive data removal. 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. 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 300-page maintenance manual is cut into tiny fragments and the retrieved snippet omits the cause-and-remedy pair. — is testing Chunk size and overlap 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. Limit parent expansion to an appropriate token budget to avoid irrelevant context dilution. 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 300-page maintenance manual is cut into tiny fragments and the retrieved snippet omits the cause-and-remedy pair. — is testing Chunk size and overlap 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 assume embedding similarity alone is a security boundary or reliable exact identifier lookup. This action primarily relates to Hybrid sparse and dense retrieval with filters: Hybrid search combines lexical exact-match and semantic similarity; metadata filtering narrows authorized relevant content. However, the described case — A 300-page maintenance manual is cut into tiny fragments and the retrieved snippet omits the cause-and-remedy pair. — is testing Chunk size and overlap 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 storage key design, user isolation, TTL/retention and retrieval authorization. This action primarily relates to Persistent conversation memory with authorized datastore: Transient prompt context differs from persistent user state; durable memory needs explicit storage, identity scope and retention. However, the described case — A chat frontend embeds a service-principal secret directly into JavaScript to call the agent endpoint. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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 required model type, deployment control, supported region, endpoint quotas and operational burden. 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 chat frontend embeds a service-principal secret directly into JavaScript to call the agent endpoint. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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 — A chat frontend embeds a service-principal secret directly into JavaScript to call the agent endpoint. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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. 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 prototype RAG agent works on one notebook cluster but fails because its deployment package omits the vector search client dependency. — is testing RAG production bundle metadata and dependencies. 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 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 prototype RAG agent works on one notebook cluster but fails because its deployment package omits the vector search client dependency. — is testing RAG production bundle metadata and dependencies. 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. 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 prototype RAG agent works on one notebook cluster but fails because its deployment package omits the vector search client dependency. — is testing RAG production bundle metadata and dependencies. 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 candidate-set recall, relevance scores, top-k cutoffs and added ranking latency. 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 — A team embeds PDFs directly into an unmanaged in-memory list, losing source versions and permissions. — is testing Delta and Unity Catalog pipeline for chunk tables. 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 section relationships, chunk hierarchy and whether cross-references survive extraction. 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 team embeds PDFs directly into an unmanaged in-memory list, losing source versions and permissions. — is testing Delta and Unity Catalog pipeline for chunk tables. 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 team embeds PDFs directly into an unmanaged in-memory list, losing source versions and permissions. — is testing Delta and Unity Catalog pipeline for chunk tables. 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 server type, endpoint URL, supported auth, tool declarations and available scopes. This action primarily relates to Managed versus external versus custom MCP server integration: MCP standardizes tool discovery; managed servers reduce hosting, external services need credentials and custom servers wrap bespoke actions. However, the described case — A 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 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 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 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 warehouse type, runtime compatibility, endpoint status, SQL arguments and batch size. This action primarily relates to SQL ai_query for governed batch inference: `ai_query()` invokes an available serving endpoint from SQL; suitability depends on supported runtimes, endpoint and workload. However, the described case — A 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 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. Check answer fidelity, citation paths and forbidden document access across test identities. This action primarily relates to Agent Bricks Knowledge Assistant suitability: A governed knowledge assistant grounds conversational responses in curated documents and access-controlled retrieval. However, the described case — A CRM agent repeats a create-ticket tool call after a timeout, producing duplicate complaints. — is testing Agent tool schemas, least privilege and retries. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Run cases with complete and missing required input fields and verify schema, access scope and usefulness. This action primarily relates to Translate use-case requirements into pipeline inputs and outputs: Business acceptance criteria must map to concrete source inputs, generated fields, correctness measures and permission constraints. However, the described case — A CRM agent repeats a create-ticket tool call after a timeout, producing duplicate complaints. — is testing Agent tool schemas, least privilege and retries. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Test malformed inputs and inspect whether every response satisfies the parser and required field contract. This action primarily relates to Structured JSON schema prompt and format compliance: A model can produce plausible prose rather than machine-readable JSON unless the output contract and validation are explicit. However, the described case — A CRM agent repeats a create-ticket tool call after a timeout, producing duplicate complaints. — is testing Agent tool schemas, least privilege and retries. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.