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

A context engineer is assessing a Databricks agent that coordinates a multi-week pharmaceutical supply chain compliance workflow across dozens of distribution centers. The agent uses a flat task decomposition strategy, dividing the entire workflow into a single-level list of atomic tasks that are dispatched and tracked independently. The workflow contains clusters of tightly coupled sub-tasks, such as per-facility inspection records that must all complete before a regional compliance certificate can be issued, and the agent repeatedly fails to coordinate these cluster-level completions correctly. Logs show that the agent loses track of intermediate group states, issues compliance certificates prematurely on incomplete facility data, and cannot recover gracefully when individual facility inspection tasks fail.

Which two changes should the context engineer make to resolve the observed failure?

Choose two

Options:

A.

Switch to a parallel decomposition strategy that executes all facility inspection and certificate tasks simultaneously, relying on eventual consistency to merge partial results into the final compliance record.

B.

Add a retry loop at the top-level agent that restarts the entire flat task list from the beginning whenever any single facility inspection task fails, ensuring no partial state persists across runs.

C.

Replace the flat task decomposition with a hierarchical decomposition strategy that groups related facility inspection sub-tasks under a parent node, enabling group-level completion tracking before dependent tasks proceed.

D.

Introduce explicit dependency gates at each cluster boundary so the compliance certificate task is dispatched only after all facility inspection tasks in the group have reached a confirmed completed state.

E.

Replace the workflow with a fixed sequential chaining strategy that executes every facility inspection one at a time before issuing any certificate, eliminating all concurrency from the pipeline.

Buy Now
Question # 5

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

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

A data analyst is creating a Genie space for a hospital operations team that needs to analyze emergency department wait times, patient discharge rates, and nurse-to-patient ratios. The engineer has added the relevant tables, written general instructions describing the hospital operations domain, and configured sample questions. Stakeholders require any metric involving nurse-to-patient ratios to use the official staffing calculation defined by the compliance team, but Genie should still answer free-form questions about discharge rates and wait times using ad hoc SQL when no trusted asset covers the question.

Which approach should the engineer use to meet both requirements?

Options:

A.

Add the compliance-approved nurse-to-patient ratio calculation to the general instructions as a text description so Genie applies the correct formula when generating ad hoc SQL for staffing questions.

B.

Register example SQL queries as trusted assets for nurse-to-patient ratios, discharge rates, and wait time metrics so that every operational response earns the “Trusted” label and stakeholders can rely on all outputs.

C.

Add the nurse-to-patient ratio query as a sample QUESTION NO: paired with the expected answer so analysts see the correct format and Genie uses the sample as a template when generating ratio queries.

D.

Register an example SQL query containing the compliance-approved nurse-to-patient ratio calculation as a trusted asset, and leave discharge rate and wait time queries unregistered so Genie generates ad hoc SQL for those questions.

Buy Now
Question # 8

A context engineer is building a memory-augmented agent that stores user session memories in Lakebase as an OLTP Postgres table. Each memory record contains columns such as user_id, session_timestamp, preference_category, and confirmed_preference_value. At runtime, the agent must retrieve all confirmed preferences for a specific user that were recorded within the last 30 days. A Databricks AI Search index is created over conversation summary embeddings as part of a delta table synced from the Lakebase, providing an additional data source.

Which retrieval mechanism should the context engineer configure for this type of query?

Options:

A.

A hybrid retrieval combining Databricks AI Search similarity scoring and a structured post-filter, because combining both mechanisms improves recall when querying a bounded time window in Lakebase.

B.

Structured query retrieval against the Lakebase OLTP Postgres table using exact filters on user_id and session_timestamp, over a bounded time range with no need for similarity ranking.

C.

Databricks AI Search against the memory embeddings index with a date range metadata filter, because Databricks AI Search with pre-filtering is the recommended approach for scoping time-bounded memory retrieval in agent frameworks.

D.

Structured query retrieval against the Lakebase OLTP Postgres table using exact filters on user_id, session_id, and preference_category, because scoping the lookup to all three attributes produces the most precise memory retrieval for a single user.

Buy Now
Question # 9

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.

Buy Now
Question # 10

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

A context engineer is developing a Databricks legal research agent for an international financial services organization. The agent uses a DELTA_SYNC Databricks AI Search index containing regulatory compliance documents for the United States, United Kingdom, and European Union.

Each document chunk includes the following metadata:

jurisdiction: The regulatory jurisdiction to which the document applies.

document_status: Whether the document is active, superseded, or archived.

effective_date: The date on which the regulatory provision became effective.

document_id: The unique identifier of the source document.

The agent uses semantic similarity search with num_results=10 to retrieve regulatory evidence.

During MLflow evaluation, the engineer discovers that questions about current UK financial reporting obligations frequently retrieve superseded UK regulations and highly relevant US regulatory documents. The resulting answers are technically plausible but cite requirements that do not apply to the user ' s jurisdiction or requested reporting period.

The embedding model produces accurate semantic similarity scores, and increasing num_results does not improve regulatory correctness.

The engineer must preserve semantic retrieval while ensuring that only regulations applicable to the requested jurisdiction and reporting date are considered.

Which retrieval configuration should the context engineer implement?

Options:

A.

Increase num_results from 10 to 50 and apply a reranker so that the most semantically relevant regulatory documents appear first, regardless of their original jurisdiction.

B.

Apply metadata filters for the requested jurisdiction, active regulatory status, and applicable effective-date conditions as part of the AI Search query, then rank the eligible documents by semantic relevance.

C.

Replace semantic retrieval with full-text search so that exact jurisdiction names and regulatory terminology determine which documents are returned.

D.

Retrieve all semantically relevant documents first and instruct the LLM through the system prompt to ignore regulations belonging to other jurisdictions or historical reporting periods.

Buy Now
Question # 12

A context engineer is evaluating a Databricks agent built for a healthcare scheduling platform. The agent’s system prompt is 5,100 tokens and includes detailed instructions for three rarely invoked capabilities, each triggered in fewer than 2% of sessions:

Insurance eligibility verification, which requires calls to a third-party payer API with variable response times

Appointment rescheduling fee calculations, with complex branching logic across dozens of plan types and provider tiers

Medical record release consent workflows, with multi-step conditional logic and regulatory references

The agent’s primary function is answering patient appointment availability queries, which account for 95% of traffic. The team must reduce per-session context cost without degrading task success rate on the dominant use case, and the solution must stay within the existing Databricks agent framework without introducing additional hosted components to manage.

Which loading strategy should the context engineer use for the three rarely invoked capabilities?

Options:

A.

Compress the three capability instruction blocks using summarization and retain them in the system prompt, reducing token count while keeping all instructions globally available for every session.

B.

Enable server-side prompt caching for the full system prompt so the token cost of the three capability blocks is amortized after the initial session, reducing effective per-session billing over time.

C.

Package each rarely-invoked capability as an Agent Skill so its instruction block is loaded dynamically only when a user query triggers the matching intent, removing those tokens from the baseline prompt.

D.

Move the three capability instruction blocks into a retrieval-augmented index and inject the top-ranked block into the user message turn at query time, keeping the system prompt shorter across sessions.

Buy Now
Question # 13

A context engineer is developing a Databricks agent for a financial research platform that answers analyst queries using a vector search index over earnings reports. The agent uses a 180-token system prompt, a 250-token conversation history window, and a RAG pipeline that retrieves 8 document chunks at runtime. Each chunk contains 550 tokens, contributing 4,400 tokens of retrieved context. The model’s context window is 8,192 tokens, leaving just 3,362 tokens for the analyst query and model response. Profiling shows that the retrieved chunks consistently contain repetitive regulatory boilerplate and duplicated table headers that are rarely cited in the model’s final answers.

Which two changes should the context engineer make to reduce the token footprint of retrieved context without discarding relevant financial content?

Choose two

Options:

A.

Reduce retrieved chunks from 8 to 3 and apply a reranker to select the highest-relevance chunks, preserving pertinent financial content while cutting injected tokens by over 60%.

B.

Switch the retrieval strategy from cosine similarity to MMR to increase diversity across retrieved chunks, reducing redundancy between chunks without modifying chunk size or removing boilerplate.

C.

Reduce each chunk from 550 tokens to 150-200 tokens by splitting at semantic boundaries and stripping repeated regulatory boilerplate and duplicate headers before indexing.

D.

Re-index the earnings reports using a finer-grained embedding model to improve retrieval precision, surfacing more relevant passages without altering chunk boundaries or stripping metadata.

E.

Expand the conversation history window from 250 tokens to 900 tokens to improve multi-turn coherence across analyst sessions and offset token pressure from the retrieved chunks.

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