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.
1345 results
Page 29 of 57
Places each risk at the cheapest reliable test boundary and keeps a small set of browser journeys for integration confidence.
Creates a task-oriented model boundary that normalizes application outcomes without erasing useful provider capabilities.
Allocates per-stage deadlines and spend, controls tokens and fan-out, and optimizes for successful outcomes rather than cheap calls.
Carries source permissions into ingestion and query-time filtering while failing closed across retrieval, caching, and citations.
Evaluates verified outcomes, trajectory quality, safety, efficiency, recovery, and important slices in realistic environments.
Separates storage from processing location, verifies provider and feature-specific retention, and minimizes sensitive inputs.
Judges claims against allowed evidence, separates correctness from support, and tests whether the system answers or abstains appropriately.
Builds a query-and-relevance dataset and separates retrieval recall, ranking quality, context quality, and generated-answer quality.
Measures schema validity, tool selection, argument correctness, policy, execution outcome, repair, and final user result.
Treats the model-facing schema and downstream consumer contract as a versioned API with compatibility and rollout concerns.
Builds titles, descriptions, canonicals, Open Graph data, and not-found behavior from the same canonical page record.
Connects answer claims to retrieved evidence while preventing decorative citations and preserving source-level traceability.
Explains safe migration strategy for Azure-hosted .NET APIs, including expand-contract changes, locking risk, rollback, and deployment order.
Keeps cached reads acceptably fresh and prevents hot-key reloads from overwhelming the database across application instances.
Controls admission, concurrency, queues, tenant fairness, token budgets, and overload behavior before provider throttling cascades.
Combines safe bindings, AOT, dependency discipline, CSP, Trusted Types, and reporting without treating one control as a complete defense.
Maps DRF and application failures into stable client errors while preserving internal diagnostic evidence.
Maps validation, HTTP, domain, and unexpected failures into a stable client contract while preserving diagnostics.
Places an idempotency key at the Spring boundary while persisting request identity and terminal outcome atomically with business work.
Makes nested create and update semantics, authorization, identity, and transaction ownership explicit.
Uses FastAPI Security dependencies to combine declared scopes with current application authorization.
Combines server and client instrumentation, OpenTelemetry, post-response work, correlation, and privacy-aware signals.
Owns a third-party widget through a DOM ref, effect lifecycle, minimal updates, and complete teardown.
Gives a practical incident flow for memory growth using metrics, traffic correlation, heap evidence, and safe mitigation.