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.
613 results across 1 active filter
Page 19 of 26
Carries the ASP.NET Core request token into a bounded EF Core query while keeping cancellation separate from business rollback guarantees.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
Explains token storage, cookies, XSS, CSRF, and why browser UI never replaces server authorization.
Explains where secrets and tokens should live, what not to log, how rotation works, and how client storage changes risk.
Combines ThreadPool counters, repeated stack snapshots, and wait-event traces to distinguish blocked workers from CPU or dependency pressure.
Compare public and internal APIs in terms of compatibility, documentation, security, support, and evolution speed.
Builds a story about challenging a risky requirement while staying constructive and product-oriented.
Compares replacement and partial-update semantics, including omitted fields, patch formats, validation, and concurrency.
Explains useful quality gates for .NET CI pipelines, including tests, analysis, security, migrations, and smoke checks.
Converts local-day boundaries to UTC once, preserving correct daylight-saving behavior and index use on stored UTC timestamps.
Fits database command timeouts into endpoint latency budgets while diagnosing slow SQL, blocking, pool pressure, and uncertain write outcomes.
Investigate and fix a race condition caused by shared mutable state in a .NET service.
Separates traffic eligibility, process recovery, and slow startup so health checks do not amplify dependency failures or restart healthy work.
Separates restricted mutation access from a stable immutable value and chooses snapshots or structural sharing deliberately.
Builds a story about taking feedback seriously and changing behavior in a visible way.
Explains stale closures in callbacks, effects, timers, subscriptions, and how to fix them cleanly.
Repairs a workflow when a remote operation may have succeeded but local state, messages, and callbacks disagree.
Explains how to inspect, fix, replay, skip, or archive dead-letter messages without repeating bad side effects.
Implements safe redaction of known sensitive keys in a dictionary before logging.
Uses profiler evidence to isolate expensive derived data and row rendering, then applies memoization without hiding correctness bugs.
Replaces a parent query plus one status query per row with one server-side projection.
Uses metadata-driven behavior deliberately and protects reflection-dependent code when publishing with trimming or ahead-of-time compilation.
Separates dependency registration from per-request middleware and endpoint composition in modern ASP.NET Core startup.
Explains compatible full-stack deployment, backend enforcement, staged rollout, telemetry, safe disablement, rollback decisions, and flag cleanup.