Loading
Pick a focused question that fits your time, stack, and interview goal.
460 drills fit a 10-minute session. Closest fits first.
Page 8 of 20
Explains when to derive values during render instead of storing duplicate state that can drift.
Explains when a value is wrapped as an object, why unboxing is exact, and how generic APIs can avoid hidden allocations.
Explains URL-backed filters, API query parameters, pagination, sorting, empty states, and shareable list views.
Builds a small, immutable, non-root .NET runtime image with controlled inputs, external configuration, graceful lifecycle behavior, and a practical patching strategy.
Compares build artifacts and deployment packages in a .NET release pipeline.
Explains permission-aware navigation, guarded routes, server authorization, stale capabilities, and safe 401/403 handling.
Explains composing dynamic LINQ filters while keeping query execution in SQL and index-friendly.
Compares caching response-shaped read models with caching domain entities or raw database objects.
Use CancellationToken to stop wasted work when clients disconnect, timeouts expire, or background operations are being shut down.
Explain why CancellationTokenSource lifetime matters and how careless timeout creation can leak timers or resources.
Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.
Chooses contracts and shared implementation based on substitutability, state ownership, evolution, and inheritance constraints.
Avoids hidden quadratic work by indexing repeated matches while preserving duplicate, missing, ordering, and memory semantics.
Compares test doubles by purpose and explains when a real dependency provides a more trustworthy test.
Chooses a type shape from identity, value semantics, mutation, copy cost, default values, and serialization boundaries.
Creates valid objects with clear intent while choosing construction patterns proportionally to optional data, validation, and lifecycle complexity.
Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.
Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.
Chooses a deployment strategy from capacity, compatibility, risk, observability, and rollback needs, then defines progressive promotion and abort signals.
Selects small structural and behavioral patterns from the problem being solved instead of pattern-name recognition.
Separates ordinal identity comparison from culture-aware display ordering and keeps hash-based collection semantics consistent.
Chooses database test infrastructure by the provider behavior a test must prove.
Explains inward dependency flow, stable business policy, adapters, and when a smaller project structure is enough.
Explains cleanup for subscriptions, timers, event listeners, and aborting stale fetches.