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.
465 results across 1 active filter
Page 9 of 20
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.
Explains how an API behaves when Redis is unavailable and which cache usages can safely fall back.
Explains what happens when roles or tenant membership change while access tokens still contain old claims.
Explains initial incident triage: confirm impact, mitigate, assign roles, preserve evidence, and communicate.
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.
Shows how publisher-to-subscriber references can retain objects and how to clean up event-based lifetimes.
Focuses on ToList chains, collection capacity, repeated enumeration, and memory-aware data shaping.
Explains staging slots, validation before swap, warm-up, traffic continuity, and safer production releases for App Service APIs.