Loading
Pick a focused question that fits your time, stack, and interview goal.
473 results across 1 active filter
Page 9 of 20
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.
Implements a stable first-unique-character search using counts and original order.
Uses NOT EXISTS to express an anti-join without null traps or duplicate parent rows.
Explain why starting background work without awaiting or tracking it is risky in ASP.NET Core applications.
Explains why cached authorization decisions are risky and how to bound or invalidate permission-related cache safely.
Flattens a tree into display paths while preserving order and preventing simple cycles.
Uses a recursive CTE to return hierarchy depth and a readable root-to-node path.
Frames a vague system-design problem with explicit flows, constraints, scale estimates, and measurable quality targets before selecting components.
Uses constraints to express required operations and explains safe assignment direction for generic producers and consumers.
Explains how tags and release branches support traceability, hotfixes, and production versioning.
Explains global query filters in EF Core with practical .NET data-access examples and production trade-offs.
Handles SIGTERM, traffic draining, cancellation, background work, and termination deadlines without losing accepted work or hanging rollout.
Explain how a .NET BackgroundService should handle cancellation, in-flight work, and application shutdown.
Builds customer summaries from order rows using grouping, aggregation, and deterministic ordering.
Uses a test-only DbCommandInterceptor to fail a regression when database command count grows with page size.
Uses the client's original rowversion to detect a lost update and return a deliberate conflict response.
Investigate and mitigate API failures caused by a slow or failing downstream dependency.
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 logout semantics for token-based APIs, revoking refresh tokens, device/session records, and short-lived access-token limits.
Keeps long-running queue work safe when message ownership expires, renewal fails, settlement is uncertain, or another worker receives the same job.
Explains Redis memory pressure, eviction policies, key sizing, TTL discipline, and what happens when the cache is full.