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.
591 results across 1 active filter
Page 22 of 25
Tests asynchronous completion, caller cancellation, owned timeouts, cleanup, and race-sensitive side effects deterministically with controlled dependencies and bounded diagnostics.
Designs integration tests for authentication, capabilities, ownership, account status, and cross-tenant isolation without bypassing the real authorization pipeline.
Tests durable background processing across duplicate delivery, retries, acknowledgement timing, crashes, poison messages, and observable completion.
Distinguishes observable contracts from incidental calls while preserving important interaction assertions.
Uses a controllable fake HTTP handler to prove request cancellation reaches a downstream dependency.
Verifies migration SQL, data preservation, production-provider behavior, mixed application versions, backfills, and expand-contract releases.
Combines protocol stubs, contract checks, sandbox tests, and failure simulation without depending on live production services.
Walks API pages through equal sort values and verifies no duplicate or missing resource ids.
Verifies status, content type, stable error extensions, and field errors for an invalid API request.
Diagnose thread-pool starvation caused by blocking work, unbounded concurrency, or sync-over-async in .NET APIs.
Diagnose an ASP.NET Core API that becomes slow because request threads are blocked or exhausted.
Uses runtime-supported initialization rather than timing-dependent manual checks and defines failure, retry, and disposal behavior explicitly.
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.