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.
405 results across 1 active filter
Page 13 of 17
Explains correlation IDs across request logs, dependency calls, queues, workers, and support investigations.
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.
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.
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.
Repairs a workflow when a remote operation may have succeeded but local state, messages, and callbacks disagree.
Replaces a parent query plus one status query per row with one server-side projection.
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.
Explains when production approvals are useful and how to avoid turning them into empty bureaucracy.
Explains how to trace a production deployment back to commit, build, artifact, configuration, and approval.
Evaluates repositories by domain language, query ownership, and substitutability instead of treating them as a mandatory wrapper around DbSet.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Explains how Aspire references inject resource configuration, how logical service names resolve, and why dependency wiring differs from startup readiness.
Explains why committed headers cannot be replaced, how streaming failures behave, and how middleware preserves response ownership.
Coordinates server retry signals with client backoff, deadlines, idempotency, overload protection, and bounded retry budgets.
Wraps a complete explicit transaction in the provider execution strategy and creates fresh context state for each retry attempt.
Classifies retryable outcomes and applies bounded attempts, exponential backoff, jitter, deadlines, and idempotency.