Weekend Special Sale 75% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: sale75best

Free Databricks Context-Engineer-Associate Practice Exam with Questions & Answers

Questions 1

A context engineer is designing an MCP server for a Databricks agent that connects to a catalog of 30 tools. The server uses a progressive disclosure architecture to manage a strict token budget. At startup, the agent loads only the tool names and one-sentence descriptions. After receiving a user request to query a specific Unity Catalog table, the agent evaluates the catalog, identifies one tool as the likely match, and needs to move to the next stage of the architecture.

What should the agent do in the inspect layer?

Options:
A.

Call the selected tool using parameter values inferred from the short description, since the catalog layer has already confirmed the tool identity.

B.

Fetch the full schemas and documentation for the single identified tool, then use that retrieved schema to construct a valid tool call.

C.

Retrieve an enriched summary for the selected tool that includes usage examples and defers loading parameter types until the execution layer.

D.

Load the full schemas for all 30 available tools so it can cross-validate the selected tool’s parameters against similar tools before constructing the call.

Databricks Context-Engineer-Associate Premium Access
Questions 2

A context engineer is building a retrieval-augmented generation agent on Databricks to answer questions about a large collection of legal contracts. Each contract is a structured PDF averaging 40 pages, with clearly defined sections such as “Definitions,” “Obligations,” and “Termination Clauses.” The embedding model in use has a 512-token context window. User queries are highly targeted, such as “What are the termination conditions in the indemnification clause?”, and require precise, clause-level retrieval rather than broad document summaries.

Which chunking strategy should the context engineer use?

Options:
A.

Use structure-aware chunking that splits documents at section boundaries, then further subdivides sections exceeding 400 tokens to stay within the embedding model’s context window.

B.

Apply paragraph-level chunking across all contracts, splitting each section into individual paragraphs, to maximize retrieval granularity for targeted clause queries.

C.

Split each contract into fixed-size chunks of 512 tokens with 50-token overlaps, ignoring document structure, keeping chunks within the embedding model’s context window.

D.

Embed each contract section as a single chunk without further subdivision, preserving full section context even when sections exceed the embedding model’s context window.

Questions 3

A context engineer is investigating why a Genie space serving the sales operations team gives inconsistent answers to revenue questions. When business users ask the same QUESTION NO: across different sessions, for example, “What was Q3 EMEA revenue?”, Genie returns different figures. The space is configured over a Unity Catalog managed table of transaction-level data.

On reviewing the space, the engineer finds:

The underlying table has comprehensive table and column comments.

The space’s text instructions describe how revenue should be computed, including currency conversion against a daily FX-rate table, accrual-timing rules, and intercompany-elimination logic.

The space includes several sample questions covering quarterly and regional revenue patterns.

In the query history, Genie composes a new SQL statement for the revenue calculation in each session, and the FX-conversion and elimination steps differ from run to run.

Which change will most reliably stabilize the space’s answers to this team’s revenue questions?

Options:
A.

Encapsulate the canonical revenue calculation in a parameterized Unity Catalog SQL function and register it in the space as a trusted asset.

B.

Add a complete example SQL query that performs the full revenue calculation to the space so Genie can learn the pattern.

C.

Expand the text instructions with step-by-step pseudocode for the revenue calculation, giving Genie a more explicit procedure to follow when generating SQL.

D.

Define a SQL expression for revenue in the space’s knowledge store so Genie has a reusable definition of the metric.

Questions 4

A context engineer is debugging a Databricks agent that staffs an internal IT help desk. The agent is already connected to a retrieval pipeline over a live, continuously updated knowledge base, and relevant KB passages are retrieved and placed in its context on every request. Its system prompt has three parts: a 400-token persona preamble, a 600-token list of every supported software title, and a 200-token closing instruction block. None of these parts explains how to weigh retrieved passages against the model’s own training knowledge.

Observed behavior: the agent correctly identifies the user’s intent, and the correct KB passages are present in context. However, for version-specific questions, it answers from its training knowledge and recommends releases that the knowledge base marks as deprecated. The team will accept only a change that does not rewrite the full prompt and does not add or modify retrieval infrastructure.

Which system-prompt revision addresses the version-accuracy behavior?

Options:
A.

Expand the persona preamble to state the model’s training-data cutoff date, so users understand version details may be out of date.

B.

Add a sentence to the closing instruction block telling the agent that, when retrieved passages and its own training knowledge conflict, the retrieved passages take priority.

C.

Move the 600-token software-title list to the very end of the prompt, after the closing block, so the supported-software context is the most recent thing the model reads before answering.

D.

Add a directive to the closing block requiring the agent to present every version number in a consistent format, such as semantic versioning (MAJOR.MINOR.PATCH).

Questions 5

A context engineer is examining an MLflow trace for a Databricks compliance agent mid-workflow on a quarterly regulatory review for a regional bank. The agent’s design pattern is to retrieve regulatory clauses, extract structured obligations with regional metadata and source citations, validate each obligation through the rules engine, and synthesize the audit memo from the structured intermediate plus the validation outcomes. The context window is nearing the compaction threshold, and compaction will fire before the workflow is complete.

The trace includes three executed spans and one queued span:

Span 1 (RETRIEVER): Retrieved 22 regulatory clause excerpts from the compliance vector index. Output: 22 documents (8,400 tokens) of raw clause text with metadata for source URI and section ID.

Span 2 (LLM/CHAT_MODEL): Produced a structured intermediate (410 tokens) containing three extracted compliance obligations, each annotated with a regional applicability tag describing how the bank’s state-level regulations modify the federal requirement and a source citation pointing back to the originating clause.

Span 3 (TOOL): Ran the three obligations through the rules engine and returned a structured pass/fail report (280 tokens) with one outcome entry per obligation. Each entry contains the obligation ID, the pass/fail value, and a brief explanation of the rule that determined the outcome.

Span 4 (LLM/CHAT_MODEL, queued): Will draft the compliance memo for the bank’s audit team.

Which content from the executed spans can the compactor safely summarize without affecting span 4’s execution?

Options:
A.

The 22 raw clause excerpts from span 1, because their content has been transferred forward by span 2 into the structured intermediate (with regional applicability tags and source citations preserved) that the memo synthesis works from.

B.

The structured intermediate output from span 2, because span 1’s raw regulatory clauses are the canonical source preserved verbatim for the memo’s direct source quotations and audit traceability, while span 2’s extracted obligations are intermediate analysis, the rules engine has already factored into the pass/fail report.

C.

All three executed spans, because the default compaction summary captures the agent’s state and findings, and span 4 will draft the memo from the digest, which preserves the agent’s analysis at the level needed for synthesis.

D.

The 22 raw clause excerpts from span 1 and the structured intermediate output from span 2, because everything that has been processed by a downstream operation is redundant in the active context; the pass/fail report from span 3 is the only output still doing work for the queued span.

Questions 6

A context engineer is developing a Databricks agent that autonomously manages a multi-day incident response workflow. The agent processes a continuous stream of structured log entries, tool call results, and short status updates. Recent messages tend to guide decisions, while earlier messages are often superseded by newer updates during the workflow. The engineer is considering whether to implement a hard-coded sliding-window trimming heuristic that drops messages older than a fixed turn count, or to invest in a semantic compaction approach that summarizes and condenses prior context before dropping it.

Which characteristic of this agent’s information relevance pattern justifies using the hard-coded sliding-window trimming heuristic instead of a semantic compaction approach?

Options:
A.

The agent receives frequent short status updates that individually appear low-value, but collectively encode a progression of state changes that a fixed trim threshold would maintain.

B.

The agent accumulates long-range dependencies across turns, in a way that semantic compaction would lose the granularity of faster than a fixed trim.

C.

Message relevance declines in a consistent and predictable way over time, allowing a fixed-size window to retain the necessary context without additional processing.

D.

Hard-coded trimming heuristics are typically used when managing context size constraints, independent of specific relevance patterns for one particular use case.

Questions 7

A context engineer is building a retail agent with Agent Bricks Custom Agents. The agent has two registered tools: a SQL query tool that queries a live inventory database, and a vector search tool that searches a static product catalog vector index for product descriptions, specifications, and categories. Both tools are configured correctly, function properly, and return valid results when called.

At runtime, when users ask questions such as “Is this item in stock?”, the agent consistently calls the product catalog tool and provides a plausible availability answer without checking the live inventory database. The product catalog tool is not intended to answer live stock availability questions.

Which context engineering issue explains this behavior?

Options:
A.

The product catalog vector index was built from a periodic snapshot, so it may contain stale product metadata.

B.

The tool descriptions and routing guidance are too ambiguous to distinguish live inventory availability questions from static product catalog search.

C.

The inventory tool’s description does not explicitly mention “stock,” “in stock,” or “availability,” even though it correctly queries real-time inventory when called.

D.

The agent prompt does not require source-of-truth checks before generating a final answer, so the agent treats any plausible retrieved context as sufficient.

Questions 8

A context engineer is preparing to deploy a per-tenant Databricks agent for a SaaS retail analytics platform. Each platform customer is provisioned with their own Unity Catalog catalog, retail_ & lt;customer & gt;, and within each tenant catalog, data is organized by business domain rather than by origin.

The sales schema contains the customer’s POS transaction and returns tables, which the customer’s source systems write to throughout the day, alongside the daily_sales_by_store, hourly_revenue_by_category, and top_skus_weekly summary tables that a nightly Lakeflow Jobs pipeline produces by reading those POS tables. The inventory schema contains stock-level and inbound-shipment tables written continuously by ingestion, alongside demand_forecast_7d and reorder_suggestions tables produced by the SaaS’s ML pipelines. The customer schema contains customer master records and contact tables, all populated by ingestion.

The SaaS deploys one agent per customer through Model Serving, and each agent has its own service principal. Before any agent endpoint is registered, the governance requirements are that an agent for a given customer must be able to retrieve data only from that customer’s catalog and never from another customer’s catalog, and that within its own customer’s catalog, the agent must be able to retrieve only from tables populated directly by the customer’s ingestion pipelines, never from nightly summaries, forecasts, or other tables produced by SaaS pipelines.

Which governance approach should the context engineer implement for each tenant’s agent before registration?

Options:
A.

Provision a single agent service principal shared across all tenants because per-tenant service principals are operationally heavy at the SaaS’s expected scale. Grant the shared service principal USE CATALOG on every retail_ < customer > catalog and table-level SELECT only on the ingestion-fed tables in each catalog. Configure the agent’s retrieval tool to inject the requesting customer’s catalog name into every query so the agent

B.

For each tenant’s agent service principal, grant USE CATALOG on that tenant’s retail_ < customer > catalog and USE SCHEMA together with SELECT on the sales, inventory, and customer schemas. Apply a Unity Catalog tag source=ingest to every ingestion-fed table across the tenant catalogs and configure each agent’s retrieval logic to issue queries only against tables carrying that tag.

C.

For each tenant’s agent service principal, grant USE CATALOG only on that tenant’s retail_ < customer > catalog and USE SCHEMA together with SELECT on the sales, inventory, and customer schemas, relying on the per-tenant catalog boundary to scope retrieval to the customer’s data.

D.

For each tenant’s agent service principal, grant USE CATALOG only on that tenant’s retail_ < customer > catalog and, within that catalog, grant USE SCHEMA on each domain schema together with table-level SELECT only on the tables populated by the customer’s ingestion pipelines. Leave the nightly summary, forecast, and other SaaS-produced tables in those schemas ungranted.

Questions 9

A context engineer is evaluating a target-landscape research agent at a pharmaceutical R & D organization. Discovery scientists ask the agent to prepare a structured landscape memo about a proposed drug target: what has been studied, who else is in the space, at what clinical phase, and with what regulatory history.

The agent runs as a single agent on Agent Bricks Custom Agents. It retrieves from a Databricks AI Search index built over PubMed, ClinicalTrials.gov, internal program memos, and FDA review documents, and produces the memo in one pass within a single context window.

Narrow queries (one target, one indication) produce accurate memos. Broader landscape queries return with competitor programs missing that the agent had named earlier in its own reasoning, quoted evidence attached to the wrong study, and cross-document fields partially filled. The MLflow trace shows window utilization rising toward the cap before drafting begins. One agent runs throughout.

What change should the AI engineer make to the agent architecture’s boundaries?

Options:
A.

Split the agent along the document-source axis (PubMed, ClinicalTrials.gov, internal memos, FDA reviews) and merge per-source outputs in the orchestrator.

B.

Keep the single-agent boundary and lower the within-agent compaction trigger threshold so compaction fires before the memo is drafted.

C.

Split the agent into sub-agents that scope exploration separately from synthesis, with summaries (not raw evidence) crossing the boundary into the synthesis step.

D.

Split the agent into a chain of single-step sub-agents (parse, retrieve, summarize, cluster, verify, cite, draft) connected by sequential handoffs.

Questions 10

A context engineer is building a compound AI system for a hospital network with Agent Bricks Custom Agents. The system answers clinician questions about a specific patient’s medication history. Patient records are stored in a Delta table that is continuously updated as new prescriptions, refills, and discontinuations are recorded, and clinicians must see the most current state of a patient’s record when they submit a query. HIPAA’s minimum necessary rule requires the system to retrieve only the requesting patient’s records instead of searching across the broader patient population. End-to-end latency per query must stay under two seconds.

Which retrieval strategy should the context engineer use?

Options:
A.

Use a Databricks AI Search index configured in delta-sync mode so the index automatically updates from the Delta table, and perform semantic retrieval at inference.

B.

Use just-in-time agentic retrieval by equipping the agent with a tool that executes a parameterized Delta table query scoped to the specific patient at inference time.

C.

Use a hybrid approach: precompute embeddings for all patient records nightly and supplement with just-in-time retrieval only for records modified during the day.

D.

Use pre-inference embedding-based retrieval by indexing all patient records into a Databricks AI Search index at pipeline build time and querying it semantically at inference.

Certification Provider: Databricks
Exam Name: Databricks Certified Context Engineer Associate
Last Update: Nov 21, 2026
Questions: 50
PDF + Testing Engine
$169.99
$42.5
Testing Engine
$129.99
$32.5
PDF (Q&A)
$104.99
$26.25

Databricks Free Exams

Databricks Free Exams
Examstrack provides free Databricks exam prep materials and practice tests to support your Databricks certification goals.