Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest diagnose choice for this specific question. Inspect whether the task requires real external state, permitted action or just text transformation. This action primarily relates to Agent tool wrappers versus direct LLM responses: A tool-using agent needs explicit callable interfaces and typed tool results, whereas plain generation requires no action execution. However, the described case — A support assistant reveals hidden instructions when users ask it to ignore the normal helpdesk policy. — is testing Unsafe model output and jailbreak response diagnosis. 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 decoding parameters, expected output variance, schema requirements and task acceptance criteria. 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 support assistant reveals hidden instructions when users ask it to ignore the normal helpdesk policy. — is testing Unsafe model output and jailbreak response diagnosis. 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 support assistant reveals hidden instructions when users ask it to ignore the normal helpdesk policy. — is testing Unsafe model output and jailbreak response diagnosis. 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 — After an ingestion rerun, duplicate chunks multiply because the pipeline only appends without source identity. — is testing Delta and Unity Catalog pipeline for chunk tables. 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. Choose coherent chunks large enough to keep cause and remedy together without exceeding embedding limits. 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 — After an ingestion rerun, duplicate chunks multiply because the pipeline only appends without source identity. — is testing Delta and Unity Catalog pipeline for chunk tables. 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 OCR-capable extraction step, evaluate recognition quality and retain source page provenance. 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 — After an ingestion rerun, duplicate chunks multiply because the pipeline only appends without source identity. — is testing Delta and Unity Catalog pipeline for chunk tables. 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 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 benefits RAG assistant cites a real policy page but its claimed deadline does not appear in the cited passage. — 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 benefits RAG assistant cites a real policy page but its claimed deadline does not appear in the cited passage. — 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 user conversation state, current intent, entity resolution and selected tool trace. 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 benefits RAG assistant cites a real policy page but its claimed deadline does not appear in the cited passage. — 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 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 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 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. Increase suitable chunk length and reduce unnecessary overlap while checking passage-level answer recall. 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 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 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. Use access-controlled persistent storage with retention and sensitive-field minimization. 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 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 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. Bundle compatible index/embedding identifiers and validate query-embedding compatibility at initialization. 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 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 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. Run the supported index update/sync process and verify the indexed source identifiers reflect current Delta records. 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 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 implement 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 each source connector's contract, join keys, runtime error handling and the final prompt inputs. 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 HR help desk says it wants 'AI answers' without specifying which employee documents users may see. — is testing Translate use-case requirements into pipeline inputs and outputs. 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. Identify whether the output is a category, extractive field, free-form summary or grounded answer. 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 — An HR help desk says it wants 'AI answers' without specifying which employee documents users may see. — is testing Translate use-case requirements into pipeline inputs and outputs. 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 prompt hierarchy, few-shot coverage, untrusted-data delimiters and observed format deviations. 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 HR help desk says it wants 'AI answers' without specifying which employee documents users may see. — is testing Translate use-case requirements into pipeline inputs and outputs. 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. 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 — An agent needs governed Genie metrics plus a company-only ticket system exposed through a custom API. — is testing Managed versus external versus custom MCP server integration. 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 store sensitive chat traces indefinitely merely because longer memory improves convenience. 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 — An agent needs governed Genie metrics plus a company-only ticket system exposed through a custom API. — is testing Managed versus external versus custom MCP server integration. 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. Configure a Knowledge Assistant over approved documents and validate source attribution and group permissions. 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 claims assistant answers in different tones because the prompt has no consistent example or response constraints. — is testing Instruction hierarchy and bounded prompt examples. 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. Define the equipment identifiers, failure observations and inventory query as required inputs, with approved part IDs as outputs. 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 claims assistant answers in different tones because the prompt has no consistent example or response constraints. — is testing Instruction hierarchy and bounded prompt examples. 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 — A claims assistant answers in different tones because the prompt has no consistent example or response constraints. — is testing Instruction hierarchy and bounded prompt examples. 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. Inject the hostile PDF and verify no secret leaves the backend and no unauthorized tool is invoked. 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 public review feed contains slurs and adversarial instructions that surface in a brand-support assistant. — is testing Toxic, inaccurate and adversarial corpus cleaning. 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 indexed chunks against a rights manifest and confirm prohibited sources are excluded. 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 public review feed contains slurs and adversarial instructions that surface in a brand-support assistant. — is testing Toxic, inaccurate and adversarial corpus cleaning. 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 usefulness and privacy leakage metrics on held-out documents before and after selective masking. 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 public review feed contains slurs and adversarial instructions that surface in a brand-support assistant. — is testing Toxic, inaccurate and adversarial corpus cleaning. 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 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 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 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 task difficulty, expected concurrency, context size, throughput and model benchmark evidence. This action primarily relates to Model selection by quality latency and budget: Select the smallest suitable model that meets a task's accuracy and latency constraints under realistic workload, not marketing rank. 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 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 experiment runs, source versions, parameter drift and metric definitions. 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 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 deploy pipeline overwrites the production prompt text each release and cannot restore yesterday's known-good response. — 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 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 deploy pipeline overwrites the production prompt text each release and cannot restore yesterday's known-good response. — 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 package lockfile, model signature, serving logs and API contract differences. 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 deploy pipeline overwrites the production prompt text each release and cannot restore yesterday's known-good response. — 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.