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.
24 results across 1 active filter
Page 1 of 1
Separates container instance reuse from concurrency guarantees and designs singleton services around stateless or safely coordinated state.
Uses class, bean, property, resource, and application conditions to provide explicit defaults without ambiguous registration.
Explains imported configuration classes, classpath and bean conditions, ordered defaults, back-off, and the condition report.
Explains ordered property sources, profile documents, environment overrides, command-line values, and evidence-driven diagnosis.
Explains container ownership, dependency declarations, bean creation, and why dependency injection is a specific form of inversion of control.
Explains proxy interception, target delegation, JDK versus class proxies, method limits, and the self-invocation boundary.
Traces the injection point, candidate type, registration path, conditions, profiles, generics, qualifiers, and package boundaries.
Treats a bean cycle as a design signal, explains constructor failure, and uses delayed resolution only for genuine lifecycle boundaries.
Uses supported properties, replacement beans, and narrow exclusions in that order, with condition-report and upgrade verification.
Explains why ordinary injection resolves once and chooses providers, factories, scoped proxies, or explicit parameters for shorter-lived dependencies.
Binds related values to typed configuration properties, applies validation constraints, and fails with actionable non-secret diagnostics.
Places the application class above owned components, uses capability-oriented packages, and keeps scanning and imports deliberate.
Preserves the root cause, separates binding, bean, port, classpath, migration, and external failures, and uses Boot's diagnostic reports.
Balances faster startup and unused-bean avoidance against delayed failures, first-request latency, memory growth, and readiness semantics.
Explains singleton, prototype, request, session, application, and WebSocket scopes as container lifecycle policies.
Explains configuration loading, bean-definition processing, dependency resolution, lifecycle, events, resources, and environment access.
Separates dependency bundles, tested version alignment, transitive dependencies, and runtime auto-configuration.
Separates Spring's application framework and container from Boot's opinionated startup, dependency, configuration, and operational conventions.
Walks from instantiation and dependency injection through post-processing, initialization callbacks, use, and supported destruction behavior.
Chooses stereotype scanning for owned application components and explicit factory methods for third-party types, construction policy, and visible composition.
Uses typed grouped binding and validation for application configuration while reserving @Value for small isolated expressions.
Prefers constructor injection for required dependencies while explaining the limited roles and costs of setter and field injection.
Chooses hooks by application readiness phase and keeps migrations, warm-up, listeners, and background resources owned and observable.
Uses profiles for named environment or deployment groups and focused conditions for feature or capability selection.