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.
298 results across 1 active filter
Page 12 of 13
Tests that an unexpected failure returns a safe correlation identifier and records the same value in structured logs.
Explains how to diagnose and mitigate a downstream dependency slowing the API through timeouts, retries, and degraded behavior.
Explains how to investigate queue age, backlog, worker health, poison messages, dependency failures, and safe catch-up.
Explains post-incident review, root cause, contributing factors, action items, tests, alerts, runbooks, and ownership.
Explains closed, open, and half-open behavior, failure classification, recovery probes, and the limits of circuit breakers.
Explains the boundary between OAuth/OIDC identity, application users, claims mapping, roles, and app-specific permissions.
Explains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.
Explains delayed delivery, scheduled work, reminders, retry timing, cancellation, and clock-related trade-offs.
Explains when set-based EF Core updates are better than loading entities and where lifecycle behavior can differ.
Explains referential integrity, cascade delete trade-offs, restrict behavior, soft deletes, and operational safety.
Connects HTTP preconditions to atomic database concurrency checks and honest 412 or 428 API behavior.
Explains the different diagnostic roles of logs, metrics, and traces during backend production issues.
Prevents lost updates with an original rowversion predicate, maps zero affected rows to an explicit conflict, and defines user, retry, aggregate, and API precondition behavior.
Explains Redis-backed rate-limit counters, atomic increments, windows, identity keys, and fallback behavior.
Explains the risks of Redis-based distributed locks and when database constraints, queues, or idempotency are safer.
Explains HTTPS, HSTS, secure cookies, HttpOnly, SameSite, no-store, and practical API/browser security hardening.
Explains structured logging fields, safe context, redaction, event naming, and avoiding secret or personal-data leaks.
Explains how Suspense boundaries stream useful page regions while coordinating loading, errors, and data ownership.
Makes consumer-side deduplication atomic with the business change while supporting concurrent delivery, retention, replay, and failed processing.
Makes business uniqueness race-safe with the exact database key, while handling normalization, tenant scope, nulls, soft deletion, rollout cleanup, and stable API conflicts.
Explains why external data needs runtime validation even when the application uses TypeScript.
Explains JWT validation, trusted issuers, audiences, expiration, signing keys, claims, and server-side authorization boundaries.
Captures test activities to prove one incoming request and its outgoing HTTP dependency share trace context.
Explains event schema evolution, backward compatibility, additive changes, consumer rollout, and contract ownership.