Loading
Pick a focused question that fits your time, stack, and interview goal.
618 drills fit a 20-minute session. Closest fits first.
Page 10 of 26
Predicts when an in-memory LINQ pipeline runs and prevents repeated work, changed results, and hidden side effects.
Uses declarative infrastructure, reviewed plans, environment parameters, protected deployment identities, state management, and drift control without hiding operational risk.
Explains when filters, sorting, pagination, and selection belong in search parameters and how to keep navigation predictable.
Explains operational signals for queue-backed systems and how to respond when consumers fall behind.
Turns a useful Aspire development model into explicit production infrastructure without treating the local AppHost as the runtime platform.
Predicts how the built-in container resolves repeated service registrations and chooses explicit selection without service-location logic.
Uses nullable annotations as a compile-time contract while still validating untrusted and legacy runtime inputs.
Uses type, property, relational, and list patterns to express decisions while keeping null and unhandled cases explicit.
Explain why request cancellation should flow into EF Core queries and where it does or does not help.
Combines ThreadPool counters, repeated stack snapshots, and wait-event traces to distinguish blocked workers from CPU or dependency pressure.
Compare public and internal APIs in terms of compatibility, documentation, security, support, and evolution speed.
Builds a story about challenging a risky requirement while staying constructive and product-oriented.
Investigate and fix a race condition caused by shared mutable state in a .NET service.
Explains when production approvals are useful and how to avoid turning them into empty bureaucracy.
Explains how to choose rollback, swap-back, hotfix, or roll-forward after a failed Azure App Service deployment.
Explains how multiple worker instances share queue work and what limits safe scaling.
Builds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.
Builds a story about taking responsibility for a production bug, mitigating impact, and preventing recurrence.
Designs integration tests for authentication, capabilities, ownership, account status, and cross-tenant isolation without bypassing the real authorization pipeline.
Tests durable background processing across duplicate delivery, retries, acknowledgement timing, crashes, poison messages, and observable completion.
Explains how to diagnose and mitigate a downstream dependency slowing the API through timeouts, retries, and degraded behavior.
Explains how to investigate queue age, backlog, worker health, poison messages, dependency failures, and safe catch-up.
Use correlation IDs, structured logs, and logging scopes to make API failures traceable in production.
Explains how query tags, request correlation, and telemetry help connect slow SQL back to code paths.