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.
199 results across 1 active filter
Page 4 of 9
Explains hot-key behavior, traffic concentration, partition pressure, payload size, and mitigation options.
Diagnoses hidden per-row EF Core queries and replaces them with a bounded query shape without creating an oversized join.
Investigate a production API slowdown caused by blocking async calls, thread-pool pressure, and dependency waits.
Explains a telemetry-driven path from slow endpoint symptoms to database, cache, dependency, CPU, or payload root cause.
Separates a live blocking chain from a deadlock victim, gathers the right database evidence, stabilizes the incident, and fixes lock duration or access order.
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.
Diagnoses thread-unsafe scoped dependencies inside parallel execution and redesigns the data boundary without exhausting shared resources.
Investigate and fix an API where client retries create duplicate orders, payments, or records.
Explains how React error boundaries, route errors, safe fallbacks, logging, and recovery work together.
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.
Connects JavaScript tasks and microtasks to rendering, responsiveness, and practical performance fixes.
Explain why starting background work without awaiting or tracking it is risky in ASP.NET Core applications.
Restores client scheme, host, and address behind trusted proxies without accepting spoofed forwarding data from arbitrary callers.
Explains practical frontend performance work: measuring, render cost, memoization, bundle splitting, images, and hydration.
Explain how a .NET BackgroundService should handle cancellation, in-flight work, and application shutdown.
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.
Makes EF Core transient retries safe across transactions, uncertain commits, generated keys, and external side effects.