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.
298 results across 1 active filter
Page 8 of 13
Covers queue-backed work, idempotency, retries, visibility timeout, poison messages, progress tracking, and choosing Storage Queues or Service Bus.
Explains safe migration strategy for Azure-hosted .NET APIs, including expand-contract changes, locking risk, rollback, and deployment order.
Explains correlation IDs, distributed tracing, dependency telemetry, message boundaries, and logs across App Service, queues, and downstream APIs.
Explains how IHttpClientFactory separates short-lived clients from pooled handlers and how concurrency, DNS, resilience, and DI lifetimes still require judgment.
Validates size and signature, writes under a generated storage key, and keeps untrusted files outside the public web root.
Explains upload UX, API boundaries, validation, progress, storage, scanning, failure handling, and safe download behavior.
Validates a bounded command set completely before applying all updates in one SaveChanges transaction.
Builds a bounded readiness check for one required dependency while keeping liveness independent and responses non-sensitive.
Stores an idempotency key, request hash, and response in the same transaction as the created resource.
Implements a small in-memory fixed-window rate limiter with per-key counters.
Implements a small LRU cache using a dictionary plus linked list for O(1) get and put.
Explains debounce, cancellation, stale-response protection, loading indicators, and backend query safety for search UI.
Processes a large import in chunks with fresh DbContexts, idempotent keys, cancellation, and bounded tracker growth.
Verifies the exact request bytes, rejects stale signatures, deduplicates event ids, and queues processing durably.
Uses the real ASP.NET Core pipeline while replacing only environment-specific boundaries deliberately.
Explains delete-on-write, versioned keys, event-driven invalidation, and the race conditions around cache freshness.
Explains refetching, targeted invalidation, stale data, optimistic updates, server truth, and user feedback after mutations.
Investigates a growing-data EF Core slowdown through one correlated request, generated SQL, representative parameters, execution plan, waits, query shape, measured repair, and guarded rollout.
Explains how to triage post-release 500 errors using deployment correlation, logs, traces, feature flags, and rollback safety.
Explains how to diagnose 401/403 spikes across token validation, identity provider issues, clock skew, deployment changes, and abuse.
Compares rollback, reset, schema, database, and tenant isolation without hiding transaction or parallelism limits.
Uses per-dependency concurrency limits, queues, pools, and workload partitions to stop one failing path from exhausting the whole API.
Explains transaction isolation levels with practical .NET data-access examples and production trade-offs.
Designs a reliable CI test system with fast feedback, deliberate test stages, bounded parallelism, visible flakiness, useful diagnostics, and clear ownership.