Pick a focused question that fits your time, stack, and interview goal.
281 results across 1 active filter
Page 6 of 12
Explains when to capture dumps, what to compare, and how to use roots without turning dumps into guesswork.
Explains SQL joins for API response shapes with practical .NET data-access examples and production trade-offs.
Draws a short atomic database boundary around one invariant while moving network side effects into explicit, recoverable workflow states.
Explains EF Core query performance diagnostics with practical .NET data-access examples and production trade-offs.
Explains safe EF Core migrations with practical .NET data-access examples and production trade-offs.
Propagates request cancellation through async dependencies while keeping committed side effects and timeout policy explicit.
Explains DbContext lifetime and unit-of-work boundaries with practical .NET data-access examples and production trade-offs.
Explain how Task.WhenAll behaves when one or more tasks fail and how to inspect failures safely.
Covers allocation rate, collection frequency, latency symptoms, and safe production steps for GC-heavy services.
Uses file upload processing to practice bounded memory, stream ownership, temporary files, and retained buffers.
Covers chunking, bounded concurrency, scoped dependencies, progress, retries, and avoiding full-dataset memory spikes.
Turns LOH theory into an API investigation around large payloads, buffers, serialization, and concurrency.
Gives a practical incident flow for memory growth using metrics, traffic correlation, heap evidence, and safe mitigation.
Frames allocation reduction as measurement-driven API work rather than premature micro-optimization.
Describes lazy iterator execution, state-machine behavior, early termination, resource disposal, and repeat-enumeration consequences.
Keeps HttpContext inside the active request, avoids concurrent access, and copies only immutable data needed by later work.
Compare synchronous enumeration with async streaming and explain when IAsyncEnumerable helps with large or delayed data.
Chooses immutable values and controlled mutable entities based on identity, concurrency, invariants, allocation cost, and update semantics.
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 bounded readiness check for one required dependency while keeping liveness independent and responses non-sensitive.
Stores an idempotency key, request hash, and response in the same transaction as the created resource.
Implements a small in-memory fixed-window rate limiter with per-key counters.
Implements a small LRU cache using a dictionary plus linked list for O(1) get and put.