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.
1225 drills fit a 20-minute session. Closest fits first.
Page 21 of 52
Handles token-budget overflow and incomplete generation through explicit prioritization, rejection, retrieval, summarization, continuation, and validation.
Separates provider refusals, safety blocks, token truncation, transport failure, and valid domain abstention.
Explains transient database errors, retry strategy, EF Core execution strategy, idempotency, timeouts, and avoiding retry storms.
Uses Resource Server and JwtDecoder to validate signature, issuer, audience, time, algorithms, key rotation, and authority mapping.
Chooses stable entity equality across transient, managed, detached, and proxied instances without breaking hash collections.
Treats interruption as a cooperative request, preserves interrupt status, defines cleanup, and separates cancellation signals from guaranteed task termination.
Builds outbound resilience from deadlines and operation safety, then adds bounded retry, circuit, and concurrency controls with telemetry.
Transforms conversational requests into bounded search inputs while preserving user intent, constraints, and traceability.
Balances retrieval precision, answer completeness, document structure, overlap, metadata, and model input limits.
Chooses a model from task-specific evaluation, operating constraints, safety, latency, cost, context, modality, and provider requirements.
Chooses browser storage by server transport, lifetime, capacity, query needs, sensitivity, synchronization, and offline behavior.
Builds a small, task-relevant, typed toolset with clear semantics rather than exposing an entire internal API surface.
Selects relevant, trustworthy, and budgeted context instead of treating the context window as storage.
Turns a product outcome into observable quality, safety, and operational criteria before selecting convenient scores.
Defines a narrow capability with a clear name, decision-oriented description, typed inputs, and safe result semantics.
Designs a narrow, typed, provider-supported schema that communicates the real downstream contract.
Balances route ownership, initial bundle cost, likely navigation, authorization, and measurable user experience.
Covers deployment logs, startup failures, runtime stack, app settings, missing files, Key Vault references, and post-deployment diagnosis.
Moves from user-visible latency to route, dependency, database, executor, JVM, and change evidence before selecting a fix.
Preserves the root cause, separates binding, bean, port, classpath, migration, and external failures, and uses Boot's diagnostic reports.
Uses Hikari metrics, thread evidence, database activity, transaction scope, and query behavior to separate leaks from slow or excessive work.
Triages heap, Metaspace, native, direct-buffer, thread, and container exhaustion using preserved evidence before changing limits.
Separates server request capacity from application executor capacity and finds blocking, queueing, rejection, or downstream causes.
Diagnoses queued work, blocked workers, nested submissions, common-pool contention, downstream waits, and misleading CPU symptoms.