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.
157 results across 1 active filter
Page 5 of 7
Carries the version observed by the client into a conditional update and returns an explicit conflict instead of silently overwriting newer data.
Implements a database-backed idempotency boundary that replays one response and rejects key reuse with a different request.
Stores an idempotency key, request hash, and response in the same transaction as the created resource.
Implements descending keyset pagination in LINQ using a compound timestamp-and-id cursor.
Explains debounce, cancellation, stale-response protection, loading indicators, and backend query safety for search UI.
Explains stable EF Core pagination using cursor predicates, deterministic ordering, and index-aligned queries.
Builds descending keyset pagination with a unique tie-breaker, opaque cursor, limit-plus-one query, and stable next page.
Implements descending cursor pagination with a unique tie-breaker, bounded projection query, and next-cursor detection.
Processes a large import in chunks with fresh DbContexts, idempotent keys, cancellation, and bounded tracker growth.
Verifies the exact request bytes, rejects stale signatures, deduplicates event ids, and queues processing durably.
Explains how to inspect EF Core generated SQL and connect LINQ shape to database execution behavior.
Investigates a growing-data EF Core slowdown through one correlated request, generated SQL, representative parameters, execution plan, waits, query shape, measured repair, and guarded rollout.
Explains when LINQ is enough, when raw SQL is clearer, and how to keep raw SQL safe and maintainable.
Uses `AsSplitQuery` deliberately for a tracked aggregate with multiple collections and explains its consistency boundary.
Relies on a database unique constraint and translates only the expected provider error into a domain conflict.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Implements descending keyset pagination with a compound cursor and stable ordering.
Explains expand-and-contract migrations, backwards-compatible schema changes, backfills, rollout order, and rollback thinking.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Explains EF Core projections for API read models that need related names, counts, and summaries without loading full graphs.
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.