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 51 of 52
Defines object-oriented programming clearly, then connects objects, responsibilities, and the main OOP mechanisms to practical C# design.
Defines OOP directly and connects Java objects, responsibilities, state, behavior, and collaboration to a practical design.
Distinguishes a Java type definition from a concrete runtime instance and keeps identity, state, and polymorphism tied to the question.
Separates deployment-level Django configuration from cohesive application features and explains the app registry.
Clarifies the difference between objects being retained accidentally and code simply allocating too much temporary memory.
Separates overlapping I/O work from simultaneous execution across processing resources.
Separates proving an identity from deciding whether that identity may perform a specific action on a resource.
Distinguishes a type's natural order from external, reusable sort strategies and connects comparison consistency to sorted collections.
Separates managing overlapping tasks from executing work simultaneously and connects both to Java backend design.
Separates view-oriented controller return handling from class-level response-body semantics without implying different request mapping.
Separates the persistence specification, its ORM implementation, and Spring's repository abstraction while keeping generated SQL visible.
Separates Spring's application framework and container from Boot's opinionated startup, dependency, configuration, and operational conventions.
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.
Covers custom domains, TLS, HTTPS, allowed hosts, CORS boundaries, and production-facing endpoint hygiene for App Service APIs.
Explains a practical CI/CD pipeline for .NET applications from code change to deployment verification.
Explains string immutability, concatenation behavior, and pragmatic use of StringBuilder in .NET.
Distinguishes object identity from value equality and prevents fragile code based on interning or implementation accidents.
Distinguishes reference identity from logical equality and shows how nulls, strings, enums, and domain values affect the choice.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.
Distinguishes render-driving state from instance-local mutable values and DOM references.
Prioritizes explicit normalization, strict equality, object identity, nullish handling, and NaN over coercion puzzles.
Explain why async void is usually dangerous outside event handlers and how exceptions behave differently.
Explains returning EF entities from APIs with practical .NET data-access examples and production trade-offs.