Black Friday Early Access - 75% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: save75geek

Context-Engineer-Associate Databricks Certified Context Engineer Associate Questions and Answers

Questions 4

A context engineer manages a personalized travel planning agent deployed on Databricks. The agent uses Databricks Agent Memory backed by Lakebase to retain durable user preferences across independent conversations.

Memory entries are organized using actor_id, session_id, and path.

During an earlier conversation, User42 stated that they preferred economy-class flights. The application persisted this preference in the memory store using:

actor_id: User42

path: /preferences/flight-class.md

content: Prefers economy-class flights.

session_id: Unset

Three months later, User42 explicitly changes their preference to business-class flights for future travel. The agent must retain the updated preference across all subsequent sessions without creating competing entries that could cause contradictory recommendations.

The application must also ensure that User42 ' s preference does not affect memories belonging to other users.

Which memory-management operation should the context engineer configure?

Options:

A.

Append the new business-class preference as another memory entry under a unique path, retaining both preferences so semantic retrieval can select whichever entry is most relevant to future travel requests.

B.

Use memory_store.put() with the existing actor_id and memory path, leaving session_id unset, to replace the previously stored preference with the newly confirmed business-class preference.

C.

Create a new memory entry using the latest session identifier and the existing preference path, allowing the agent to retrieve the updated value through session-scoped memory search.

D.

Retain the original economy-class preference in the durable memory store and place the new business-class preference exclusively in the current conversation ' s short-term session context.

Buy Now
Questions 5

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.

Buy Now
Questions 6

A context engineer is building a Databricks research agent that produces analyst reports where every claim must cite a verifiable source: a reviewer must be able to trace each citation back to its exact original source text. At each step, the agent calls a retrieval tool that returns several short source snippets, writes a reasoning trace explaining how those snippets support its conclusions, and appends both the snippets and the reasoning to a running context reused by later steps. As the run grows, the accumulated context pushes per-step token cost above the team’s budget, so the context must be compacted to reduce token spend.

Which compaction strategy meets both the citation requirement and the need to reduce tokens?

Options:

A.

Snippet summarization: replace each retrieved snippet with a short paraphrase of what it says to save tokens, while keeping every reasoning trace in full.

B.

Conservative compaction: keep the retrieved snippets verbatim but compress the reasoning traces and drop redundant text, accepting a smaller token saving in order to preserve the source text citations depend on.

C.

Recency eviction: drop the earliest steps’ snippets and reasoning as new steps arrive, keeping only the most recent context that fits the token budget.

D.

Aggressive compaction: replace each step’s snippets and reasoning with a brief model-written summary before passing context to later steps, since summaries reclaim the most tokens.

Buy Now
Questions 7

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.

Buy Now
Questions 8

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.

Buy Now
Questions 9

A context engineer is building a multi-agent Databricks workflow where an orchestrating agent coordinates five sub-agents, each performing document analysis, entity extraction, and summarization tasks. The orchestrator receives the complete raw output from each sub-agent, including intermediate reasoning chains, extracted entity lists, and status messages, and appends all of it to its running context window before issuing follow-up instructions. After scaling to production document volumes, the orchestrator’s context window consistently saturates before all sub-agent results are processed, causing truncation errors and a loss of task coherence.

Which two changes to sub-agent output design would reduce the orchestrator’s context load while preserving the information it needs to continue coordinating tasks?

Choose two

Options:

A.

Restructure sub-agent outputs to return only a concise structured summary object containing task status, key extracted entities, and a confidence score, omitting intermediate reasoning chains.

B.

Reduce the number of sub-agents so that fewer tokens are sent to the orchestrator before final synthesis.

C.

Increase the orchestrator’s model context window by switching to a larger foundation model so that all sub-agent outputs fit without truncation.

D.

Merge all five sub-agents into a single agent so the orchestrator receives one combined output instead of five separate outputs per workflow run.

E.

Configure sub-agents to store full outputs in a Lakebase table and return only a record identifier to the orchestrator.

Buy Now
Questions 10

A context engineer is building a Databricks agent to orchestrate a multi-step data quality remediation workflow across a large enterprise dataset. The agent iterates through validation rules, flags violations, applies corrections, and logs every remediation action. The workflow can span dozens of steps and may be interrupted by cluster preemption or network timeouts. Business stakeholders require every correction applied to the dataset to be traceable and reversible, and the agent must be able to resume mid-workflow without reapplying corrections already committed to prior records.

Which state management approach meets these requirements?

Options:

A.

Persist each step’s output to a temporary in-memory Python dictionary shared across agent invocations within the same cluster session.

B.

Write remediation actions to a plain text log file on DBFS, reading the file at the start of each step to reconstruct the prior state.

C.

Use an in-context scratchpad to accumulate remediation actions as a running list appended to the agent’s prompt on each step.

D.

Store intermediate state in a Delta table, leveraging transaction history for traceability and enabling the agent to checkpoint and resume from the last committed step.

Buy Now
Questions 11

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.

Buy Now
Questions 12

A context engineer is building an AI application that tracks every prompt sent to a large language model, the retrieved context chunks passed to it, and the final generated response. The application must capture token usage, latency metrics, and user feedback scores associated with each inference run. The engineer needs a unified system that versions prompt templates alongside model artifacts, links evaluation results to specific runs, and provides a query interface so downstream dashboards can compare performance across experiment iterations, all without building a custom logging backend.

Which Databricks product should the context engineer use to meet these requirements?

Options:

A.

Unity Catalog, to register prompt templates as catalog assets, enforce access policies on inference logs, and track lineage between input datasets and model outputs.

B.

Lakebase, to store inference run records in a transactional database, version prompt templates as rows, and query latency metrics through a relational interface.

C.

MLflow 3, to log full inference traces, version prompt templates as registered model artifacts, and query evaluation results across experiment runs without a custom logging backend.

D.

MCP, to expose the LLM inference endpoint and prompt templates as a standardized tool schema that agent frameworks can discover and invoke at runtime.

Buy Now
Questions 13

A context engineer is configuring a Databricks agent for an automotive service center platform. The agent must serve service center staff who submit a vehicle identification number (VIN) and a reported symptom. The agent is expected to return a summary of the vehicle’s operating profile, identify the applicable SOP procedure code for the symptom, and retrieve the narrative step-by-step service instructions for that procedure. The engineer has access to these data sources:

Unity Catalog Delta table named vehicle_profiles with columns vin, engine_type, and operating_spec.

Unity Catalog Delta table named symptom_sop_map with columns symptom_code and sop_procedure_code.

Unity Catalog Delta table named service_history with columns vin, service_date, and technician_id.

Databricks AI Search index built from scanned OEM service manuals containing narrative SOP instructions and safety warnings.

Which combination of context elements correctly supports the agent’s task?

Options:

A.

A system prompt scoping the agent as an automotive service assistant; explicit tool-use instructions mapping service_history to VIN-based operating profile lookups and symptom_sop_map to symptom-to-procedure-code resolution; and the Databricks AI Search index for retrieving narrative OEM service instructions.

B.

A system prompt scoping the agent as an automotive service assistant; tool-use instructions mapping vehicle_profiles to VIN-based operating profile lookups and symptom_sop_map to symptom-to-procedure-code resolution; and the Databricks AI Search index for retrieving narrative OEM service instructions.

C.

A system prompt scoping the agent as an automotive service assistant; a generic instruction to query available structured Delta tables for any structured lookup based on provided identifiers; and the Databricks AI Search index for retrieving narrative OEM service instructions.

D.

A system prompt scoping the agent as an automotive service assistant; explicit tool-use instructions mapping vehicle_profiles to VIN-based operating profile lookups; and the Databricks AI Search index for both procedure code resolution and narrative OEM service instructions, relying on semantic search to surface structured codes from manual text.

Buy Now
Questions 14

A context engineer is building a personalized shopping assistant agent on Databricks. The agent is deployed for returning users who expect it to remember their stated product preferences and past purchase topics from previous conversations. After several weeks in production, users consistently report that every new session feels like a first interaction, with no recognition of their preferences or history.

What should the engineer configure to properly resolve this limitation?

Options:

A.

Attach a Lakebase-backed durable store to the agent and configure it to persist key user preferences and interaction summaries between sessions.

B.

Configure the AsyncPostgresSaver checkpointer with a fixed thread ID per user so that session context is preserved across separate conversations.

C.

Instantiate an InMemorySaver checkpointer scoped to the user ID, register it with the compiled LangGraph graph, and persist each session’s final checkpoint to a vector index for cross-session retrieval.

D.

Enable Delta Lake change data feed on the agent state table and configure the agent runtime to reload the latest snapshot at session start.

Buy Now
Questions 15

A context engineer is debugging a long-running data pipeline orchestration agent that runs multi-step workflows using registered Databricks tools such as run_job, query_catalog, and validate_schema. After compaction occurs at turn 40, the agent starts re-invoking tools it successfully called earlier in the session and ignores results that downstream steps depend on. Inspection of the compacted context shows that the summarization prompt was instructed to retain only the final state of each pipeline stage. The current compaction prompt reads: “Summarize the current pipeline state in a few sentences and include only what is necessary.”

Which revision to the compaction prompt addresses the coherence failure while keeping token cost low?

Options:

A.

Replace “include only what is necessary” with: “Include the reasoning chain and internal thinking text produced before each tool invocation.”

B.

Replace “include only what is necessary” with: “Include a compact record of each tool called, its key arguments, and its returned result.”

C.

Append: “For each tool invocation, include the full input payload and every response field returned by the tool.”

D.

Append: “Retain the user ' s original task description and all clarifying questions asked during the session.”

Buy Now
Exam Name: Databricks Certified Context Engineer Associate
Last Update: Nov 21, 2026
Questions: 50
Context-Engineer-Associate pdf

Context-Engineer-Associate PDF

$22.5  $89.99
Context-Engineer-Associate Engine

Context-Engineer-Associate Testing Engine

$28.75  $114.99
Context-Engineer-Associate PDF + Engine

Context-Engineer-Associate PDF + Testing Engine

$35  $139.99