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.
690 results
Page 24 of 29
Separates identity issuance, untrusted client behavior, API authorization, tenant isolation, resource checks, and token-handling responsibilities.
Uses separate models where they protect contracts, invariants, or storage evolution while avoiding repetitive mapping with no boundary value.
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.
Explains Next.js server/client component boundaries, interactivity, data access, serialization, and bundle impact.
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.
Explains EF Core shadow properties for audit or infrastructure columns with practical .NET data-access examples and production trade-offs.
Explains the output shape of core LINQ transformations and uses them without hiding empty groups, duplicate keys, or excessive buffering.
Shapes an API list from its contract and cardinality, projecting only required values while preserving authorization, stable pagination, bounded nesting, index support, and measurable query cost.
Applies single responsibility to reasons for change, cohesive behavior, and maintainable service boundaries instead of counting methods.
Builds fast, safe deployment smoke checks that verify readiness and one critical business path, then combine their result with live telemetry to promote, pause, or roll back.
Keeps data and secrets on the server while sending a small serializable model to an interactive client component.
Explains server rendering, client rendering, static rendering, freshness, SEO, personalization, and performance trade-offs.
Explains asynchronous-looking state updates, batching, functional setters, and avoiding stale values.
Uses static members for type-wide stateless behavior and constants while avoiding hidden global mutable state and lifetime problems.
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.
Distinguishes operators that can yield incrementally from operators that must consume substantial input before producing results.
Designs cancellation-aware response streaming with bounded memory, correct resource ownership, and practical download behavior.
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.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.