Loading
Pick a focused question that fits your time, stack, and interview goal.
13 results across 1 active filter
Page 1 of 1
Design background jobs that handle cancellation, retries, and duplicate execution without corrupting external state.
Use Channel<T> to coordinate producer/consumer background processing inside a .NET service while respecting backpressure and shutdown.
Explain async/await as C# syntax over Task-based asynchronous work, with attention to non-blocking I/O and request throughput.
Explain why starting background work without awaiting or tracking it is risky in ASP.NET Core applications.
Explain how a .NET BackgroundService should handle cancellation, in-flight work, and application shutdown.
Defines what happens when several operations fail, cancellation arrives, or only part of a parallel batch completes, without orphaning work or hiding errors.
Explain how Task.WhenAll behaves when one or more tasks fail and how to inspect failures safely.
Compare synchronous enumeration with async streaming and explain when IAsyncEnumerable helps with large or delayed data.
Compare Parallel.ForEachAsync and Task.WhenAll for processing collections with async work and controlled concurrency.
Explain when Task.Run is useful, when async/await is enough, and why Task.Run is usually wrong for I/O in ASP.NET Core.
Compare Task and Thread in .NET, including abstraction level, scheduling, and when direct thread management is rarely appropriate.
Use Task.WhenAll to run independent asynchronous I/O operations concurrently while handling exceptions, cancellation, and dependency limits.
Explain the async state machine, continuation scheduling, and exception flow when a C# method awaits a Task.