Loading
Pick a focused question that fits your time, stack, and interview goal.
618 drills fit a 20-minute session. Closest fits first.
Page 16 of 26
Choose between ConcurrentDictionary and explicit locks when managing concurrent in-memory data.
Explain what ConfigureAwait(false) does, why it mattered historically, and how to reason about it in ASP.NET Core and library code.
Keeps images environment-neutral while handling configuration precedence, secret delivery, rotation, and startup validation safely.
Separates ephemeral instance files from durable data and sends logs, uploads, caches, and diagnostics to storage with explicit lifecycle ownership.
Uses immutable image identity, controlled promotion, registry security, and deliberate base-image rebuilding instead of mutable latest tags.
Explains bind addresses, published ports, internal DNS, service identity, and why localhost changes meaning across container boundaries.
Distinguishes request and response media types and designs predictable negotiation, rejection, documentation, and caching behavior.
Compare endpoint styles in real services, including organization, conventions, testing, filters, and OpenAPI behavior.
Explains deployment markers, version telemetry, feature-flag state, commit traceability, and incident diagnosis after releases.
Explains browser same-origin enforcement, preflight requests, credentials, middleware behavior, and why CORS is not authorization.
Explains database constraints versus application validation with practical .NET data-access examples and production trade-offs.
Distinguishes instants, local calendar values, offsets, and named time zones so APIs and persistence survive daylight-saving and locale boundaries.
Explains how to decide if caching is the right fix for a slow API endpoint instead of query tuning or contract changes.
Explains how to design DTOs, response shapes, UI needs, API compatibility, and frontend/backend ownership for a feature.
Distinguishes callable delegate values from publisher-controlled events and makes subscription lifetime explicit.
Keeps business policy independent from infrastructure while centralizing concrete dependency assembly at the application edge.
Explains the difference between deploying code and releasing functionality to users using feature flags.
Explains alert design based on user-impact symptoms, SLOs, burn rate, thresholds, and avoiding noisy cause-only alerts.
Explains useful message metadata for tracing, idempotency, ownership, versioning, and support diagnostics.
Explains reset-token generation, hashing, expiration, generic responses, session revocation, and abuse controls.
Explains password verification, hashing, throttling, generic errors, lockout, and safe login telemetry.
Explains cache-key scope for tenant, user, role, locale, filters, response version, and security-sensitive reads.
Explains how client-side validation, server-side validation, DTOs, domain rules, and user feedback work together.
Explains health checks that prove an API can serve traffic without becoming fragile dependency probes.