Loading
Pick a focused question that fits your time, stack, and interview goal.
281 results across 1 active filter
Page 10 of 12
Explains the output shape of core LINQ transformations and uses them without hiding empty groups, duplicate keys, or excessive buffering.
Uses static members for type-wide stateless behavior and constants while avoiding hidden global mutable state and lifetime problems.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
Distinguishes operators that can yield incrementally from operators that must consume substantial input before producing results.
Uses async streams for incremental asynchronous production while preserving cancellation, disposal, backpressure expectations, and API boundaries.
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.
Investigate deadlocks or starvation caused by blocking on async code with 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.
Moves invariant-sensitive decisions toward the owning object while keeping orchestration, queries, and cross-boundary work appropriately explicit.
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.
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.