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.
1345 results
Page 49 of 57
Separates what a model can perform from whether the complete AI feature behaves dependably under real inputs, failures, and constraints.
Separates logging a user into an application, obtaining tokens for outbound calls, and validating access tokens on an API.
Distinguishes fewer network round trips from atomic execution and chooses the smallest correct Redis primitive.
Separates Spring's application framework and container from Boot's opinionated startup, dependency, configuration, and operational conventions.
Separates transaction-phase callbacks inside one process from durable database-backed publication across process failure.
Separates Jakarta cascaded validation, Spring validation groups, and modern MVC method validation without relying on outdated controller advice.
Distinguishes the synchronous WSGI request contract from ASGI's asynchronous, multi-event application contract.
Walks from instantiation and dependency injection through post-processing, initialization callbacks, use, and supported destruction behavior.
Explains N+1 queries in EF Core with practical .NET data-access examples and production trade-offs.
Explains how Java compiles generic code and connects erasure to runtime checks, reflection limits, overloads, arrays, and bridge methods.
Explains heap, per-thread stacks, Metaspace, code cache, and native memory through the failures and evidence they produce.
Explains how GC roots retain reachable object graphs and turns heap evidence into a concrete ownership fix for static state, events, closures, queues, and caches.
Distinguishes model-directed execution from explicit application control and explains when each is appropriate.
Connects stable hashing and equality to dictionary and set correctness, including custom types and mutable-key failures.
Treats a production prompt as a versioned request contract containing instructions, context, output expectations, and application-owned controls.
Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.
Designs index records that support filtering, authorization, freshness, citations, diagnosis, and safe reprocessing.
Applies parsing, schema and domain validation, authorization, confirmation, idempotency, limits, and audit before execution.
Explains Aspire as a code-first application model and developer experience without confusing it with a production runtime or architecture style.
Combines Spring Boot signals into an operator-focused baseline for service health, dependencies, capacity, releases, and actionable alerts.
Explains Next.js 16 explicit caching, static shells, dynamic islands, cache keys, and adoption boundaries.
Defines MCP as a client-host-server protocol for discovering and using tools, resources, and prompts without confusing interoperability with safety.
Covers custom domains, TLS, HTTPS, allowed hosts, CORS boundaries, and production-facing endpoint hygiene for App Service APIs.
Places provider guardrails as one configurable defense while preserving application authorization, validation, testing, and incident evidence.