Grab 75% Off This Black Friday: Use coupon code below to save on all exam bundles! - Ends in 0d 00h 00m 00s - Coupon code: 75only

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

Questions 4

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 5

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 6

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.

Buy Now
Questions 7

A context engineer is building a regulatory compliance agent on Databricks that connects to an external compliance management platform through an MCP Service registered in Unity Catalog.

The MCP server exposes the following tools:

search_compliance_records: Retrieves existing compliance records without modifying them.

get_submission_status: Checks the status of previously submitted reports.

submit_regulatory_report: Sends a finalized regulatory report to an external authority.

delete_compliance_record: Permanently deletes an existing compliance record.

The agent serves compliance officers who are authorized to retrieve records and submit reports. However, organizational policy requires explicit human approval before every regulatory report submission.

The agent must continue executing read-only tools without interruption. It must also prevent unauthorized destructive operations and maintain an auditable record of tool invocations.

The engineering team has confirmed that the MCP tools function correctly. The remaining requirement is to enforce the approval and authorization rules at the platform governance layer rather than relying exclusively on instructions inside the agent ' s system prompt.

Which approach should the context engineer implement?

Options:

A.

Add instructions to the system prompt requiring the agent to ask the user for confirmation before invoking submit_regulatory_report, and instruct the agent never to invoke delete_compliance_record.

B.

Increase the model ' s reasoning effort so the agent evaluates the consequences of each MCP invocation before deciding whether user approval is necessary.

C.

Configure the MCP Service with appropriate Unity Catalog permissions and tool restrictions, and attach an input-phase service policy that requires approval for submit_regulatory_report while allowing authorized read-only calls.

D.

Remove all tools capable of modifying external systems from the MCP server and require compliance officers to submit regulatory reports through an independent manual process.

Buy Now
Questions 8

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 9

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.

Buy Now
Questions 10

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 11

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 12

A context engineer is investigating an AI agent deployed on Databricks that handles customer support operations. The agent has two MCP tools registered: one described as “Searches customer support tickets and open case records for a given customer”, and another described as “Looks up customer issue history and unresolved case details by customer ID”.

When users ask whether a customer has any open issues, the agent randomly chooses between the two tools across repeated identical requests. When users ask about a customer’s past resolved issues, the agent similarly misfires between the two tools. The engineer has reviewed the tool call logs and confirmed that the agent cannot reliably distinguish which tool to invoke.

Which overlap between the two tool descriptions is causing the agent to select tools ambiguously?

Options:

A.

Both descriptions omit the data source or system name, so the agent cannot determine which backend database each tool queries when forming a retrieval plan.

B.

Both descriptions use action verbs (Searches and Looks up) that belong to the same semantic category, causing the agent to treat the tools as interchangeable retrieval operations.

C.

Both descriptions claim the same functional scope: each covers open cases (open case records and unresolved case details) and historical records (support tickets and issue history), leaving no functional differentiator.

D.

Both descriptions reference a customer identifier as the lookup parameter, making the input signature indistinguishable to the agent when resolving tool selection.

Buy Now
Questions 13

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 14

A context engineer is investigating a multi-agent pipeline on Databricks where a coordinating agent breaks down a document analysis task and dispatches subtasks to three specialized sub-agents. After deployment, the sub-agents produce outputs that are internally consistent but contradict one another and do not reflect earlier inferences made at the pipeline level. The sub-agents have access to the same retrieval index, the embedding model is verified as current, and individual sub-agent outputs are accurate when tested in isolation with full context supplied manually.

What is a reasonable root cause of the downstream failures?

Options:

A.

The coordinating agent’s temperature parameter is set too high, introducing non-determinism into the subtask decomposition and producing inconsistent dispatch instructions.

B.

Each sub-agent is dispatched with only its individual task message and lacks access to the coordinator’s earlier reasoning, tool outputs, and decisions.

C.

The retrieval index used by the sub-agents is misconfigured, so they are querying a different corpus than the coordinating agent, leading to contradictory but locally consistent outputs.

D.

The embedding model used for retrieval was not trained on the document domain, causing sub-agents to retrieve irrelevant chunks and produce contradictory summaries.

Buy Now
Questions 15

A context engineer is debugging a Databricks customer support agent that manages complex billing escalations.

The system prompt instructs the agent to:

Strictly apply the company’s official refund policy.

Treat entries from the “Billing-Policies” tool as authoritative.

Treat FAQ snippets and prior chat history as non-binding guidance only.

In one multi-step trace, the engineer observes the following:

Step 1: The agent calls the “Billing-Policies” tool and retrieves the official refund policy, which clearly states that chargebacks filed more than 90 days after purchase are not eligible for refunds.

Step 2: The agent calls a “Customer-FAQ-Search” tool that returns a community-authored FAQ thread. A top-voted but outdated and unofficial answer incorrectly claims that chargebacks are fully refundable regardless of when they are filed, and the agent summarizes this in the running conversation as an established fact.

Step 3: In a later turn, the customer describes a chargeback dispute from 18 months ago. The agent reasons from its own earlier summary, approves a full refund, and makes no reference to the official policy section excluding cases older than 90 days, even though that policy text remains in the context.

Step 4: In subsequent similar cases, the agent repeatedly approves refunds for old chargebacks, citing its prior summary as justification each time.

Which context failure mode describes what is occurring in this trace?

Options:

A.

Context distraction, because the context has grown so long with policy text, FAQs, and chat history that the model loses focus on the specific 90-day rule and drifts toward irrelevant retrieved content.

B.

Context clash, because the agent is simultaneously presented with two contradictory authoritative sources and produces an inconsistent response that partially applies each policy.

C.

Context confusion, because the agent misidentifies which retrieved policy section governs chargeback disputes, applying refund rules intended for a different transaction category to the current case.

D.

Context poisoning, because a mistaken statement about refund eligibility enters the context as ground truth and is repeatedly reused in downstream steps, overriding the correct policy that is also present.

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

PDF + Testing Engine

$42.5  $169.99

Testing Engine

$32.5  $129.99
buy now Context-Engineer-Associate testing engine

PDF (Q&A)

$27.5  $109.99
buy now Context-Engineer-Associate pdf
dumpsmate guaranteed to pass

24/7 Customer Support

DumpsMate's team of experts is always available to respond your queries on exam preparation. Get professional answers on any topic of the certification syllabus. Our experts will thoroughly satisfy you.

Site Secure

mcafee secure

TESTED 22 Nov 2026