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 18 of 24
Separates restricted mutation access from a stable immutable value and chooses snapshots or structural sharing deliberately.
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.
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.
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.
Implements a bounded async retry helper that respects cancellation and does not retry every exception blindly.
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.
Persists a job and outbox command before returning a status URL for long-running work.
Produces field-keyed validation errors through one reusable endpoint boundary.
Explains safe error responses for auth failures, validation failures, server errors, and sensitive resource access.
Implements top-K frequency selection with deterministic tie-breaking.
Explains why Redis connections are reused, how timeouts protect API threads, and how to diagnose client-side Redis pressure.
Compares revert and reset, especially for shared branches and production-safe history.