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.
326 results across 1 active filter
Page 11 of 14
Explains compatible full-stack deployment, backend enforcement, staged rollout, telemetry, safe disablement, rollback decisions, and flag cleanup.
Ranks duplicate import rows, previews the deletion set, and removes older copies with deterministic retention.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Uses a database transaction and row lock to keep stock non-negative when reservations race.
Uses a conditional update and transaction to prevent overselling while recording the reservation consistently.
Explains how Aspire references inject resource configuration, how logical service names resolve, and why dependency wiring differs from startup readiness.
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.
Explains why Redis connections are reused, how timeouts protect API threads, and how to diagnose client-side Redis pressure.
Reviews and stages destructive EF Core schema changes around live data, locks, mixed application versions, recovery, and rollback.
Coordinates old and new application versions, expand-and-contract schema changes, migration ownership, readiness, and rollback during rolling releases.
Fetches multiple URLs with bounded concurrency, per-request and batch deadlines, cancellation, ordered results, and executor cleanup.
Reduces container privileges through non-root execution, minimal images, controlled filesystems, and explicit capability requirements.
Explains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.
Persists business state and durable publication intent atomically, leaving broker delivery to an idempotent retrying publisher.
Persists business state and durable publication intent atomically while leaving broker delivery to an idempotent publisher.
Persists domain state and its outbox message in one SaveChanges transaction without publishing inside the request transaction.
Explains how multiple worker instances share queue work and what limits safe scaling.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.