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.
96 results across 1 active filter
Page 3 of 4
Verifies the exact request bytes, rejects stale signatures, deduplicates event ids, and queues processing durably.
Uses WebApplicationFactory with test-only authentication and isolated dependencies to exercise the real ASP.NET Core pipeline.
Uses `AsSplitQuery` deliberately for a tracked aggregate with multiple collections and explains its consistency boundary.
Maps a stable ProblemDetails validation contract to fields and a fallback form-level error.
Relies on a database unique constraint and translates only the expected provider error into a domain conflict.
Implements interval merging for scheduling-style time ranges with sorted output.
Implements descending keyset pagination with a compound cursor and stable ordering.
Parses a simple filter expression into a validated dictionary without accepting arbitrary keys.
Guards a mutation immediately, exposes pending state, and restores the command after failure.
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Builds a read-only EF Core projection with aggregates, stable ordering, and bounded results instead of loading an entity graph.
Carries the ASP.NET Core request token into a bounded EF Core query while keeping cancellation separate from business rollback guarantees.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
Converts local-day boundaries to UTC once, preserving correct daylight-saving behavior and index use on stored UTC timestamps.
Implements safe redaction of known sensitive keys in a dictionary before logging.
Uses profiler evidence to isolate expensive derived data and row rendering, then applies memoization without hiding correctness bugs.
Replaces a parent query plus one status query per row with one server-side projection.
Ranks duplicate import rows, previews the deletion set, and removes older copies with deterministic retention.
Uses server-resolved capabilities for presentation while keeping the mutation endpoint authoritative.
Uses an explicit state model for initial loading, success, empty, recoverable error, and refetching.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Uses a conditional update and transaction to prevent overselling while recording the reservation consistently.
Implements a bounded async retry helper that respects cancellation and does not retry every exception blindly.
Wraps a complete explicit transaction in the provider execution strategy and creates fresh context state for each retry attempt.