Black Friday Countdown: 75% Off Exam Bundles! Use coupon code below before time runs out! - Ends in 0d 00h 00m 00s - Coupon code: 75vsure

Context-Engineer-Associate Exam Dumps - Databricks Certified Context Engineer Associate

Searching for workable clues to ace the Databricks Context-Engineer-Associate Exam? You’re on the right place! ExamCert has realistic, trusted and authentic exam prep tools to help you achieve your desired credential. ExamCert’s Context-Engineer-Associate PDF Study Guide, Testing Engine and Exam Dumps follow a reliable exam preparation strategy, providing you the most relevant and updated study material that is crafted in an easy to learn format of questions and answers. ExamCert’s study tools aim at simplifying all complex and confusing concepts of the exam and introduce you to the real exam scenario and practice it with the help of its testing engine and real exam dumps

Go to page:
Question # 9

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?

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.

Full Access
Question # 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?

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.

Full Access
Question # 11

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?

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.

Full Access
Question # 12

A context engineer manages a Genie space for a finance team. Users repeatedly ask the same shape of QUESTION NO: with different fiscal periods: “What is the total open pipeline by region for FY26 Q1?”, “...for FY26 Q2?” “...for the last quarter?”. The SQL pattern Genie generates is identical across these questions (same JOIN, GROUP BY, and aggregation, with only the fiscal-period filter changing), and the team requires that responses to these recurring questions be labeled Trusted in the chat UI. The engineer must register an asset that reuses the same vetted SQL pattern with the user-supplied fiscal period.

Which curation choice should the engineer make?

A.

A parameterized example SQL query with a typed (Date or String) fiscal-period parameter, so Genie can reuse the SQL pattern with the user-supplied value each time the QUESTION NO: is asked.

B.

A Unity Catalog SQL function that defines open_pipeline as a reusable measure, with Genie composing the surrounding per-period and per-region SQL around the function call each turn.

C.

A general instructions text block that describes the desired SELECT, JOIN, WHERE, and GROUP BY structure so Genie can regenerate the SQL on every turn from that description.

D.

Multiple static example SQL queries (one for each commonly asked fiscal period: FY26 Q1, FY26 Q2, last quarter), so Genie matches each user QUESTION NO: to its corresponding vetted example.

Full Access
Question # 13

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?

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.

Full Access
Question # 14

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?

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.

Full Access
Question # 15

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?

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.

Full Access
Go to page: