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.
177 results across 1 active filter
Page 5 of 8
Explains a telemetry-driven path from slow endpoint symptoms to database, cache, dependency, CPU, or payload root cause.
Pairs a bounded isolated reproduction with telemetry and a disposal fix for leaked database connections.
Collects a bounded EventPipe CPU trace and reads stack evidence without confusing hot methods, blocked time, native work, or sampling artifacts.
Explains N plus one query behavior, symptoms in APIs, fixes with set-based reads, batching, projections, and monitoring.
Decide whether Azure SQL errors are transient platform faults or a real application/query regression.
Explains command messages versus event messages and how ownership changes their design.
Explains how React error boundaries, route errors, safe fallbacks, logging, and recovery work together.
Explains how consumer groups share event-stream work and how offset commits affect duplicate or lost processing.
Writes predicates the optimizer can use as index search arguments, then proves the effect through plans and reads while balancing computed columns, composite indexes, and write overhead.
Explains parameter sniffing, data skew, cached plans, symptoms, and cautious mitigation options in SQL Server.
Explains how statistics and cardinality estimates affect plan choice, joins, memory grants, and slow queries.
Explains why exactly-once claims do not remove the need for idempotent side effects and consistency boundaries.
Explains what CORS controls, what it does not protect, and why APIs still need authentication and authorization.
Explains why cached authorization decisions are risky and how to bound or invalidate permission-related cache safely.
Frames a vague system-design problem with explicit flows, constraints, scale estimates, and measurable quality targets before selecting components.
Explains practical frontend performance work: measuring, render cost, memoization, bundle splitting, images, and hydration.
Uses a test-only DbCommandInterceptor to fail a regression when database command count grows with page size.
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 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 deployment versus release, staged enablement, kill switches, cleanup, and App Service slot interaction.