Loading
Pick a focused question that fits your time, stack, and interview goal.
102 results across 1 active filter
Page 1 of 5
Explain API behavior when data and operations cross services with separate data ownership.
Design and debug rate limiting while protecting the API without blocking legitimate users and integrations.
Separates identity establishment from permission decisions and applies ASP.NET Core schemes, policies, tenant boundaries, ownership checks, and correct challenge or forbid behavior.
Explains dynamic filters and SQL injection risk with practical .NET data-access examples and production trade-offs.
Maps business invariants and stale-data tolerance to strong or eventual consistency, explicit failure behavior, reconciliation, and user-visible state.
Explains composite index column order with practical .NET data-access examples and production trade-offs.
Explains EF Core connection resiliency and retries with practical .NET data-access examples and production trade-offs.
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 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.
Designs an async export flow for large reports without blocking API requests or exhausting database and memory resources.
Designs dashboard APIs with precomputed metrics, freshness rules, query cost control, and drill-down support.
Designs explicit workflow states, allowed transitions, guard rules, audit history, idempotency, and operational repair paths.
Design API error handling across validation errors, conflicts, auth failures, not-found responses, and unexpected exceptions.
Designs feature flag storage, targeting, safe defaults, auditability, and rollout observability for backend behavior.
Designs tenant isolation across API, data, cache, background jobs, search, and admin access.
Designs an activity feed with event capture, fan-out strategy, pagination, privacy, and read performance.
Introduces API versions only for unavoidable breaks, with explicit routing, versioned documentation, migration support, telemetry, deprecation, and removal criteria.
Designs immutable audit records for sensitive administrative changes with useful before/after context and safe retention.
Designs a checkout or order creation flow that survives client retries without duplicate orders, payments, or messages.