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.
405 results across 1 active filter
Page 15 of 17
Designs cancellation-aware response streaming with bounded memory, correct resource ownership, and practical download behavior.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.
Investigate blocked request threads and thread-pool starvation caused by Result, Wait, or GetAwaiter().GetResult().
Adds a stable query tag and inspects generated SQL without embedding user data or enabling unsafe global logging.
Explain when Task.Run is useful, when async/await is enough, and why Task.Run is usually wrong for I/O in ASP.NET Core.
Compare Task and Thread in .NET, including abstraction level, scheduling, and when direct thread management is rarely appropriate.
Expresses allowed and denied capability combinations as one parameterized API integration test.
Proves repeated requests with one idempotency key create one resource and return a consistent result.
Combines schema diffing, real provider tests, consumer expectations, generated clients, semantic scenarios, and rollout evidence to prevent accidental API breaks.
Proves that one authenticated user cannot read or modify another user's private resource.
Designs integration tests for authentication, capabilities, ownership, account status, and cross-tenant isolation without bypassing the real authorization pipeline.
Uses a controllable fake HTTP handler to prove request cancellation reaches a downstream dependency.
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.
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.