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 4 of 7
Uses EXISTS instead of a row-multiplying join when the related table is only a filter.
Groups normalized email values to identify duplicates before adding or repairing a uniqueness rule.
Uses the gaps-and-islands pattern to find consecutive login-day streaks after deduplicating same-day activity.
Solves a many-to-many all-match filter with grouping and a deliberate empty-selection rule.
Uses NOT EXISTS to express an anti-join without null traps or duplicate parent rows.
Repairs a Django serialization path with select_related and prefetch_related, then locks the query shape with a regression test.
Uses a bounded entity graph for a to-one association and proves the repair with Hibernate query statistics.
Uses a recursive CTE to return hierarchy depth and a readable root-to-node path.
Uses SQLAlchemy version counters and an HTTP precondition to reject stale writes without silently overwriting newer state.
Uses the client's original rowversion to detect a lost update and return a deliberate conflict response.
Separates caller cancellation from a dependency timeout and maps expected downstream outcomes safely.
Makes EF Core transient retries safe across transactions, uncertain commits, generated keys, and external side effects.
Explains optimistic concurrency with EF Core rowversion tokens, API conflict responses, and safe retry boundaries.
Explains stale edit detection, row versioning, conflict UI, refresh behavior, and safe update contracts.
Explains why application-level duplicate checks are not enough and how EF Core APIs map database constraints to friendly errors.
Connects EF Core change tracking to object retention, query shape, projections, and read-only API performance.
Explains transient database errors, retry strategy, EF Core execution strategy, idempotency, timeouts, and avoiding retry storms.
Covers using managed identity and Microsoft Entra authentication for Azure SQL access from a .NET API.
Uses Hikari metrics, thread evidence, database activity, transaction scope, and query behavior to separate leaks from slow or excessive work.
Explains safe migration strategy for Azure-hosted .NET APIs, including expand-contract changes, locking risk, rollback, and deployment order.
Sizes per-instance database concurrency from workload and database capacity instead of equating more connections with more throughput.
Validates size and signature, writes under a generated storage key, and keeps untrusted files outside the public web root.
Validates a bounded command set completely before applying all updates in one SaveChanges transaction.
Builds a Celery task that survives timeout ambiguity, retries temporary failures, and records one durable business outcome.