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 9 of 17
Preserves the root cause, separates binding, bean, port, classpath, migration, and external failures, and uses Boot's diagnostic reports.
Separates Python allocation growth from process RSS, native memory, fragmentation, caches, and workload peaks.
Triages heap, Metaspace, native, direct-buffer, thread, and container exhaustion using preserved evidence before changing limits.
Diagnoses queued work, blocked workers, nested submissions, common-pool contention, downstream waits, and misleading CPU symptoms.
Maps DRF and application failures into stable client errors while preserving internal diagnostic evidence.
Maps validation, HTTP, domain, and unexpected failures into a stable client contract while preserving diagnostics.
Places an idempotency key at the Spring boundary while persisting request identity and terminal outcome atomically with business work.
Makes nested create and update semantics, authorization, identity, and transaction ownership explicit.
Uses FastAPI Security dependencies to combine declared scopes with current application authorization.
Separates fast rollback isolation from tests that must observe commits, multiple connections, or database concurrency.
Uses representative traffic and tail latency to find the real bottleneck and a safe operating range.
Binds typed configuration, understands property precedence, validates startup invariants, and keeps secrets outside source control.
Uses routers as feature-oriented HTTP modules while keeping application logic, composition, and contract ownership clear.
Organizes Django configuration without duplicating environments or leaking secrets into source code.
Carries an original version through an API update and turns an optimistic-lock failure into an explicit conflict workflow.
Chooses evidence based on whether latency comes from CPU execution, waiting, contention, or an external dependency.
Reviews correctness, boundaries, failure behavior, capacity, security, observability, delivery, and recovery through concrete evidence.
Coordinates admission stop, task cancellation or draining, resource closure, and bounded termination.
Tests asynchronous coordination through observable events and proves spawned tasks finish or cancel cleanly.
Uses Actuator for operational visibility while controlling endpoint exposure, access, detail, and network reachability.
Verifies provider signatures over raw bytes, enforces freshness, and makes repeated delivery idempotent.
Chooses immutable values and controlled mutable entities based on identity, concurrency, invariants, allocation cost, and update semantics.
Builds a story about improving code quality incrementally while still delivering product value.
Builds a story about improving team workflow with lightweight, useful process changes.