Loading
Pick a focused question that fits your time, stack, and interview goal.
102 results across 1 active filter
Page 4 of 5
Covers chunking, bounded concurrency, scoped dependencies, progress, retries, and avoiding full-dataset memory spikes.
Gives a practical incident flow for memory growth using metrics, traffic correlation, heap evidence, and safe mitigation.
Explains transaction isolation levels with practical .NET data-access examples and production trade-offs.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Explains multi-tenant data filtering with practical .NET data-access examples and production trade-offs.
Explains offset versus cursor pagination with practical .NET data-access examples and production trade-offs.
Designs an EF Core optimistic-concurrency contract around tokens, conflict policy, HTTP semantics, merge behavior, and real relational tests.
Uses a transactional outbox to make a local state change durably publishable while accepting at-least-once delivery and operating the backlog safely.
Chooses between EF Core complex types, owned entities, and regular entities from value semantics, identity, ownership, querying, and storage needs.
Uses RFC 9457 Problem Details as a stable, safe error contract with documented problem types, actionable extensions, and centralized ASP.NET mapping.
Compare public and internal APIs in terms of compatibility, documentation, security, support, and evolution speed.
Fits database command timeouts into endpoint latency budgets while diagnosing slow SQL, blocking, pool pressure, and uncertain write outcomes.
Reviews a proposed response-field rename by finding consumers, classifying the break, choosing a migration path, and proving rollout and removal are safe.
Places identity, optional selection controls, command representations, headers, and files in predictable HTTP locations while accounting for security, caching, limits, and model binding.
Separates identity issuance, untrusted client behavior, API authorization, tenant isolation, resource checks, and token-handling responsibilities.
Builds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.
Explains EF Core shadow properties for audit or infrastructure columns with practical .NET data-access examples and production trade-offs.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.
Diagnose an ASP.NET Core API that becomes slow because request threads are blocked or exhausted.
Use correlation IDs, structured logs, and logging scopes to make API failures traceable in production.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.
Explains read models for complex API screens with practical .NET data-access examples and production trade-offs.
Explains why memory diagnostics need access control, retention limits, and careful handling of secrets and user data.
Practices incident response after an OOM: restore service, collect evidence, identify trigger, and prevent recurrence.