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.
460 drills fit a 10-minute session. Closest fits first.
Page 17 of 20
Covers configuration that must stay with a slot, such as connection strings, secrets, callback URLs, and staging-only settings.
Covers symptom-based alerting for latency, error rate, availability, dependency failures, queue length, and resource pressure.
Explains practical pull request review signals for .NET services, including tests, API contracts, migrations, configuration, and operational impact.
Explain the async state machine, continuation scheduling, and exception flow when a C# method awaits a Task.
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.
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.
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.
Explains minimal APIs, endpoint groups, dependency injection, typed results, filters, and when they fit real services.
Identifies useful memory and GC signals for alerting without overwhelming the team with noisy telemetry.
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 local filesystem limits, multiple instances, in-memory state, distributed cache, durable storage, and scale-out-safe API design.
Explains how to choose an E2E flow, control test data, avoid brittleness, and cover frontend/API integration risk.
Explains attribute routing, binding-source inference, automatic validation responses, and where explicit domain validation still belongs.
Chooses counters, traces, stack snapshots, GC dumps, full dumps, or a profiler from the production symptom and investigation cost.
Explains Aspire as a code-first application model and developer experience without confusing it with a production runtime or architecture style.
Separates hiding implementation complexity from controlling access to state, with practical examples where both ideas work together.
Uses public, internal, protected, private, and protected internal deliberately to control API surface and inheritance exposure.
Clarify the common misconception that await starts work on a new thread, and explain what actually happens for I/O-bound operations.
Separates identity establishment from permission decisions and applies ASP.NET Core schemes, policies, tenant boundaries, ownership checks, and correct challenge or forbid behavior.
Explains how TTL choices balance freshness, load reduction, user expectations, and operational safety.