Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
559 results across 1 active filter
Page 23 of 24
Defines abstraction as a deliberate contract over essential behavior, then explains practical C# boundaries and the cost of weak abstractions.
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.
Defines object-oriented programming clearly, then connects objects, responsibilities, and the main OOP mechanisms to practical C# design.
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 Aspire as a code-first application model and developer experience without confusing it with a production runtime or architecture style.
Explains why memory diagnostics need access control, retention limits, and careful handling of secrets and user data.
Covers build-once deployment, tests, artifact traceability, slot deployment, smoke checks, approvals, and post-release monitoring.
Explains a practical CI/CD pipeline for .NET applications from code change to deployment verification.
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.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.
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.