Loading
Pick a focused question that fits your time, stack, and interview goal.
690 results
Page 23 of 29
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.
Compares revert and reset, especially for shared branches and production-safe history.
Reviews a proposed response-field rename by finding consumers, classifying the break, choosing a migration path, and proving rollout and removal are safe.
Reviews and stages destructive EF Core schema changes around live data, locks, mixed application versions, recovery, and rollback.
Explains how to choose rollback, swap-back, hotfix, or roll-forward after a failed Azure App Service deployment.
Compares rollback and roll-forward decisions after a failed production deployment.
Coordinates old and new application versions, expand-and-contract schema changes, migration ownership, readiness, and rollback during rolling releases.
Places identity, optional selection controls, command representations, headers, and files in predictable HTTP locations while accounting for security, caching, limits, and model binding.
Reduces container privileges through non-root execution, minimal images, controlled filesystems, and explicit capability requirements.
Explains how callers use one contract while runtime dispatch selects implementation, then connects that mechanism to extensible behavior.
Explains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.
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.
Explains safe handling of secrets and environment-specific configuration in CI/CD pipelines.
Protects source, dependencies, workflows, build identities, runners, artifacts, and deployment verification while preserving traceability and patch response.