Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest diagnose choice for this specific question. Inspect data schema, primary identifiers, change detection, UC permissions and ingestion checkpoint behavior. 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 crawler fetches HTML product manuals but outputs menu text instead of article content. — is testing Format-specific document extraction and OCR needs. 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 crawler fetches HTML product manuals but outputs menu text instead of article content. — is testing Format-specific document extraction and OCR needs. 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 the most frequent n-grams, extracted layout artifacts and top retrieved false positives. This action primarily relates to Boilerplate and navigation filtering in source corpora: Duplicated headers, disclaimers and navigation menus contaminate embeddings and cause irrelevant hits. However, the described case — A crawler fetches HTML product manuals but outputs menu text instead of article content. — is testing Format-specific document extraction and OCR needs. 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. Use budget limits and retry semantics when applying per-row model calls to large tables. 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 team has a clean chunk table but no searchable index for semantic passage retrieval. — is testing Databricks Vector Search index from governed Delta data. 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. Rotate credentials and separately verify caller identity and underlying data permission scopes. 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 — A team has a clean chunk table but no searchable index for semantic passage retrieval. — is testing Databricks Vector Search index from governed Delta data. 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. Require approval/rollback for prompt and index changes that alter user-facing model behavior. This action primarily relates to CI/CD pipelines for retrieval and agent components: Production promotions should test source index, prompt, model packaging and tool behavior independently before release. However, the described case — A team has a clean chunk table but no searchable index for semantic passage retrieval. — is testing Databricks Vector Search index from governed Delta data. 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 agent routing to Genie, space permissions, metric definitions and tool-returned values. This action primarily relates to Multi-agent Genie Space tool routing and governed answers: Genie Spaces can provide governed natural-language access to structured business metrics; an agent should choose authorized Genie tools over guessing SQL facts. However, the described case — A maintenance chatbot fabricates a firmware version not found in its manual index. — is testing Hallucinated facts and unsupported citations. It does not directly establish the 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 maintenance chatbot fabricates a firmware version not found in its manual index. — is testing Hallucinated facts and unsupported citations. It does not directly establish the 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 maintenance chatbot fabricates a firmware version not found in its manual index. — is testing Hallucinated facts and unsupported citations. It does not directly establish the 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. Turn each relevant table row into a header-aware text/metadata record with original page citation. 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 — Hybrid search retrieves the right troubleshooting note at rank 18 yet generation uses only the first five hits. — is testing Cross-encoder reranking after candidate 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. 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 — Hybrid search retrieves the right troubleshooting note at rank 18 yet generation uses only the first five hits. — is testing Cross-encoder reranking after candidate 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. 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 — Hybrid search retrieves the right troubleshooting note at rank 18 yet generation uses only the first five hits. — is testing Cross-encoder reranking after candidate 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. Document supported decoding options per endpoint and do not assume temperature guarantees factual correctness. This action primarily relates to Temperature and deterministic format tradeoffs: Decoding settings can affect variability and cost but cannot replace validation, grounding or application logic. However, the described case — A public application generates harmful abusive content after an unusual user prompt despite sanitized inputs. — 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. 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 — A public application generates harmful abusive content after an unusual user prompt despite sanitized inputs. — 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. 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 public application generates harmful abusive content after an unusual user prompt despite sanitized inputs. — 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 verify choice for this specific question. Simulate a traffic burst and confirm rate limiting protects other clients while usage reporting remains accurate. 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 — An agent endpoint gets accuracy complaints but serving logs capture only HTTP status, hiding response content and retrieval IDs. — is testing Inference logging and production trace privacy. 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 quality and latency threshold breaches and confirm responsible owners receive alerts. This action primarily relates to Production performance KPIs and incident thresholds: Monitoring should include answer correctness, retrieval coverage, safety, latency, drift and per-user harm indicators, not just availability. However, the described case — An agent endpoint gets accuracy complaints but serving logs capture only HTTP status, hiding response content and retrieval IDs. — is testing Inference logging and production trace privacy. 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 paired experiments with consistent evaluation data and evaluate cost-quality Pareto tradeoffs. This action primarily relates to Model selection from quantitative task metrics: Select candidate LLMs by measured task success, latency, safety and token cost, not parameter count or leaderboard rank. However, the described case — An agent endpoint gets accuracy complaints but serving logs capture only HTTP status, hiding response content and retrieval IDs. — is testing Inference logging and production trace privacy. 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. Add concise role instructions and representative input/output examples while keeping untrusted claim text in a delimited data section. 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 — An internal service team wants a citation-backed chat over equipment procedures without writing a custom agent framework. — is testing Agent Bricks Knowledge Assistant suitability. 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 authoritative structured values separate from explanatory unstructured content in the final answer. 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 — An internal service team wants a citation-backed chat over equipment procedures without writing a custom agent framework. — is testing Agent Bricks Knowledge Assistant suitability. 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. Test mismatched user and account values and confirm zero unauthorized retrieval and correct contextual answers. This action primarily relates to Query-field driven prompt and retrieval filters: User intent and structured fields such as account_id should drive authorized SQL lookups or retrieval filters, not be ignored in free text. However, the described case — A vendor proposes to copy managed model weights into an on-prem product contrary to provider terms. — is testing Open model license versus managed endpoint obligations. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Verify matched query and document vectors use the approved version and retrieval improves on held-out examples. This action primarily relates to Embedding model swap and reindex compatibility: Changed embedding dimensions or model semantics typically require re-embedding and index consistency before comparing search quality. However, the described case — A vendor proposes to copy managed model weights into an on-prem product contrary to provider terms. — is testing Open model license versus managed endpoint obligations. It does not directly establish the 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. Check embedding dimensions or extracted-field validation against task-specific acceptance tests. This action primarily relates to Specialized model versus general LLM: Embedding, reranking, extraction and generative models solve different stages and should be evaluated for their actual role. However, the described case — A vendor proposes to copy managed model weights into an on-prem product contrary to provider terms. — is testing Open model license versus managed endpoint obligations. It does not directly establish the 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 data schema, primary identifiers, change detection, UC permissions and ingestion checkpoint behavior. 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 — PDF extraction repeats a footer classification notice inside every employee policy chunk. — is testing Boilerplate and navigation filtering in source corpora. It does not directly establish the 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 — PDF extraction repeats a footer classification notice inside every employee policy chunk. — is testing Boilerplate and navigation filtering in source corpora. It does not directly establish the 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 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 — PDF extraction repeats a footer classification notice inside every employee policy chunk. — is testing Boilerplate and navigation filtering in source corpora. It does not directly establish the 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 a topic switch and anaphoric reference to ensure correct routing and no cross-session state bleed. 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 simple meeting recap bot is configured with payment and email tools despite only needing a text summary. — is testing Agent tool wrappers versus direct LLM responses. 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 simple meeting recap bot is configured with payment and email tools despite only needing a text summary. — is testing Agent tool wrappers versus direct LLM responses. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Compare repeated generations against the task rubric and format parser to detect unwanted drift. This action primarily relates to Temperature and deterministic format tradeoffs: Decoding settings can affect variability and cost but cannot replace validation, grounding or application logic. However, the described case — A simple meeting recap bot is configured with payment and email tools despite only needing a text summary. — is testing Agent tool wrappers versus direct LLM responses. 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. Register the MLflow model as a named Unity Catalog model version and grant only approved use/manage rights. 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 deployed chatbot silently uses a different embedding model from the retrieval index built in development. — is testing RAG production bundle metadata and dependencies. 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. Compare storage-optimized versus standard options, supported limits and actual query latency before selection. 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 deployed chatbot silently uses a different embedding model from the retrieval index built in development. — is testing RAG production bundle metadata and dependencies. 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. Query the relevant index with a compatible query embedding, select authorized matches and pass them to the prompt. This action primarily relates to Vector Search retrieval workflow and query integration: Semantic retrieval uses an embedding model to query a compatible index, returns ranked passages and metadata for grounded generation. However, the described case — A deployed chatbot silently uses a different embedding model from the retrieval index built in development. — is testing RAG production bundle metadata and dependencies. 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.