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.
618 drills fit a 20-minute session. Closest fits first.
Page 21 of 26
Compares replacement and partial-update semantics, including omitted fields, patch formats, validation, and concurrency.
Explains useful quality gates for .NET CI pipelines, including tests, analysis, security, migrations, and smoke checks.
Fits database command timeouts into endpoint latency budgets while diagnosing slow SQL, blocking, pool pressure, and uncertain write outcomes.
Separates restricted mutation access from a stable immutable value and chooses snapshots or structural sharing deliberately.
Explains compatible full-stack deployment, backend enforcement, staged rollout, telemetry, safe disablement, rollback decisions, and flag cleanup.
Explains how to trace a production deployment back to commit, build, artifact, configuration, and approval.
Explains why committed headers cannot be replaced, how streaming failures behave, and how middleware preserves response ownership.
Classifies retryable outcomes and applies bounded attempts, exponential backoff, jitter, deadlines, and idempotency.
Explains why Redis connections are reused, how timeouts protect API threads, and how to diagnose client-side Redis pressure.
Compares revert and reset, especially for shared branches and production-safe history.
Places identity, optional selection controls, command representations, headers, and files in predictable HTTP locations while accounting for security, caching, limits, and model binding.
Reduces container privileges through non-root execution, minimal images, controlled filesystems, and explicit capability requirements.
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.
Explains safe handling of secrets and environment-specific configuration in CI/CD pipelines.
Uses separate models where they protect contracts, invariants, or storage evolution while avoiding repetitive mapping with no boundary value.
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.
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.