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.
7 results across 1 active filter
Page 1 of 1
Diagnose a growing queue backlog in an Azure-based background processing system.
Traces duplicate side effects across message delivery, lock ownership, settlement, durable job state, and external idempotency, then repairs affected users safely.
Diagnose missing trace continuity when an API enqueues work processed by an Azure worker.
Investigate messages that repeatedly fail and move to a poison queue or dead-letter queue.
Covers queue-backed work, idempotency, retries, visibility timeout, poison messages, progress tracking, and choosing Storage Queues or Service Bus.
Compares App Service WebJobs and Azure Functions for queue processing, scheduled tasks, scaling, deployment ownership, and operational isolation.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.