Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest safeguard choice for this specific question. Use an available Foundation Model API endpoint with compatible authentication, task API and quotas. 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 LangChain pipeline returns an SDK message object while its API gateway expects a plain answer string. — is testing Simple prompt-retrieval-generation chain assembly. 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 prompt alias updates as change-controlled deployments with regression gates and auditing. 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 LangChain pipeline returns an SDK message object while its API gateway expects a plain answer string. — is testing Simple prompt-retrieval-generation chain assembly. 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. Rerank a sufficiently broad candidate pool then pass a smaller high-relevance set to the LLM. 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 — 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 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 tenant identity metadata filters before or during retrieval and use hybrid ranking within that scope. 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 — 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 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 — 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 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. Keep the retriever as an independent runnable stage and swap model components under the same interface. This action primarily relates to LangChain runnable composition and invocation: Composable runnable chains pass typed values between retrieval, prompt and model stages; each binding must preserve expected input keys. 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 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 coding success with executable tests and cost/latency rather than generic chat ratings. 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 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. Split the section at legal boundaries and preserve exceptions rather than allowing implicit truncation. 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 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 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. 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 invoice extraction agent passes generic relevance judges but loses an essential invoice currency field. — is testing MLflow GenAI tracing, built-in and custom scorers. 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 — An invoice extraction agent passes generic relevance judges but loses an essential invoice currency field. — is testing MLflow GenAI tracing, built-in and custom scorers. 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 sampled live traces and demonstrate a complaint can be reproduced and scored on an offline test. This action primarily relates to Inference tables and Agent Monitoring feedback loop: Inference tables and agent monitoring capture production request/response signals and traces for quality investigations. However, the described case — An invoice extraction agent passes generic relevance judges but loses an essential invoice currency field. — is testing MLflow GenAI tracing, built-in and custom scorers. 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. Benchmark a supported index type and provision for the expected vector count, latency and update pattern. 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 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 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 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 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. Deploy synchronized index definitions and validate source freshness during production cutover. 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 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 — A live call-center assistant must respond under three seconds and keep per-call model cost bounded. — is testing Latency, cost and retrieval targets as design requirements. 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 — A live call-center assistant must respond under three seconds and keep per-call model cost bounded. — is testing Latency, cost and retrieval targets as design requirements. 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 — A live call-center assistant must respond under three seconds and keep per-call model cost bounded. — is testing Latency, cost and retrieval targets as design requirements. 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 request/response sensitive spans, redaction logs, moderation findings and business exceptions. 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 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 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 tool-call traces, retrieved source text and permission decisions for instruction-origin confusion. This action primarily relates to Prompt-injection defenses for retrieved context: Retrieved content is lower-trust data; embedded instructions must not trigger privileged tool calls or override assistant rules. 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 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 nested traces, span order, tool duration and captured payload security. 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 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 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 use a document-answering assistant as an autonomous transaction engine without explicit tools and approvals. 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 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 cost/latency budgets whenever context window or retrieval size changes significantly. 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 — 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 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 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 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. Pin compatible dependencies and rebuild/evaluate the serving artifact before promoting a new environment. 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 policy chatbot creates vectors but never passes retrieved passages to the LLM, producing unsupported recommendations. — is testing Vector Search retrieval workflow and query 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. Treat prompt alias updates as change-controlled deployments with regression gates and auditing. 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 policy chatbot creates vectors but never passes retrieved passages to the LLM, producing unsupported recommendations. — is testing Vector Search retrieval workflow and query 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 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 compliance summary app adds examples but stops honoring the one-line required answer format. — is testing Prompt changes evaluated against baseline. 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 compliance summary app adds examples but stops honoring the one-line required answer format. — is testing Prompt changes evaluated against baseline. 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 compliance summary app adds examples but stops honoring the one-line required answer format. — is testing Prompt changes evaluated against baseline. 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. Trace retriever and generator spans, score passage relevance and answer faithfulness separately. 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 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 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. Enable authorized usage/inference tracking and per-principal attribution with clear quota alerts. 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 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. Monitor tail latency, timeout rate and affected user experience under representative load. 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 implement outcome or constraint that the question requires; it may still be useful in a different stage or incident.