Loading
Pick a focused question that fits your time, stack, and interview goal.
298 results across 1 active filter
Page 7 of 13
Explains client cache keys, freshness, invalidation, refetching, optimistic updates, and server truth.
Handles SIGTERM, traffic draining, cancellation, background work, and termination deadlines without losing accepted work or hanging rollout.
Uses a test-only DbCommandInterceptor to fail a regression when database command count grows with page size.
Uses the client's original rowversion to detect a lost update and return a deliberate conflict response.
Investigate and mitigate API failures caused by a slow or failing downstream dependency.
Separates caller cancellation from a dependency timeout and maps expected downstream outcomes safely.
Makes EF Core transient retries safe across transactions, uncertain commits, generated keys, and external side effects.
Explains optimistic concurrency with EF Core rowversion tokens, API conflict responses, and safe retry boundaries.
Explains logout semantics for token-based APIs, revoking refresh tokens, device/session records, and short-lived access-token limits.
Keeps long-running queue work safe when message ownership expires, renewal fails, settlement is uncertain, or another worker receives the same job.
Explains Redis memory pressure, eviction policies, key sizing, TTL discipline, and what happens when the cache is full.
Explains how an API behaves when Redis is unavailable and which cache usages can safely fall back.
Explains stale edit detection, row versioning, conflict UI, refresh behavior, and safe update contracts.
Explains what happens when roles or tenant membership change while access tokens still contain old claims.
Explains initial incident triage: confirm impact, mitigate, assign roles, preserve evidence, and communicate.
Explains why application-level duplicate checks are not enough and how EF Core APIs map database constraints to friendly errors.
Explains staging slots, validation before swap, warm-up, traffic continuity, and safer production releases for App Service APIs.
Explains how App Service plans provide compute capacity, how scale-out affects app instances, and why APIs need stateless design.
Explains deployment versus release, staged enablement, kill switches, cleanup, and App Service slot interaction.
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.
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.