Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest verify choice for this specific question. Document legal clearance and confirm the deployed artifact matches the approved license/version. This action primarily relates to Open model license versus managed endpoint obligations: Model availability on a hub does not itself confer commercial training, redistribution or hosting rights. However, the described case — A team switches from a 768-dimensional embedding model to a 1024-dimensional model while keeping the same vector index. — is testing Embedding model swap and reindex compatibility. 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 team switches from a 768-dimensional embedding model to a 1024-dimensional model while keeping the same vector index. — is testing Embedding model swap and reindex compatibility. 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 reproducible pairwise experiments with confidence and segment-level result analysis. 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 switches from a 768-dimensional embedding model to a 1024-dimensional model while keeping the same vector index. — is testing Embedding model swap and reindex compatibility. 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 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 — 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 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 business decision, data owners, actor permissions, known inputs and success 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 — 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 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 — 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 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 flagged passages, content provenance, approval status and observed retrieval matches. 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 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 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 fields are necessary, masking false positives and any leaked sensitive fields. 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 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 — 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 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 — 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 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 — 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 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 output type, input modality and measured task capability rather than model size alone. 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 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. Compare both models on the same held-out support questions, citations, cost and safety cases. 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 medical summarization product considers a model evaluated only on short English news articles. — is testing Model cards and task-specific limitations. 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 mistake text masking for permission checks, lawful data use or complete safety assurance. 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 medical summarization product considers a model evaluated only on short English news articles. — is testing Model cards and task-specific limitations. 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. Choose asynchronous batch throughput and cost targets rather than paying for interactive latency. This action primarily relates to Latency, cost and retrieval targets as design requirements: A valid pipeline design has measurable quality, latency, token and throughput constraints before model selection. 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 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. Evaluate a summarization model against faithful concise summaries with source references. 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 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. Retrieve schedule and fare restrictions, solicit explicit confirmation, then invoke booking and record confirmation. 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 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. 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 product catalog has 85 million vectors with stringent p95 search latency and frequent incremental updates. — is testing Standard versus storage-optimized Vector Search index. 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. Treat index freshness as a monitored dependency of source-document correctness. 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 product catalog has 85 million vectors with stringent p95 search latency and frequent incremental updates. — is testing Standard versus storage-optimized Vector Search index. 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 present nearest neighbors as verified answers without evidence validation and permission checks. 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 product catalog has 85 million vectors with stringent p95 search latency and frequent incremental updates. — is testing Standard versus storage-optimized Vector Search index. 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 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 compliance RAG app splits a numbered contract clause so exclusions are separated from the obligation. — is testing Semantic boundaries versus fixed-window chunks. 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 compliance RAG app splits a numbered contract clause so exclusions are separated from the obligation. — is testing Semantic boundaries versus fixed-window chunks. 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 compliance RAG app splits a numbered contract clause so exclusions are separated from the obligation. — is testing Semantic boundaries versus fixed-window chunks. 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. Never equate a successful embedding API call with a governed and reproducible source-data pipeline. 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 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 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 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 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. Route documents by actual format and flag low-confidence extraction rather than silently indexing blank text. 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 — 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 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. Rerun a controlled experiment and confirm metrics match within expected stochastic tolerance. 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 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 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 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 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 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 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. Do not hide expert disagreement by excluding difficult cases or averaging away severe failures. This action primarily relates to Human SME feedback rubric and reviewer calibration: Domain experts should use a shared rubric, calibrate disagreements and maintain adjudicated examples to improve model evaluation. However, the described case — A support RAG app fails some answers, but team cannot tell whether retrieval or generation caused each error. — is testing MLflow GenAI tracing, built-in and custom scorers. 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 usage monitoring and budgets to detect regressions when prompts, indexes or models change. 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 support RAG app fails some answers, but team cannot tell whether retrieval or generation caused each error. — is testing MLflow GenAI tracing, built-in and custom scorers. 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. Revisit the choice as workload and evaluation data change instead of permanently trusting benchmark ranking. 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 — A support RAG app fails some answers, but team cannot tell whether retrieval or generation caused each error. — is testing MLflow GenAI tracing, built-in and custom scorers. 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.