Pick a focused question that fits your time, stack, and interview goal.
281 results across 1 active filter
Page 2 of 12
Explain why CancellationTokenSource lifetime matters and how careless timeout creation can leak timers or resources.
Use Channel<T> to coordinate producer/consumer background processing inside a .NET service while respecting backpressure and shutdown.
Chooses contracts and shared implementation based on substitutability, state ownership, evolution, and inheritance constraints.
Chooses a sequential collection from size, mutation, access pattern, memory locality, and the behavior callers actually need.
Avoids hidden quadratic work by indexing repeated matches while preserving duplicate, missing, ordering, and memory semantics.
Compares test doubles by purpose and explains when a real dependency provides a more trustworthy test.
Chooses a type shape from identity, value semantics, mutation, copy cost, default values, and serialization boundaries.
Creates valid objects with clear intent while choosing construction patterns proportionally to optional data, validation, and lifecycle complexity.
Separates ordinal identity comparison from culture-aware display ordering and keeps hash-based collection semantics consistent.
Chooses database test infrastructure by the provider behavior a test must prove.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Chooses between sequence, counted, indexed, set, and dictionary contracts based on required operations and complexity.
Explains how unit, integration, contract, component, and end-to-end tests cover different failure boundaries.
Implements chunking for batch processing without dropping final partial batches.
Explains what a lambda captures, how captured state is shared, and why a long-lived callback can retain more memory than expected.
Review async .NET code that does not accept or propagate CancellationToken and explain the practical production risk.
Uses complexity as a first filter while accounting for constants, locality, allocations, data size, and the complete operation sequence.
Implements comparison for simple semantic version strings with missing patch parts treated as zero.
Builds optional EF Core predicates while preserving server translation, stable ordering, and a bounded result.
Explains composite index column order with practical .NET data-access examples and production trade-offs.
Combines focused collaborators for independent behavior while recognizing cases where a genuine stable hierarchy remains simpler.
Choose between ConcurrentDictionary and explicit locks when managing concurrent in-memory data.
Explains how later configuration providers override earlier values and keeps secrets, environment overrides, and diagnostics within explicit boundaries.
Explain what ConfigureAwait(false) does, why it mattered historically, and how to reason about it in ASP.NET Core and library code.