Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
77 results across 1 active filter
Page 1 of 4
Uses traces to separate unclear goals, bad tool interfaces, missing state, contradictory results, poor termination, and retry amplification.
Builds a reproducible evaluation harness that records immutable cases, versioned outputs, deterministic checks, calibrated graders, slices, and release decisions.
Builds a schema-constrained extraction boundary that distinguishes refusal, malformed output, semantic invalidity, and safe bounded repair.
Builds a hybrid retrieval pipeline that enforces tenant scope before ranking, assembles a bounded context, and verifies returned citations.
Chooses between managed ingestion and retrieval convenience and custom control over indexing, ranking, security, evaluation, and operations.
Chooses delegation patterns based on who owns the user interaction, context, final answer, permissions, and failure handling.
Chooses between a direct provider relationship and a cloud-managed integration using concrete security, operations, capability, and commercial constraints.
Separates the current model input from authoritative workflow state and selectively retained information across runs.
Balances burst flexibility, predictable capacity, latency variance, commitment cost, and realistic traffic shape.
Separates application instruction attacks from attempts to bypass a model's safety behavior and explains their overlapping defenses.
Handles a poisoned retrieval corpus by freezing ingestion, tracing provenance, switching immutable index versions, rebuilding clean data, and proving recovery.
Combines restrained autonomy, curated tools, durable state, approval, memory, recovery, MCP trust, evaluation, and operational controls.
Combines governed ingestion, authorized hybrid retrieval, reranking, grounded generation, citations, evaluation, observability, and fallback.
Combines threat modeling, injection containment, data minimization, tenant isolation, tools, audit, incident response, and governance.
Uses workflow traces to distinguish planning failure, stale observations, retry ambiguity, and missing terminal conditions in a looping agent.
Uses versioned traces and evaluation slices to locate whether a RAG regression came from ingestion, retrieval, context assembly, or generation.
Explains instruction authority while keeping provider-specific message roles separate from the application’s durable trust boundary.
Uses plans as bounded, revisable execution aids while preserving evidence, policy, and application-owned state transitions.
Treats prompts as observable behavior, removes secrets and authorization policy from them, and limits the consequence of disclosure.
Returns correlated, minimal, typed, and safely bounded tool results without confusing them with trusted instructions.
Records attributable versions, decisions, evidence references, policy results, and side-effect receipts while minimizing content-rich logs.
Defines success, failure, step, time, token, cost, retry, and repetition limits with useful escalation behavior.
Chooses among shared, provisioned, regional, data-zone, global, batch, or managed-compute patterns from workload and governance constraints.
Chooses among routing, sequential, parallel, evaluator-optimizer, and bounded agent loops from the task's dependency structure.