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.
491 results across 1 active filter
Page 17 of 21
Explains how callers use one contract while runtime dispatch selects implementation, then connects that mechanism to extensible behavior.
Explains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.
Persists domain state and its outbox message in one SaveChanges transaction without publishing inside the request transaction.
Explains how multiple worker instances share queue work and what limits safe scaling.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.
Explains safe handling of secrets and environment-specific configuration in CI/CD pipelines.
Protects source, dependencies, workflows, build identities, runners, artifacts, and deployment verification while preserving traceability and patch response.
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.
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.
Applies single responsibility to reasons for change, cohesive behavior, and maintainable service boundaries instead of counting methods.
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.
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.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.
Investigate deadlocks or starvation caused by blocking on async code with Result, Wait, or GetAwaiter().GetResult().