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.
439 results across 1 active filter
Page 17 of 19
Diagnose an ASP.NET Core API that becomes slow because request threads are blocked or exhausted.
Distinguish timeouts from cancellation and explain how to combine them around external calls and request handling.
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.
Attaches a key-only stub and marks one property modified for a narrow update while naming the rules this pattern bypasses.
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 when a Next.js route layer helps with cookies, tokens, aggregation, and UI-specific API adaptation.
Explains policy-based authorization, requirements, handlers, claims, capabilities, and resource-aware checks.
Explains the cache-aside pattern for read-heavy endpoints and how misses, TTLs, and source-of-truth reads fit together.
Explains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.
Use correlation IDs, structured logs, and logging scopes to make API failures traceable in production.
Uses EF Core context pooling only when reusable context state, tenant isolation, and underlying connection state are controlled and tested.
Explains when EF Core compiled queries help, what they do not fix, and how to measure their value.
Explains how query tags, request correlation, and telemetry help connect slow SQL back to code paths.
Explains when set-based EF Core updates are better than loading entities and where lifecycle behavior can differ.
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.
Explains route handlers as a frontend server boundary for cookies, API adaptation, auth, and backend calls.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.