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.
391 results across 1 active filter
Page 5 of 17
Explains how managed changes become SQL at flush and why flush is not the same as a durable commit.
Explains circular lock waits, consistent ordering, reduced lock scope, timed acquisition, and thread-dump confirmation.
Connects identity, sequence, table, UUID, and assigned identifiers to database support, round trips, ordering, and batch inserts.
Explains mapping fetch semantics while separating them from the query-specific data shape an endpoint actually needs.
Explains one observation lifecycle feeding metrics, tracing, and context through registered handlers.
Explains first-match chain selection, rule matching inside a chain, ordering, fallback coverage, and accidental unprotected paths.
Explains how input conversion, strict validation, and extra-field policies change what an API accepts and preserves.
Explains pytest fixture dependency resolution, caching, lifetime, and the isolation cost of wider scopes.
Compares joining an existing transaction, suspending it for an independent transaction, and using a savepoint-backed nested scope.
Treats GrantedAuthority as the common representation while explaining role prefixes, scope mapping, and domain permission design.
Explains proxy interception, target delegation, JDK versus class proxies, method limits, and the self-invocation boundary.
Explains object identity, tracked changes, flush ordering, and the limits of session-level caching.
Uses Django cache configuration to control freshness, namespace sharing, and safe cache migrations.
Explains cheap JVM-scheduled threads, blocking-I/O throughput, carrier pinning, ThreadLocal cost, and unchanged downstream limits.
Explains per-worker memory and copy-on-write savings without preloading process-unsafe resources.
Connects Django deployment interfaces with the real sync and async call chain.
Explains reverse-order fixture cleanup and designs teardown that remains safe when setup or tests fail.
Maps each part of the HTTP request to explicit controller arguments and distinguishes conversion, model binding, and body conversion.
Chooses the smallest DRF view abstraction that expresses an endpoint clearly.
Chooses a concurrency model from workload, libraries, isolation, runtime build, and operational cost.
Chooses relationship loading from cardinality, query count, result size, and hidden-I/O boundaries.
Chooses a Java collection by the behavior the code needs: ordering, duplicates, membership, lookup keys, and iteration.
Selects the smallest Spring test scope that can prove the risky boundary without mocking away framework or infrastructure behavior.
Builds stable Micrometer dimensions that answer operational questions without unbounded time series and cost.