Loading
Pick a focused question that fits your time, stack, and interview goal.
123 results across 1 active filter
Page 5 of 6
Wraps a complete explicit transaction in the provider execution strategy and creates fresh context state for each retry attempt.
Writes a left-join aggregate that keeps active customers with no paid orders and applies date filters without changing join semantics.
Uses ROW_NUMBER with a deterministic tie-breaker to return the complete latest status row per order.
Aggregates product sales and ranks independently inside each category with a deterministic top-N rule.
Reviews and stages destructive EF Core schema changes around live data, locks, mixed application versions, recovery, and rollback.
Persists domain state and its outbox message in one SaveChanges transaction without publishing inside the request transaction.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.
Explains EF Core shadow properties for audit or infrastructure columns with practical .NET data-access examples and production trade-offs.
Shapes an API list from its contract and cardinality, projecting only required values while preserving authorization, stable pagination, bounded nesting, index support, and measurable query cost.
Adds a stable query tag and inspects generated SQL without embedding user data or enabling unsafe global logging.
Proves repeated requests with one idempotency key create one resource and return a consistent result.
Verifies migration SQL, data preservation, production-provider behavior, mixed application versions, backfills, and expand-contract releases.
Attaches a key-only stub and marks one property modified for a narrow update while naming the rules this pattern bypasses.
Explains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.
Uses EF Core context pooling only when reusable context state, tenant isolation, and underlying connection state are controlled and tested.
Explains when EF Core compiled queries help, what they do not fix, and how to measure their value.
Explains how query tags, request correlation, and telemetry help connect slow SQL back to code paths.
Explains when set-based EF Core updates are better than loading entities and where lifecycle behavior can differ.
Explains referential integrity, cascade delete trade-offs, restrict behavior, soft deletes, and operational safety.
Explains aggregate queries, grouping keys, filters before and after aggregation, and business-count correctness.
Prevents lost updates with an original rowversion predicate, maps zero affected rows to an explicit conflict, and defines user, retry, aggregate, and API precondition behavior.
Explains read models for complex API screens with practical .NET data-access examples and production trade-offs.
Makes business uniqueness race-safe with the exact database key, while handling normalization, tenant scope, nulls, soft deletion, rollout cleanup, and stable API conflicts.
Uses ROW_NUMBER with deterministic partition ordering to return one complete latest row per group, then evaluates index support, tie semantics, scale, and read-model alternatives.