Black Friday VIP Hour Limited Time 75% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = simple75

Pass the Databricks Context Engineer Context-Engineer-Associate Questions and answers with Dumpstech

Exam Context-Engineer-Associate Premium Access

View all detail and faqs for the Context-Engineer-Associate exam

Practice at least 50% of the questions to maximize your chances of passing.
Viewing page 1 out of 2 pages
Viewing questions 1-10 out of questions
Questions # 1:

A context engineer maintains a Databricks-based assistant for a fraud investigation team. Each investigation is a long-running thread that the team works on across many sessions over weeks or months. Investigations are typically handled by two or three analysts who rotate in and out as new evidence arrives, and any one analyst is usually working several open investigations at the same time. The assistant runs on Agent Bricks Custom Agents with a single retrieval tool over a Databricks AI Search index of the team’s case file corpus (incident reports, suspect dossiers, transaction logs, exhibits), synced nightly from the source Delta tables that the case management system writes to. The retrieval tool is called with num_results=50. The system has been in production for nine months.

The team begins reporting that the assistant treats every new session as a cold start. The most recent example: on Friday, analyst A and the assistant work together on an active investigation. By the end of the session, they have eliminated two suspects on alibi evidence, confirmed a third as the likely actor, and identified two specific accounts as the transfer pathway for the funds in question. On Monday, analyst B opens the assistant against the same investigation to draft the next subpoena request. The assistant responds by asking who the suspect is, what the eliminations were, and which accounts are in scope. The engineer reproduces the pattern across other investigations: within a single session, the assistant reasons well; the next session, regardless of which analyst opens it, starts cold.

What change should the engineer make to address this pattern?

Options:

A.

Add a case-scoped persistent memory store (a Unity Catalog Delta table keyed by case_id) and wire the agent with a tool that writes a structured summary of each session’s conclusions (eliminations, confirmations, key entities, decisions) to the store at session end and a tool that fetches the active case’s entries at session start so the prior conclusions enter the context before the analyst’s first message.

B.

Add a per-analyst session history store (a Unity Catalog Delta table keyed by analyst user ID where the agent appends each completed session’s conversation transcript) and have the assistant fetch the analyst’s recent transcripts at session start and include them in the context so prior work carries over.

C.

Raise num_results on the case vector index from 50 to 150 and add a client-side similarity-score floor of 0.25, so that a wider net of case-relevant chunks reaches the assistant at the start of each session and the prior context surfaces alongside the analyst’s first message.

D.

Replace the nightly Delta sync on the case index with Lakeflow Connect streaming ingestion so that the most recent activity on the investigation lands in the vector index within minutes of being created and is available at every session start.

Questions # 2:

A context engineer runs a finance Q & A agent on Databricks. The agent invokes a Genie space backed by tables in the finance.silver schema, and Genie chooses which table to query for each user QUESTION NO: by reading Unity Catalog table and column metadata. Two tables exist in the schema: revenue and revenue_gross.

MLflow evaluation runs show the Correctness scorer flagging frequent failures in which Genie queries revenue_gross when the user asks about net revenue, and queries revenue when the user asks about gross figures. Both tables are in active production use and must remain available to the Genie space, and the same disambiguation should be usable by other Genie spaces and BI consumers building against the same schema.

Which intervention resolves this failure?

Options:

A.

Add COMMENT text on both tables and their columns in Unity Catalog that clearly distinguishes the two tables – what each represents, the units, and the basis, so Genie reads the disambiguating descriptions when routing each user question.

B.

Apply a Unity Catalog certified-status tag to revenue and a deprecated-status tag to revenue_gross so that downstream consumers treat revenue as the authoritative source.

C.

Add a Genie space instruction at the space level stating which table to use for net-revenue questions and which to use for gross-revenue questions, so Genie applies the rule when routing each user question.

D.

Apply a custom Unity Catalog tag categorizing one table as the primary revenue source and the other as a secondary view, so Genie’s tool selection prefers the primary.

Questions # 3:

A context engineer is debugging a Databricks agent that supports a multi-turn customer support application. The agent keeps a running summary of all conversation history across every user session in a single vector index and retrieves it on every turn through semantic search. Users report that the agent loses track of facts stated earlier in the same session, while unrelated details from other users’ past sessions appear unexpectedly. Latency has also increased as conversation volume grows.

Which storage configuration correctly resolves the memory type mismatch that is causing this degraded behavior?

Options:

A.

Partition the vector index by user ID and session ID so that semantic retrieval is scoped per session, preventing cross-session bleed while reserving long-term facts for all users.

B.

Use a session-scoped short-term buffer to retain all within-session conversation turns, and reserve the vector store for durable cross-session user facts retrieved by semantic search.

C.

Replace the vector index with a relational table partitioned by session ID, and retrieve all rows matching the current session on every turn to maintain full conversational context for both short-term and long-term memory needs.

D.

Use a session-scoped short-term buffer to retain all within-turn context, and write a full conversation summary to the vector index at the end of each turn so semantic retrieval stays current across all active sessions.

Questions # 4:

A context engineer is developing an agent to support legal teams reviewing multi-part pharmaceutical trial protocols. Each protocol document includes a narrative background section, nested dosage tables with footnote qualifiers, cross-referenced section identifiers, and figure captions describing study design diagrams. The agent must answer precise questions such as which protocol section governs a specific dosage threshold and what footnote conditions apply to that threshold.

Available data sources include:

A PDF binary store in Unity Catalog Volumes.

A Delta table of plain-text chunks extracted from the protocols, each tagged with page number and document identifier, indexed in a Databricks AI Search index.

A Delta table of protocol structure metadata at the page level, containing table summaries, figure captions, and section hierarchy, accessible through Unity Catalog functions.

Which context elements should the context engineer include to answer structural and footnote-level questions accurately?

Options:

A.

The structure metadata Delta table loaded entirely into the prompt as a hierarchy, combined with the Databricks AI Search index, so the model can resolve table and footnote references from the full metadata.

B.

The PDF binary store in Unity Catalog Volumes and the structure metadata Delta table, using document identifiers to locate source files and extract table content through a preprocessing step at query time.

C.

The Databricks AI Search index over plain-text chunks alone, relying on semantic similarity to surface table and footnote content without consulting the structure metadata Delta table.

D.

The Databricks AI Search index over plain-text chunks to retrieve relevant passages, then a scoped lookup into the structure metadata Delta table for table summaries and figure context on the matched pages.

Questions # 5:

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 # 6:

A context engineer is creating a Databricks agent to triage incoming customer support tickets for a B2B software platform. Each ticket averages 200 tokens.

For each ticket, the agent must:

(1) assign a severity rating of P0/P1/P2/P3 based on whether the issue is fully blocking, degrades core functionality, affects a non-critical feature, or is informational—a judgment that requires reading the ticket body rather than matching keywords;

(2) route the ticket to one of eight engineering teams based on the technical area implied by the ticket;

(3) generate a brief, context-aware acknowledgment reply.

The pipeline must process up to 500 tickets per minute with an end-to-end latency budget of under 2 seconds per ticket. The token budget per invocation is 2,048 tokens, and the operations team has flagged that inference costs must remain minimal at this throughput.

Which reasoning mode should the context engineer configure for the agent?

Options:

A.

Standard mode with extended thinking disabled, because skipping all reasoning overhead minimizes both per-invocation latency and inference cost at 500 tickets per minute.

B.

Extended thinking with max_tokens capped at 1,024, because limiting the response length reduces cost while preserving full reasoning depth.

C.

Extended thinking with a default thinking budget, because severity classification across four tiers and routing across eight teams benefits from deep chain-of-thought reasoning to maximize accuracy.

D.

Reduced thinking, because the task requires modest structured reasoning across four severity tiers, a small thinking budget fits within the 2,048-token invocation, and latency and cost stay manageable at 500 tickets per minute.

Questions # 7:

A context engineer is developing a Databricks agent for a retail inventory management system. The system prompt and tool descriptions consume 1,800 tokens of a 4,096-token context window, and the engineer reserves 1,000 tokens for the user turn and model response. The remaining tokens are used for few-shot examples, each costing approximately 250 tokens, so the engineer includes exactly five examples.

The agent uses three tools: inventory_lookup, reorder_check, and supplier_lead_time.

Six candidate examples are available:

Example 1: A warehouse manager asks whether a depleted SKU needs reordering; the agent calls inventory_lookup, confirms depletion, calls reorder_check, and returns a binary reorder decision.

Example 2: A procurement officer asks when a low-stock item can be replenished; the agent calls reorder_check, calls supplier_lead_time, and returns a replenishment recommendation.

Example 3: A store associate asks for the current stock count of a single product; the agent calls inventory_lookup and returns a scalar quantity.

Example 4: A store associate asks for the current stock count of a single product; the agent calls inventory_lookup and returns a structured status object containing the quantity and a restocking flag.

Example 5: A store associate asks whether a forecasted shortfall requires immediate action; the agent calls inventory_lookup, compares against minimums, calls reorder_check, and returns a binary reorder decision.

Example 6: A logistics coordinator asks how long a specific supplier takes to fulfill an order; the agent calls supplier_lead_time and returns a scalar lead-time value.

Which example should the engineer omit to preserve the token budget while maximizing behavioral coverage?

Options:

A.

Example 1, because the same tools are exercised across Examples 2 and 5, making its specific decision path redundant.

B.

Example 6, because supplier_lead_time is already invoked in Example 2, and a standalone lead-time lookup does not add new tools to the demonstrated call space.

C.

Example 3, because another example in the set covers the same user role and tool path, but the output of the other example is richer.

D.

Example 5, because its forecasting logic duplicates the threshold-check pattern already established in Example 1, and its user role (store associate) appears elsewhere in the set.

Questions # 8:

A context engineer is examining MLflow experiment tracking results comparing two system prompt configurations for a Databricks agent designed to assist with contract review. Configuration P uses a role declaration, a full task instruction, and a dedicated edge-case handling section that explains in prose how the agent should respond to ambiguous or overlapping clause types, averaging 205 tokens per call and 81% clause-classification accuracy. Configuration Q retains the role declaration, removes the prose edge-case handling section, shortens the task instruction to a concise directive, and adds three few-shot examples, each showing how the agent should classify a distinct edge-case clause type, averaging 340 tokens per call and 93% clause-classification accuracy. The token budget increases by 135 tokens per call between Configuration P and Configuration Q. Latency rises from 290 ms to 380 ms.

Which conclusion is supported by these experiment tracking results?

Options:

A.

The token increase is justified by the 12-percentage-point accuracy gain, and the shortened task instruction is the specific prompt element driving the performance improvement.

B.

The token increase is justified by the 12-percentage-point accuracy gain, and the few-shot edge-case examples are the specific prompt element driving the performance improvement.

C.

The token increase is not justified because removing the prose edge-case handling section and replacing it with examples introduces ambiguity that accuracy gain does not sufficiently offset.

D.

The token increase is justified by the accuracy gain, but the improvement is attributable to the larger token budget because the removed edge-case handling section and added few-shot examples represent an equivalent token exchange.

Questions # 9:

A context engineer is tuning a compaction prompt for a Databricks agent that summarizes customer support ticket histories before sending them to a downstream LLM. The trace being compacted spans 40 turns, and the compacted output must fit within the downstream LLM’s context window. During initial evaluation against a benchmark of escalated support cases, the engineer observes that the compaction output consistently omits several prior resolutions and key escalation events, even though it fits well within the downstream LLM’s context window.

What tuning step should the engineer take next?

Options:

A.

Add a token-count cap to the compaction prompt to shorten the summary and lower downstream inference cost and latency, then check afterward whether the key events were retained.

B.

Add a recency rule that keeps the most recent turns in full and compresses the earlier turns, since the latest exchanges usually carry the most relevant context.

C.

Broaden the compaction prompt’s retention rules to capture all events, resolutions, and escalation signals, accepting a longer summary for now and tightening verbosity in a later iteration.

D.

Add retention rules and pruning rules in the same iteration so recall and precision are tuned together rather than over separate passes.

Questions # 10:

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.

Viewing page 1 out of 2 pages
Viewing questions 1-10 out of questions