Databricks Certified Generative AI Engineer Associate Bundle

Not the strongest implement choice for this specific question. Use the managed Genie connector alongside a narrowly scoped custom MCP server for ticket actions. This action primarily relates to Managed versus external versus custom MCP server integration: MCP standardizes tool discovery; managed servers reduce hosting, external services need credentials and custom servers wrap bespoke actions. 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 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 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 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. Register immutable prompt versions, evaluate staging and move the approved production alias. 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 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 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 runnable input/output schemas, prompt variables and invocation traces around the failing stage. 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 adds 'be helpful' to a system prompt, and responses become longer but less grounded. — 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 team adds 'be helpful' to a system prompt, and responses become longer but less grounded. — 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 team adds 'be helpful' to a system prompt, and responses become longer but less grounded. — 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 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 internal employee portal wants a Streamlit RAG chat UI over governed policy and private team data. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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. 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 — An internal employee portal wants a Streamlit RAG chat UI over governed policy and private team data. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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 — An internal employee portal wants a Streamlit RAG chat UI over governed policy and private team data. — is testing Databricks Apps user-facing agent interface and OAuth identities. 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. Separate low-trust quoted input from higher-priority task instructions and include an example that preserves the schema. 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 order-status assistant needs real-time package state plus the carrier's public shipping policy. — is testing Parallel retrieval and deterministic chain postprocessing. 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 — An order-status assistant needs real-time package state plus the carrier's public shipping policy. — is testing Parallel retrieval and deterministic chain postprocessing. 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 validated ticket fields and a stable idempotency key with bounded retry handling. 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 — An order-status assistant needs real-time package state plus the carrier's public shipping policy. — is testing Parallel retrieval and deterministic chain postprocessing. 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 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 — A team wants to deploy a new prompt based solely on improving live thumbs-up counts. — is testing Offline evaluation versus ongoing production monitoring. 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 trace context passages, token distribution, coverage of necessary conditions and retrieval rank. This action primarily relates to Chunk quality evaluation and boundary splitting: Retrieval failure can arise from overly small chunks that omit needed context or overly large chunks that dilute relevance. However, the described case — A team wants to deploy a new prompt based solely on improving live thumbs-up counts. — is testing Offline evaluation versus ongoing production monitoring. 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 license text, model provenance, intended distribution and operational hosting constraints. 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 wants to deploy a new prompt based solely on improving live thumbs-up counts. — is testing Offline evaluation versus ongoing production monitoring. 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. 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 chain logged under Python package version A fails to deserialize when the model serving image ships incompatible version B. — is testing Deployed model dependency drift and environment compatibility. 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. 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 chain logged under Python package version A fails to deserialize when the model serving image ships incompatible version B. — is testing Deployed model dependency drift and environment compatibility. 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 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 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 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 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 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 model type, deployment control, supported region, endpoint quotas and operational burden. 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 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. Specify a stable array-of-objects schema, require only the specified keys and reject malformed results before rendering. 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 travel agent books a flight before checking ticket rules and traveler approval. — is testing Tool ordering and error isolation in multi-stage reasoning. 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. Separate low-trust quoted input from higher-priority task instructions and include an example that preserves the schema. 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 — A travel agent books a flight before checking ticket rules and traveler approval. — is testing Tool ordering and error isolation in multi-stage reasoning. 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. Translate SLA into retrieval latency, time-to-first-token, maximum context and quality floor for candidate designs. 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 travel agent books a flight before checking ticket rules and traveler approval. — is testing Tool ordering and error isolation in multi-stage reasoning. 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. Retest prompt injection protections whenever new retrieval connectors or tools are introduced. 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 RAG assistant passes an internal evaluation set but receives complaints about new policy terms after launch. — is testing Offline evaluation versus ongoing production monitoring. 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. Reject unsupported suitability assumptions and benchmark clinical-document handling with proper controls. 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 RAG assistant passes an internal evaluation set but receives complaints about new policy terms after launch. — is testing Offline evaluation versus ongoing production monitoring. 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 assume a managed Foundation Model endpoint grants unrestricted training rights or satisfies data residency automatically. 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 team persists all raw conversations in an unprotected shared cache to preserve agent memory. — is testing Persistent conversation memory with authorized datastore. 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 team persists all raw conversations in an unprotected shared cache to preserve agent memory. — is testing Persistent conversation memory with authorized datastore. 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. Set load thresholds and versioned fallback rather than assuming a single demo proves production scalability. 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 team persists all raw conversations in an unprotected shared cache to preserve agent memory. — is testing Persistent conversation memory with authorized datastore. 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. Build a CI gate for prompt schema, retrieval relevance, agent tools and controlled promotion across environments. 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 chain logged under Python package version A fails to deserialize when the model serving image ships incompatible version B. — 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. 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 chain logged under Python package version A fails to deserialize when the model serving image ships incompatible version B. — 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. Log the app with dependency requirements, retrieval configuration, model signature and example requests. 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 chain logged under Python package version A fails to deserialize when the model serving image ships incompatible version B. — 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.