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.
300 results across 1 active filter
Page 11 of 13
Chooses among explicit joins, reusable fetch graphs, and bounded secondary selects based on query shape and cardinality.
Places protocol-wide work in filters, handler-aware MVC work in interceptors, and controller exception or body concerns in advice.
Uses bounds to express capabilities required by generic code and distinguishes them from wildcard flexibility at call sites.
Chooses stereotype scanning for owned application components and explicit factory methods for third-party types, construction policy, and visible composition.
Uses typed grouped binding and validation for application configuration while reserving @Value for small isolated expressions.
Prefers constructor injection for required dependencies while explaining the limited roles and costs of setter and field injection.
Chooses a query representation from static versus dynamic shape, portability, database features, readability, and performance evidence.
Chooses version-based conflict detection or database locks from contention, transaction duration, and invariant needs.
Uses HTTP rules for route-level policy and method security for reusable service operations without creating contradictory enforcement.
Chooses synchronous, reactive, or declarative clients based on the application's execution model while keeping shared timeout and error policy explicit.
Chooses credential transport and server state from client shape, revocation, browser threats, scaling, and operational requirements.
Chooses hooks by application readiness phase and keeps migrations, warm-up, listeners, and background resources owned and observable.
Uses profiles for named environment or deployment groups and focused conditions for feature or capability selection.
Chooses a focused MVC slice or full application context based on whether the risk is the web contract or complete wiring.
Chooses dataclasses for transparent data-oriented types while preserving invariants, safe defaults, and honest immutability claims.
Positions records as transparent, shallowly immutable data carriers with generated value-oriented members and clear modeling limits.
Bases CSRF policy on whether browsers automatically attach credentials and keeps unsafe requests protected without disabling security globally.
Distinguishes small in-process post-response work from durable, retryable, independently operated jobs.
Frames inheritance as a behavioral is-a relationship whose subtypes must remain valid substitutes, not merely a code-reuse shortcut.
Uses generated examples to test stable invariants while preserving readable examples and reproducible failures.
Chooses a Django user model early and preserves swappable references without turning it into a profile dumping ground.
Varies DRF query and representation behavior deliberately across list, detail, and write actions.
Chooses between FastAPI-managed response processing and direct control over the HTTP response.
Uses fixture factories and test-data builders to keep setup flexible, readable, and owned by each test.