Databricks Certified Generative AI Engineer Associate Bundle

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 company must deploy a custom fine-tuned checkpoint with nonstandard preprocessing not offered by managed endpoints. — is testing Foundation Model API versus custom serving choices. 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 predict entrypoint, model artifacts, dependency environment, inputs and output serialization. This action primarily relates to MLflow pyfunc packaging for pre- and post-processing: A custom MLflow pyfunc model wraps request parsing, retriever/model invocation and output formatting inside a reproducible predict interface. However, the described case — A company must deploy a custom fine-tuned checkpoint with nonstandard preprocessing not offered by managed endpoints. — is testing Foundation Model API versus custom serving choices. 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 p95 latency, queue depth, rate limits, cost and per-version error traces. This action primarily relates to Endpoint scale concurrency and operational rollout: Serving latency and reliability depend on provisioned capacity, request concurrency, quotas and controlled rollout. However, the described case — A company must deploy a custom fine-tuned checkpoint with nonstandard preprocessing not offered by managed endpoints. — is testing Foundation Model API versus custom serving choices. 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. Promote a tracked model version or alias while preserving the previous model version for rollback. 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 new model signature expects messages array but the existing app sends only a prompt string. — is testing Deployed model dependency drift and environment 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 a custom serving endpoint with model packaging and scaling suitable to the checkpoint. 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 new model signature expects messages array but the existing app sends only a prompt string. — is testing Deployed model dependency drift and environment 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. 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 new model signature expects messages array but the existing app sends only a prompt string. — is testing Deployed model dependency drift and environment 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. Test model invocation under realistic throughput and verify output schema, quota and governance constraints. 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 RAG endpoint should be invoked only by the internal support group, but every workspace member can call it. — is testing Model Serving endpoint permissions and caller identity. 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 peak traffic and controlled rollback while monitoring end-to-end user outcomes. This action primarily relates to Endpoint scale concurrency and operational rollout: Serving latency and reliability depend on provisioned capacity, request concurrency, quotas and controlled rollout. However, the described case — A RAG endpoint should be invoked only by the internal support group, but every workspace member can call it. — is testing Model Serving endpoint permissions and caller identity. 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. Execute a small sample query then validate throughput, cost, failed rows and result parsing. 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 RAG endpoint should be invoked only by the internal support group, but every workspace member can call it. — is testing Model Serving endpoint permissions and caller identity. 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 extraction fields, masking policy, downstream embedded text and sensitive-data exposure paths. This action primarily relates to Sensitive-field masking before embedding: Masking or tokenization can remove unnecessary PII from chunks before embedding and external model calls while retaining useful meaning. However, the described case — A support bot incorporates competitor FAQs with usage terms that forbid automated redistribution. — is testing Training and retrieval corpus license rights. 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 support bot incorporates competitor FAQs with usage terms that forbid automated redistribution. — is testing Training and retrieval corpus license rights. 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 support bot incorporates competitor FAQs with usage terms that forbid automated redistribution. — is testing Training and retrieval corpus license rights. 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. Run side-by-side evaluations for baseline and candidate prompts with format, groundedness and latency metrics. This action primarily relates to Prompt changes evaluated against baseline: A prompt improvement should be measured against a fixed baseline set, not accepted because a few outputs sound better. However, the described case — A supply-chain assistant must call an inventory API before recommending an available replacement part. — 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. 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 supply-chain assistant must call an inventory API before recommending an available replacement part. — 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 paired representative requests and record quality versus p95 latency and cost tradeoffs. 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 supply-chain assistant must call an inventory API before recommending an available replacement part. — 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 safeguard choice for this specific question. Never grant the model blanket tool permission based only on a safe-looking input text score. This action primarily relates to Prompt safety filtering and tool allowlists: Content filters and action allowlists are complementary; a moderation score is not a substitute for authorization of external effects. However, the described case — A medical appointment chatbot replaces all dates with redaction tokens, making scheduling answers impossible. — is testing Contextual masking versus destructive data removal. 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 masking rules under regression control and treat embeddings and logs as potentially sensitive too. This action primarily relates to Sensitive-field masking before embedding: Masking or tokenization can remove unnecessary PII from chunks before embedding and external model calls while retaining useful meaning. However, the described case — A medical appointment chatbot replaces all dates with redaction tokens, making scheduling answers impossible. — is testing Contextual masking versus destructive data removal. 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 human review for borderline filtering decisions so source cleaning does not silently erase important warnings. 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 medical appointment chatbot replaces all dates with redaction tokens, making scheduling answers impossible. — is testing Contextual masking versus destructive data removal. 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. Remove unused side-effect tools and use a plain summarization chain with bounded output. 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 — An agent receives a customer message requesting deletion of every table while only ticket lookup is authorized. — is testing Unsafe model output and jailbreak response diagnosis. 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. Maintain scoped conversation state and resolve the reference to a verified invoice identifier before lookup. 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 — An agent receives a customer message requesting deletion of every table while only ticket lookup is authorized. — is testing Unsafe model output and jailbreak response diagnosis. 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 supported MLflow GenAI tracing around each model, retriever and tool operation with secret redaction. 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 — An agent receives a customer message requesting deletion of every table while only ticket lookup is authorized. — is testing Unsafe model output and jailbreak response diagnosis. 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 proposed tool call sequence, preconditions, approval gates and partial failures. 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 — A repairs workflow wants parts suggestions but does not state which serial number, failure code or stock fields matter. — 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 whether the task is grounded document Q&A, extraction, tool coordination or cross-agent orchestration. 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 repairs workflow wants parts suggestions but does not state which serial number, failure code or stock fields matter. — 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 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 — A repairs workflow wants parts suggestions but does not state which serial number, failure code or stock fields matter. — 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. Do not equate registering a model with approving its business safety or access to all governed tables. 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 developer's support chain omits the retrieved context and the LLM hallucinates policy clauses. — 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. 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 developer's support chain omits the retrieved context and the LLM hallucinates policy clauses. — 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. Enforce reproducible environment manifests and API compatibility checks in CI/CD. 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 developer's support chain omits the retrieved context and the LLM hallucinates policy clauses. — 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 diagnose choice for this specific question. Inspect extraction fields, masking policy, downstream embedded text and sensitive-data exposure paths. This action primarily relates to Sensitive-field masking before embedding: Masking or tokenization can remove unnecessary PII from chunks before embedding and external model calls while retaining useful meaning. However, the described case — A customer agent is allowed to issue account refunds but a hostile chat asks it to refund unrelated accounts. — 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 customer agent is allowed to issue account refunds but a hostile chat asks it to refund unrelated accounts. — 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 content provenance, licensing terms, rights reservations and intended distribution. 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 customer agent is allowed to issue account refunds but a hostile chat asks it to refund unrelated accounts. — 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 implement choice for this specific question. Redact or pseudonymize identity fields before vector indexing and enforce source access rules. This action primarily relates to Sensitive-field masking before embedding: Masking or tokenization can remove unnecessary PII from chunks before embedding and external model calls while retaining useful meaning. However, the described case — A customer agent is allowed to issue account refunds but a hostile chat asks it to refund unrelated accounts. — is testing Prompt safety filtering and tool allowlists. 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. Differentiate direct identifiers from permissible temporal fields and apply purpose-specific protection. 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 customer agent is allowed to issue account refunds but a hostile chat asks it to refund unrelated accounts. — is testing Prompt safety filtering and tool allowlists. 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. Obtain appropriate rights or replace manuals with licensed public documentation before ingestion. 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 customer agent is allowed to issue account refunds but a hostile chat asks it to refund unrelated accounts. — is testing Prompt safety filtering and tool allowlists. 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.