Black Friday Mega Drop - Up to 75% Off Best Sellers - Ends in 0d 00h 00m 00s - Coupon code: certbig75

Context-Engineer-Associate Exam Dumps - Databricks Context Engineer Questions and Answers

Question # 14

A context engineer is developing a multi-agent research pipeline on Databricks. A coordinator agent divides an incoming scientific literature query into two parallel subtasks: a citation-retrieval agent and a methodology-analysis agent. Both agents independently receive only the original user query, produce their outputs, and return them to the coordinator, which then invokes a synthesis agent. The synthesis agent produces a final report that contradicts the citation-retrieval findings because it relies solely on the methodology-analysis output and has no visibility into retrieved citations.

Which two context propagation changes would prevent the conflicting outputs in the synthesis agent?

Choose two

Options:

A.

Configure the coordinator agent to merge outputs from the citation-retrieval and methodology-analysis agents into a single context payload before invoking the synthesis agent.

B.

Replace the parallel dispatch pattern with a sequential chain so the methodology-analysis agent runs first, and the citation-retrieval agent runs afterward, without changing what context is forwarded to the synthesis agent.

C.

Configure the coordinator to forward only a high-level methodology summary into the synthesis agent’s context while omitting the underlying citation-retrieval data, to keep the context window small.

D.

Broadcast every agent’s full raw interaction history, including intermediate prompts and tool calls, directly to the synthesis agent, allowing the LLM to self-structure citation results from methodology analysis.

E.

Update the synthesis agent’s input schema to accept a structured context object containing both citation-retrieval results and methodology-analysis results as named fields.

Buy Now
Question # 15

A context engineer is developing a RAG pipeline for a pharmaceutical knowledge base. Document chunks from clinical trial summaries are stored in a Unity Catalog-governed Delta table with precomputed embedding vectors. Pure vector similarity search retrieves topically related chunks effectively but misses chunks that depend on precise drug compound names and dosage identifiers in the search string, because those tokens are underrepresented in the embedding space. The engineer wants to recover those exact-term chunks while preserving the semantic retrieval that already works, without standing up a separate keyword index or adding a downstream merge step.

Which configuration should the engineer use to close this retrieval gap?

Options:

A.

Query the index using a filter with a LIKE operator in conjunction with approximate nearest neighbors (ANN) to return a single ranking while recovering the specific exact-term chunks being ignored in the original search.

B.

Query the index using full-text search, then leverage the Databricks reranker with approximate nearest neighbors (ANN) to return a single hybrid ranking.

C.

Query the index with hybrid search, using approximate nearest neighbors (ANN) and full-text search in one call and returning a single fused ranking.

D.

Query the index using approximate nearest neighbors (ANN), then filter the returned chunks to those containing the exact drug and dosage terms, resulting in a single ranked result set.

Buy Now
Question # 16

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
Question # 17

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.

Buy Now
Question # 18

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
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

$25  $99.99
Context-Engineer-Associate PDF + Engine

Context-Engineer-Associate PDF + Testing Engine

$35  $139.99