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 6 of 17
Configures finite origins, methods, headers, credentials, and preflight behavior while separating browser enforcement from authorization.
Uses generated repository behavior for simple cases and explicit query or implementation boundaries when the use case becomes complex.
Designs executor ownership, pool size, queue capacity, rejection, shutdown, task context, and observability around workload behavior.
Traces the injection point, candidate type, registration path, conditions, profiles, generics, qualifiers, and package boundaries.
Finds repeated association queries with SQL evidence and chooses a bounded fetch or projection without creating a cartesian result.
Finds synchronous I/O or CPU work that prevents the event loop from scheduling other tasks.
Classifies mapping, conversion, binding, validation, multipart, CORS, filter, and negotiation failures before changing controller code.
Locates pre-handler failures across proxies, routing, parsing, validation, dependencies, and middleware using structured evidence.
Combines asyncio debug evidence, task inspection, warnings, profiling, and capacity signals.
Distinguishes missing-class and incompatible-class failures, then traces them to the actual packaged runtime dependency graph.
Models partial updates without confusing omitted fields, explicit nulls, defaults, or unauthorized changes.
Prefers compatible evolution, uses Spring version resolution when a breaking contract requires it, and operates deprecation deliberately.
Maps a bounded public list contract to Spring arguments without exposing persistence property names or unstable ordering.
Separates authentication challenge from denied authorization and traces the selected entry point, denied handler, and matched rule.
Treats a bean cycle as a design signal, explains constructor failure, and uses delayed resolution only for genuine lifecycle boundaries.
Defines fail-fast, all-results, and partial-success behavior for concurrent asyncio operations.
Maps known framework and application failures to RFC 9457 responses while preserving stable codes, safe detail, and correlation.
Controls operation identities, request and response schemas, error documentation, and compatibility checks without hand-maintaining a second contract.
Places semaphore and admission boundaries around scarce work without retaining unlimited tasks.
Connects virtual environments, pyproject metadata, version constraints, lock artifacts, Python versions, and CI verification.
Combines JDBC batching, compatible identifiers, periodic flush and clear, bounded transactions, and explicit bulk-operation semantics.
Produces a pinned, reviewable Python artifact once and promotes the same image across environments.
Keeps domain outcomes transport-neutral and maps not-found, conflict, invalid transition, and dependency failure at the web boundary.
Chooses atomic database expressions, row locks, and constraints from the invariant being protected.