Loading
Pick a focused question that fits your time, stack, and interview goal.
123 results across 1 active filter
Page 4 of 6
Explains `IQueryable` versus `IEnumerable` in EF Core with practical .NET data-access examples and production trade-offs.
Compares rollback, reset, schema, database, and tenant isolation without hiding transaction or parallelism limits.
Explains transaction isolation levels with practical .NET data-access examples and production trade-offs.
Explains when LINQ is enough, when raw SQL is clearer, and how to keep raw SQL safe and maintainable.
Explains LINQ translation boundaries with practical .NET data-access examples and production trade-offs.
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.
Explains multi-tenant data filtering with practical .NET data-access examples and production trade-offs.
Explains offset versus cursor pagination with practical .NET data-access examples and production trade-offs.
Designs an EF Core optimistic-concurrency contract around tokens, conflict policy, HTTP semantics, merge behavior, and real relational tests.
Uses a transactional outbox to make a local state change durably publishable while accepting at-least-once delivery and operating the backlog safely.
Chooses between EF Core complex types, owned entities, and regular entities from value semantics, identity, ownership, querying, and storage needs.
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 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.
Converts local-day boundaries to UTC once, preserving correct daylight-saving behavior and index use on stored UTC timestamps.
Fits database command timeouts into endpoint latency budgets while diagnosing slow SQL, blocking, pool pressure, and uncertain write outcomes.
Uses an actual execution plan, row-flow evidence, runtime measurements, and representative parameters to diagnose a slow query without guessing.
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 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.