Black Friday VIP Hour Limited Time 75% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = simple75

Pass the Databricks Context Engineer Context-Engineer-Associate Questions and answers with Dumpstech

Exam Context-Engineer-Associate Premium Access

View all detail and faqs for the Context-Engineer-Associate exam

Practice at least 50% of the questions to maximize your chances of passing.
Viewing page 2 out of 2 pages
Viewing questions 11-20 out of questions
Questions # 11:

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.

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.

Questions # 13:

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.

Questions # 14:

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.

Questions # 15:

A context engineer is building a retrieval-augmented generation agent on Databricks to answer questions about a large collection of legal contracts. Each contract is a structured PDF averaging 40 pages, with clearly defined sections such as “Definitions,” “Obligations,” and “Termination Clauses.” The embedding model in use has a 512-token context window. User queries are highly targeted, such as “What are the termination conditions in the indemnification clause?”, and require precise, clause-level retrieval rather than broad document summaries.

Which chunking strategy should the context engineer use?

Options:

A.

Use structure-aware chunking that splits documents at section boundaries, then further subdivides sections exceeding 400 tokens to stay within the embedding model’s context window.

B.

Apply paragraph-level chunking across all contracts, splitting each section into individual paragraphs, to maximize retrieval granularity for targeted clause queries.

C.

Split each contract into fixed-size chunks of 512 tokens with 50-token overlaps, ignoring document structure, keeping chunks within the embedding model’s context window.

D.

Embed each contract section as a single chunk without further subdivision, preserving full section context even when sections exceed the embedding model’s context window.

Viewing page 2 out of 2 pages
Viewing questions 11-20 out of questions