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.
1225 drills fit a 20-minute session. Closest fits first.
Page 49 of 52
Explains controller actions, result types, status codes, thin controllers, and HTTP response generation.
Introduces managed heap cleanup, generational collection, object lifetime, and why allocation behavior affects .NET services.
Explains container ownership, dependency declarations, bean creation, and why dependency injection is a specific form of inversion of control.
Explains Python assignment as name binding and connects identity, type, value, aliasing, mutation, and rebinding.
Explains Java primitives and references through observable language behavior without relying on an inaccurate stack-versus-heap shortcut.
Compares JavaScript declarations through scope, initialization, redeclaration, reassignment, and practical default choices.
Chooses Python collections by ordering, uniqueness, lookup, mutability, and domain intent rather than complexity slogans alone.
Chooses a Java collection by the behavior the code needs: ordering, duplicates, membership, lookup keys, and iteration.
Explains release notes and changelog thinking for engineering, QA, support, and product communication.
Constructs a service directly with explicit collaborators and verifies behavior without Spring startup or framework-owned concerns.
Explains semantic versioning for .NET applications and how it communicates release impact.
Covers App Service app settings, environment-specific configuration, restarts, slot settings, and avoiding hard-coded production values.
Explains DbContext lifetime and unit-of-work boundaries with practical .NET data-access examples and production trade-offs.
Explains a practical Git workflow for a .NET team using branches, pull requests, code review, and protected main branches.
Designs consumer-focused contracts that reduce accidental authority and coupling without producing meaningless one-method wrappers.
Explains cache observability across hit rate, latency, source load, memory, evictions, stale data, and fallback behavior.
Starts object-oriented design from cohesive state and behavior instead of creating classes for every noun in a requirement.
Explains when backend work belongs in a queue instead of slow or unreliable inline request handling.
Explains correlation IDs across request logs, dependency calls, queues, workers, and support investigations.
Separates dependency registration from per-request middleware and endpoint composition in modern ASP.NET Core startup.
Explains safe error responses for auth failures, validation failures, server errors, and sensitive resource access.
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Uses static members for type-wide stateless behavior and constants while avoiding hidden global mutable state and lifetime problems.
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.