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.
185 results across 1 active filter
Page 7 of 8
Explains what happens when a hot key expires and how request coalescing, TTL jitter, background refresh, and stale serving help.
Explains insecure direct object reference risks and how APIs enforce ownership, tenant scope, and authorization per resource.
Explains why request DTOs should expose only allowed fields and how server-owned fields stay protected.
Explains correlation IDs across request logs, dependency calls, queues, workers, and support investigations.
Explains where secrets and tokens should live, what not to log, how rotation works, and how client storage changes risk.
Uses an actual execution plan, row-flow evidence, runtime measurements, and representative parameters to diagnose a slow query without guessing.
Repairs a workflow when a remote operation may have succeeded but local state, messages, and callbacks disagree.
Explains how to inspect, fix, replay, skip, or archive dead-letter messages without repeating bad side effects.
Replaces a parent query plus one status query per row with one server-side projection.
Explains compatible full-stack deployment, backend enforcement, staged rollout, telemetry, safe disablement, rollback decisions, and flag cleanup.
Explains safe error responses for auth failures, validation failures, server errors, and sensitive resource access.
Explains why Redis connections are reused, how timeouts protect API threads, and how to diagnose client-side Redis pressure.
Explains how multiple worker instances share queue work and what limits safe scaling.
Chooses event retention and compaction from consumer outage, replay, rebuild, audit, and disaster-recovery requirements rather than storage cost alone.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.
Adds a stable query tag and inspects generated SQL without embedding user data or enabling unsafe global logging.
Tests that an unexpected failure returns a safe correlation identifier and records the same value in structured logs.
Explains tracing one user action across browser, frontend server, API, dependencies, logs, metrics, and safe diagnostics.
Uses live runtime and application counters to classify CPU, memory, GC, exception, request, and ThreadPool symptoms before deeper collection.
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 policy-based authorization, requirements, handlers, claims, capabilities, and resource-aware checks.
Explains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.