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.
1345 results
Page 40 of 57
Places identity, optional selection controls, command representations, headers, and files in predictable HTTP locations while accounting for security, caching, limits, and model binding.
Combines quality, reliability, cost, security, privacy, and recovery evidence into a realistic launch and incident game day.
Fetches multiple URLs with bounded concurrency, per-request and batch deadlines, cancellation, ordered results, and executor cleanup.
Reduces container privileges through non-root execution, minimal images, controlled filesystems, and explicit capability requirements.
Explains how callers use one contract while runtime dispatch selects implementation, then connects that mechanism to extensible behavior.
Explains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.
Persists business state and durable publication intent atomically, leaving broker delivery to an idempotent retrying publisher.
Persists business state and durable publication intent atomically while leaving broker delivery to an idempotent publisher.
Persists domain state and its outbox message in one SaveChanges transaction without publishing inside the request transaction.
Explains how multiple worker instances share queue work and what limits safe scaling.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.
Explains safe handling of secrets and environment-specific configuration in CI/CD pipelines.
Protects source, dependencies, workflows, build identities, runners, artifacts, and deployment verification while preserving traceability and patch response.
Separates identity issuance, untrusted client behavior, API authorization, tenant isolation, resource checks, and token-handling responsibilities.
Uses separate models where they protect contracts, invariants, or storage evolution while avoiding repetitive mapping with no boundary value.
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Explains cached value serialization, schema versioning, deploy compatibility, and safe handling of old payloads.
Explains Next.js server/client component boundaries, interactivity, data access, serialization, and bundle impact.
Chooses event retention and compaction from consumer outage, replay, rebuild, audit, and disaster-recovery requirements rather than storage cost alone.
Sets bounded timeout and deadline policies across callers, APIs, databases, and external services without hiding unknown outcomes.
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.
Explains the output shape of core LINQ transformations and uses them without hiding empty groups, duplicate keys, or excessive buffering.
Shapes an API list from its contract and cardinality, projecting only required values while preserving authorization, stable pagination, bounded nesting, index support, and measurable query cost.