Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest verify choice for this specific question. Exercise failed tests and confirm release is blocked, then deploy and verify a passing version. 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 support agent times out at peak demand because requests exceed the configured endpoint throughput. — is testing Endpoint scale concurrency and operational rollout. 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. Query a new source chunk and a retired chunk to confirm expected inclusion and removal. This action primarily relates to Databricks Vector Search index from governed Delta data: A vector index serves embeddings of chunked records maintained in a Unity Catalog governed Delta source table. However, the described case — A support agent times out at peak demand because requests exceed the configured endpoint throughput. — is testing Endpoint scale concurrency and operational rollout. 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. Sign in as two users with different UC rights and confirm their answers cannot expose each other's data. This action primarily relates to Databricks Apps user-facing agent interface and OAuth identities: Databricks Apps supports authenticated interactive frontends; app credentials and user credentials have different scopes. However, the described case — A support agent times out at peak demand because requests exceed the configured endpoint throughput. — is testing Endpoint scale concurrency and operational rollout. 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. 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 — A support search returns five unrelated policy pages while the correct refund clause is at rank 20. — is testing Retrieval recall precision and ranking diagnostics. 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 both rare identifiers and paraphrased questions with strict cross-tenant non-disclosure checks. 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 support search returns five unrelated policy pages while the correct refund clause is at rank 20. — is testing Retrieval recall precision and ranking diagnostics. 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 that an exception and its definition are available to the generator after retrieval. 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 support search returns five unrelated policy pages while the correct refund clause is at rank 20. — is testing Retrieval recall precision and ranking diagnostics. It does not directly establish the verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest verify choice for this specific question. Simulate a 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 — A chatbot owner demands exact reference-match scoring for open-ended helpfulness with many valid phrasings. — is testing Ground-truth requirement for correctness versus reference-free judges. 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. Reproduce a failing request and verify a sanitized trace contains enough evidence to diagnose it. This action primarily relates to Inference logging and production trace privacy: Inference logs and tracing permit diagnosis of real issues but must be sampled, retained and redacted safely. However, the described case — A chatbot owner demands exact reference-match scoring for open-ended helpfulness with many valid phrasings. — is testing Ground-truth requirement for correctness versus reference-free judges. 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. Benchmark per-answer cost and quality on representative traffic before promoting optimizations. 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 chatbot owner demands exact reference-match scoring for open-ended helpfulness with many valid phrasings. — is testing Ground-truth requirement for correctness versus reference-free judges. 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. 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 retrieved internal wiki page embeds a fake system instruction to grant an attacker access to all support tickets. — is testing Input guardrails against prompt-injected source documents. 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 retrieved internal wiki page embeds a fake system instruction to grant an attacker access to all support tickets. — is testing Input guardrails against prompt-injected source documents. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Use a evaluated classification model and return a bounded label with confidence/abstention handling. This action primarily relates to Task choice: classification versus generative summarization: Classification predicts a category whereas summarization compresses meaning; the desired output determines the appropriate task. However, the described case — Accounts payable needs supplier name, invoice date and line items extracted into typed columns from PDFs. — is testing Agent Bricks Information Extraction versus Multiagent Supervisor. 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 let an agent execute an irreversible action solely because a retrieved paragraph requests it. This action primarily relates to Tool ordering and error isolation in multi-stage reasoning: An agent should retrieve authoritative context before taking consequential actions and validate tool outcomes at each stage. However, the described case — Accounts payable needs supplier name, invoice date and line items extracted into typed columns from PDFs. — is testing Agent Bricks Information Extraction versus Multiagent Supervisor. 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. Pass both the user question and selected passages into the prompt template before invoking the model. 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 shipping chatbot returns a list with inconsistent property names, breaking the downstream parcel status renderer. — is testing Structured JSON schema prompt and format compliance. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Do not treat model fluency or demo satisfaction as a substitute for measurable business acceptance criteria. This action primarily relates to Translate use-case requirements into pipeline inputs and outputs: Business acceptance criteria must map to concrete source inputs, generated fields, correctness measures and permission constraints. However, the described case — A shipping chatbot returns a list with inconsistent property names, breaking the downstream parcel status renderer. — is testing Structured JSON schema prompt and format compliance. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Do not equate an LLM judge score with unquestionable ground truth; calibrate against reviewed labels. 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 — An internal assistant sends 40,000 irrelevant tokens to the LLM for every short FAQ question. — is testing Databricks usage and token cost controls. 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. Choose the candidate meeting the agreed citation-quality threshold and p95 latency with lower cost. 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 internal assistant sends 40,000 irrelevant tokens to the LLM for every short FAQ question. — is testing Databricks usage and token cost controls. 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. Compare fixed evaluation queries on baseline and candidate retrieval with confidence in differences. 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 troubleshooting guide's symptom and resolution are in separate sections when cut every 400 characters. — is testing Semantic boundaries versus fixed-window chunks. 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 precision at k before and after cleaning while checking no required policy sentences were removed. 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 troubleshooting guide's symptom and resolution are in separate sections when cut every 400 characters. — is testing Semantic boundaries versus fixed-window chunks. 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 both rare identifiers and paraphrased questions with strict cross-tenant non-disclosure checks. 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 troubleshooting guide's symptom and resolution are in separate sections when cut every 400 characters. — is testing Semantic boundaries versus fixed-window chunks. 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 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 helpdesk bot sends full payment card numbers to an external model for a simple FAQ answer. — is testing PII masking and output moderation as complementary guardrails. It does not directly establish the 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 helpdesk bot sends full payment card numbers to an external model for a simple FAQ answer. — is testing PII masking and output moderation as complementary guardrails. It does not directly establish the 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 helpdesk bot sends full payment card numbers to an external model for a simple FAQ answer. — is testing PII masking and output moderation as complementary guardrails. It does not directly establish the 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 deployed agent hardcodes prompt version 1, so validated updates never reach the application. — is testing MLflow Prompt Registry version aliases and promotion. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect 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 deployed agent hardcodes prompt version 1, so validated updates never reach the application. — is testing MLflow Prompt Registry version aliases and promotion. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect 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 — A deployed agent hardcodes prompt version 1, so validated updates never reach the application. — is testing MLflow Prompt Registry version aliases and promotion. It does not directly establish the diagnose outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Version embeddings with source and model identifiers to prevent silently mixing incompatible representations. This action primarily relates to Embedding model swap and reindex compatibility: Changed embedding dimensions or model semantics typically require re-embedding and index consistency before comparing search quality. However, the described case — A support assistant retrieves a full 60-page manual and overwhelms the model prompt with unrelated sections. — is testing Chunk quality evaluation and boundary splitting. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Never compare metrics from non-equivalent data snapshots as if they were a paired model test. This action primarily relates to Experiment tracking and version reproducibility: MLflow experiments should retain prompt, model, dataset, parameters and evaluation outputs to support a defensible comparison. However, the described case — A support assistant retrieves a full 60-page manual and overwhelms the model prompt with unrelated sections. — is testing Chunk quality evaluation and boundary splitting. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Reassess tokenizer and context limits when switching embedding models or input languages. 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 support assistant retrieves a full 60-page manual and overwhelms the model prompt with unrelated sections. — is testing Chunk quality evaluation and boundary splitting. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.