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.
584 results across 1 active filter
Page 19 of 25
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.
Ranks duplicate import rows, previews the deletion set, and removes older copies with deterministic retention.
Uses server-resolved capabilities for presentation while keeping the mutation endpoint authoritative.
Uses an explicit state model for initial loading, success, empty, recoverable error, and refetching.
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.
Handles the request body as a forward-only resource, buffers only when necessary, and enforces limits before large input consumes the service.
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.
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.
Writes a left-join aggregate that keeps active customers with no paid orders and applies date filters without changing join semantics.
Explains safe error responses for auth failures, validation failures, server errors, and sensitive resource access.
Uses ROW_NUMBER with a deterministic tie-breaker to return the complete latest status row per order.
Implements top-K frequency selection with deterministic tie-breaking.
Aggregates product sales and ranks independently inside each category with a deterministic top-N rule.
Explains why Redis connections are reused, how timeouts protect API threads, and how to diagnose client-side Redis pressure.