Databricks Certified Generative AI Engineer Associate Bundle

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.

Not the strongest implement 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 — An agent promotion script overwrites the only model file without retaining the prior validated artifact. — is testing Unity Catalog registered model version and privileges. 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 an authenticated Databricks App backend that invokes the agent and enforces user-specific data permissions. This action primarily relates to Databricks Apps user-facing agent interface and OAuth identities: Databricks Apps supports authenticated interactive frontends; app credentials and user credentials have different scopes. However, the described case — An agent promotion script overwrites the only model file without retaining the prior validated artifact. — is testing Unity Catalog registered model version and privileges. 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. Resolve the authorized production alias at runtime using a controlled refresh strategy. 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 — An agent promotion script overwrites the only model file without retaining the prior validated artifact. — is testing Unity Catalog registered model version and privileges. 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. 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 compliance agent needs both a Unity Catalog table result and an approved policy passage for each answer. — is testing Parallel retrieval and deterministic chain postprocessing. 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. Retain audit trails and constrain retries, tool permissions and approval for high-impact actions. 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 compliance agent needs both a Unity Catalog table result and an approved policy passage for each answer. — is testing Parallel retrieval and deterministic chain postprocessing. 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 instructions and examples versioned and test new patterns without allowing retrieved data to override policy. 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 compliance agent needs both a Unity Catalog table result and an approved policy passage for each answer. — is testing Parallel retrieval and deterministic chain postprocessing. 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. Review model license and select an authorized commercial alternative before deployment. 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 — An engineer changes the source chunking but keeps old stored embeddings and assumes retrieval reflects the new boundaries. — 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. Select a candidate with measured language coverage and document residual risk on target-language samples. 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 — An engineer changes the source chunking but keeps old stored embeddings and assumes retrieval reflects the new boundaries. — 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. Require preproduction evaluation on curated labeled examples and later observe production quality. 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 — An engineer changes the source chunking but keeps old stored embeddings and assumes retrieval reflects the new boundaries. — 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 diagnose choice for this specific question. Inspect scorer rubric, available trace spans, model response and known evaluation references. 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 — Four reviewers rate the same policy answers inconsistently and the team cannot determine whether prompt changes help. — is testing Human SME feedback rubric and reviewer calibration. 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 production trace quality, error types, latency percentiles, user feedback and alert routes. 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 — Four reviewers rate the same policy answers inconsistently and the team cannot determine whether prompt changes help. — is testing Human SME feedback rubric and reviewer calibration. 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 token volumes, QPS, endpoint pricing, cache hit rate and user/workload attribution. This action primarily relates to Databricks usage and token cost controls: Reduce LLM spend through token budgets, caching, smaller appropriate models and AI Gateway quotas while preserving acceptance quality. However, the described case — Four reviewers rate the same policy answers inconsistently and the team cannot determine whether prompt changes help. — is testing Human SME feedback rubric and reviewer calibration. 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. Sign in as two users with different UC rights and confirm their answers cannot expose each other's data. This action primarily relates to Databricks Apps user-facing agent interface and OAuth identities: Databricks Apps supports authenticated interactive frontends; app credentials and user credentials have different scopes. 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 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. Load an explicitly registered version and confirm its dependencies and outputs match the approved evaluation run. 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 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 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. Exercise failed tests and confirm release is blocked, then deploy and verify a passing version. 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 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 verify outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest safeguard choice for this specific question. Do not 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 finance controller wants a one-paragraph explanation of a long audit memo, not a risk score. — is testing Task choice: classification versus generative summarization. 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 instructions and examples versioned and test new patterns without allowing retrieved data to override policy. 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 finance controller wants a one-paragraph explanation of a long audit memo, not a risk score. — is testing Task choice: classification versus generative summarization. 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. Retain audit trails and constrain retries, tool permissions and approval for high-impact actions. 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 finance controller wants a one-paragraph explanation of a long audit memo, not a risk score. — is testing Task choice: classification versus generative summarization. It does not directly establish the safeguard outcome or constraint that the question requires; it may still be useful in a different stage or incident.

Not the strongest diagnose choice for this specific question. Inspect table extraction, repeated column headings, units, row identity and exact filter fields. This action primarily relates to Table-aware chunking and metadata-rich retrieval: Tabular rows need headers, units and column semantics preserved when transformed into retrieval documents. However, the described case — 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 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 lexical token overlap, dense distance, metadata predicates and index access control. 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 — 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 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 token distribution, overlap proportion, expected retrieval granularity and vector count. 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 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. Choose a rubric or pairwise assessment suitable for open answers rather than exact string equality. This action primarily relates to Ground-truth requirement for correctness versus reference-free judges: A correctness comparison often needs an expected answer; other judges such as format or safety can operate without a reference. However, the described case — A travel agent meets its average response time but p99 exceeds 30 seconds during peak traffic. — is testing Production performance KPIs and incident thresholds. 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 supported AI Gateway endpoint quotas or rate limits by workload and inspect usage traces. 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 — A travel agent meets its average response time but p99 exceeds 30 seconds during peak traffic. — is testing Production performance KPIs and incident thresholds. 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 a fit-for-task model, batching and usage thresholds with per-request cost monitoring. This action primarily relates to Databricks usage and token cost controls: Reduce LLM spend through token budgets, caching, smaller appropriate models and AI Gateway quotas while preserving acceptance quality. However, the described case — A travel agent meets its average response time but p99 exceeds 30 seconds during peak traffic. — is testing Production performance KPIs and incident thresholds. 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 extracted schema completeness or supervisor routing correctness on representative multi-step cases. This action primarily relates to Agent Bricks Information Extraction versus Multiagent Supervisor: Information Extraction maps source documents to structured fields; Multiagent Supervisor coordinates specialized capabilities for compound workflows. 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 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 adversarial quoted-text tests and compare output structure on representative and edge inputs. 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 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 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 answer fidelity, citation paths and forbidden document access across test identities. 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 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. Exercise failed tests and confirm release is blocked, then deploy and verify a passing version. 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 support agent times out at peak demand because requests exceed the configured endpoint throughput. — is testing Endpoint scale concurrency and operational rollout. 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 a new source chunk and a retired chunk to confirm expected inclusion and removal. 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 support agent times out at peak demand because requests exceed the configured endpoint throughput. — is testing Endpoint scale concurrency and operational rollout. 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. Sign in as two users with different UC rights and confirm their answers cannot expose each other's data. This action primarily relates to Databricks Apps user-facing agent interface and OAuth identities: Databricks Apps supports authenticated interactive frontends; app credentials and user credentials have different scopes. However, the described case — A support agent times out at peak demand because requests exceed the configured endpoint throughput. — is testing Endpoint scale concurrency and operational rollout. 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.