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 6 of 13
Designs membership, role changes, removal, ownership transfer, and permission updates without weakening tenant boundaries.
Uses unique namespaces and correctly scoped fixtures so parallel tests improve speed without creating collisions.
Designs an invitation workflow with token security, expiry, membership creation, email delivery, and replay-safe onboarding.
Designs a settings service with defaults, validation, scoped preferences, caching, and safe rollout of new settings.
Explains hot-key behavior, traffic concentration, partition pressure, payload size, and mitigation options.
Treats flakiness as an observable defect in timing, state, order, infrastructure, or product behavior.
Explains a telemetry-driven path from slow endpoint symptoms to database, cache, dependency, CPU, or payload root cause.
Separates a live blocking chain from a deadlock victim, gathers the right database evidence, stabilizes the incident, and fixes lock duration or access order.
Pairs a bounded isolated reproduction with telemetry and a disposal fix for leaked database connections.
Uses instance state, termination reasons, events, logs, configuration, probes, and resource evidence to distinguish common container startup failures.
Decide whether Azure SQL errors are transient platform faults or a real application/query regression.
Explains command messages versus event messages and how ownership changes their design.
Builds deterministic images efficiently by controlling context, restore layers, dependency inputs, and cache invalidation.
Uses Compose for reproducible local dependencies while preserving fast inner loops, realistic readiness, and clear differences from production orchestration.
Investigate and fix an API where client retries create duplicate orders, payments, or records.
Maps an HTTP ETag precondition to EF Core rowversion and returns 412 when the representation is stale.
Implements representation-aware ETags and conditional GETs correctly, including validators, 304 metadata, authorization, cache variation, generation cost, and tests.
Performs a set-based bulk update without loading session entities into the change tracker.
Explains how consumer groups share event-stream work and how offset commits affect duplicate or lost processing.
Explains when stale cache reads are acceptable, when they are dangerous, and how to make freshness visible.
Explains why exactly-once claims do not remove the need for idempotent side effects and consistency boundaries.
Explains what CORS controls, what it does not protect, and why APIs still need authentication and authorization.
Explains why cached authorization decisions are risky and how to bound or invalidate permission-related cache safely.
Frames a vague system-design problem with explicit flows, constraints, scale estimates, and measurable quality targets before selecting components.