Loading
Pick a focused question that fits your time, stack, and interview goal.
281 results across 1 active filter
Page 11 of 12
Diagnose thread-pool starvation caused by blocking work, unbounded concurrency, or sync-over-async in .NET APIs.
Diagnose an ASP.NET Core API that becomes slow because request threads are blocked or exhausted.
Uses runtime-supported initialization rather than timing-dependent manual checks and defines failure, retry, and disposal behavior explicitly.
Distinguish timeouts from cancellation and explain how to combine them around external calls and request handling.
Tests that an unexpected failure returns a safe correlation identifier and records the same value in structured logs.
Attaches a key-only stub and marks one property modified for a narrow update while naming the rules this pattern bypasses.
Use correlation IDs, structured logs, and logging scopes to make API failures traceable in production.
Redesigns read-heavy shared state so readers observe a complete version without coordinating every access through a lock.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.
Explains read models for complex API screens with practical .NET data-access examples and production trade-offs.
Explains middleware continuation, terminal delegates, path branches, short-circuiting, and two-way request and response flow.
Use SemaphoreSlim to bound concurrent asynchronous work without blocking threads unnecessarily.
Use Task.WhenAll to run independent asynchronous I/O operations concurrently while handling exceptions, cancellation, and dependency limits.
Implements a small validation helper for date ranges with clear error messages.
Explains what is copied when values and object references are assigned or passed, including the explicit effect of ref, out, and in.
Captures test activities to prove one incoming request and its outgoing HTTP dependency share trace context.
Explain the async state machine, continuation scheduling, and exception flow when a C# method awaits a Task.
Explains LINQ deferred execution with EF Core with practical .NET data-access examples and production trade-offs.
Explains how route values, query strings, headers, and request bodies become typed endpoint input.
Clarifies the difference between objects being retained accidentally and code simply allocating too much temporary memory.
Explains N+1 queries in EF Core with practical .NET data-access examples and production trade-offs.
Explains how GC roots retain reachable object graphs and turns heap evidence into a concrete ownership fix for static state, events, closures, queues, and caches.
Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.
Explains why memory diagnostics need access control, retention limits, and careful handling of secrets and user data.