Loading
Pick a focused question that fits your time, stack, and interview goal.
460 drills fit a 10-minute session. Closest fits first.
Page 14 of 20
Compare Parallel.ForEachAsync and Task.WhenAll for processing collections with async work and controlled concurrency.
Chooses a parallel API based on whether the workload is a data query or an imperative loop and keeps CPU work pure, bounded, and measurable.
Explains how to verify a .NET release after deployment using smoke tests, metrics, logs, and business signals.
Explains what happens when a hot key expires and how request coalescing, TTL jitter, background refresh, and stale serving help.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Explains insecure direct object reference risks and how APIs enforce ownership, tenant scope, and authorization per resource.
Explains why request DTOs should expose only allowed fields and how server-owned fields stay protected.
Uses RFC 9457 Problem Details as a stable, safe error contract with documented problem types, actionable extensions, and centralized ASP.NET mapping.
Explains EF Core projections for API read models that need related names, counts, and summaries without loading full graphs.
Explains where secrets and tokens should live, what not to log, how rotation works, and how client storage changes risk.
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.