Loading
Pick a focused question that fits your time, stack, and interview goal.
167 results across 1 active filter
Page 2 of 7
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.
Applies CQRS proportionally, separating model responsibilities without assuming separate databases, messaging, or event sourcing.
Creates and disposes explicit service scopes for hosted, queued, and parallel work without sharing scoped dependencies across operations.
Explains database constraints versus application validation with practical .NET data-access examples and production trade-offs.
Uses deadlock evidence to correct EF Core transaction scope, query plans, and resource order, with bounded retries only for repeat-safe victims.
Debugs ASP.NET Core authentication challenges and authorization forbids across schemes, token validation, policies, claims, tenants, and resource checks.
Handle a production support case where logs exist but related request events cannot be connected.
Explains a practical debugging path across browser, Next.js layer, API, logs, database, and deployment changes.
Investigate an endpoint accepting invalid data or returning inconsistent validation errors.
Explains database connection pool exhaustion with practical .NET data-access examples and production trade-offs.
Explains high database CPU after an API change with practical .NET data-access examples and production trade-offs.
Define logs, metrics, traces, alerts, and dashboards needed to operate an ASP.NET Core API in production.
Explains how to design DTOs, response shapes, UI needs, API compatibility, and frontend/backend ownership for a feature.
Distinguishes explicit dependency injection from runtime service lookup and identifies the narrow framework boundaries where scoped resolution is legitimate.
Keeps business policy independent from infrastructure while centralizing concrete dependency assembly at the application edge.
Design API error handling across validation errors, conflicts, auth failures, not-found responses, and unexpected exceptions.
Introduces API versions only for unavoidable breaks, with explicit routing, versioned documentation, migration support, telemetry, deprecation, and removal criteria.
Makes POST retries return one durable business outcome by combining scoped keys, request identity, atomic ownership, response replay, and reconciliation.
Explains soft delete in EF Core APIs with practical .NET data-access examples and production trade-offs.
Places contract, use-case, domain, authorization, and database validation at the boundaries that can enforce each rule consistently.
Explains how client-side validation, server-side validation, DTOs, domain rules, and user feedback work together.
Explains list/detail API boundaries, route state, prefetching, selected item behavior, and avoiding over-fetching.
Design list endpoints with pagination, filtering, sorting, limits, and database-aware performance behavior.