Pick a focused question that fits your time, stack, and interview goal.
281 results across 1 active filter
Page 12 of 12
Practices incident response after an OOM: restore service, collect evidence, identify trigger, and prevent recurrence.
Explains string immutability, concatenation behavior, and pragmatic use of StringBuilder in .NET.
Distinguishes deterministic cleanup from finalization and explains resource ownership in normal application code.
Explains asynchronous cleanup for resources whose shutdown path needs async work, such as flushing or closing remote connections.
Evaluates whether read-heavy access justifies a reader/writer lock instead of a simpler lock or immutable snapshot.
Covers large exports, uploads, and API responses where bounded memory matters more than convenience.
Explains minimal APIs, endpoint groups, dependency injection, typed results, filters, and when they fit real services.
Introduces lower-level allocation tools while emphasizing measurement, ownership, and safe usage.
Identifies useful memory and GC signals for alerting without overwhelming the team with noisy telemetry.
Explain why async void is usually dangerous outside event handlers and how exceptions behave differently.
Explains returning EF entities from APIs with practical .NET data-access examples and production trade-offs.
Covers the Large Object Heap, big buffers, fragmentation pressure, and practical ways to avoid loading too much at once.
Explains how middleware order affects authentication, authorization, error handling, routing, CORS, and response behavior.
Explains cache memory growth, eviction, size limits, stale data, and why cache design needs explicit bounds.
Reviews a captive scoped dependency as both a lifetime and concurrency bug, then replaces it with explicit per-operation scopes and minimal immutable work data.
Diagnoses lost struct mutations and explains how readonly access can trigger defensive copies.
Separates memory visibility and ordering from atomic multi-step updates, avoiding volatile as a substitute for real synchronization.