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 8 of 14
Explains deployment versus release, staged enablement, kill switches, cleanup, and App Service slot interaction.
Explains cache interception, keys, conditions, eviction, proxy self-invocation, and the provider boundary.
Draws a short atomic database boundary around one invariant while moving network side effects into explicit, recoverable workflow states.
Explains safe EF Core migrations with practical .NET data-access examples and production trade-offs.
Explains transient database errors, retry strategy, EF Core execution strategy, idempotency, timeouts, and avoiding retry storms.
Separates restart-worthy process failure from traffic readiness and composes Spring Boot health groups around those meanings.
Builds outbound resilience from deadlines and operation safety, then adds bounded retry, circuit, and concurrency controls with telemetry.
Covers chunking, bounded concurrency, scoped dependencies, progress, retries, and avoiding full-dataset memory spikes.
Explains health endpoints, readiness versus liveness, warm-up, dependency checks, and safe App Service health behavior.
Covers queue-backed work, idempotency, retries, visibility timeout, poison messages, progress tracking, and choosing Storage Queues or Service Bus.
Separates server request capacity from application executor capacity and finds blocking, queueing, rejection, or downstream causes.
Explains safe migration strategy for Azure-hosted .NET APIs, including expand-contract changes, locking risk, rollback, and deployment order.
Keeps cached reads acceptably fresh and prevents hot-key reloads from overwhelming the database across application instances.
Coordinates startup work, readiness, schema compatibility, warmup, and mixed-version traffic during a rolling release.
Binds typed configuration, understands property precedence, validates startup invariants, and keeps secrets outside source control.
Reviews correctness, boundaries, failure behavior, capacity, security, observability, delivery, and recovery through concrete evidence.
Sizes per-instance database concurrency from workload and database capacity instead of equating more connections with more throughput.
Explains correlation IDs, distributed tracing, dependency telemetry, message boundaries, and logs across App Service, queues, and downstream APIs.
Explains how IHttpClientFactory separates short-lived clients from pooled handlers and how concurrency, DNS, resilience, and DI lifetimes still require judgment.
Validates size and signature, writes under a generated storage key, and keeps untrusted files outside the public web root.
Explains upload UX, API boundaries, validation, progress, storage, scanning, failure handling, and safe download behavior.
Validates a bounded command set completely before applying all updates in one SaveChanges transaction.
Builds a bounded readiness check for one required dependency while keeping liveness independent and responses non-sensitive.
Builds a Celery task that survives timeout ambiguity, retries temporary failures, and records one durable business outcome.