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.
326 results across 1 active filter
Page 12 of 14
Protects source, dependencies, workflows, build identities, runners, artifacts, and deployment verification while preserving traceability and patch response.
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Explains cached value serialization, schema versioning, deploy compatibility, and safe handling of old payloads.
Chooses event retention and compaction from consumer outage, replay, rebuild, audit, and disaster-recovery requirements rather than storage cost alone.
Sets bounded timeout and deadline policies across callers, APIs, databases, and external services without hiding unknown outcomes.
Builds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.
Wraps widget creation, listeners, observers, timers, and destruction in one lifecycle boundary and verifies repeated navigation does not accumulate resources.
Explains session state choices for scaled-out ASP.NET Core APIs and when Redis-backed state is appropriate.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
Designs cancellation-aware response streaming with bounded memory, correct resource ownership, and practical download behavior.
Structures xUnit tests around per-test instances and shares only expensive infrastructure through deliberate class, collection, or assembly fixture lifetimes while preserving isolation and parallel safety.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.
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.
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.
Tests that an unexpected failure returns a safe correlation identifier and records the same value in structured logs.
Explains how to diagnose and mitigate a downstream dependency slowing the API through timeouts, retries, and degraded behavior.