Technical interview questions and drills

22 results across 1 active filter

Page 1 of 1

Showing the Message Queues & Events curriculum. Technology tags describe each drill's actual implementation context; shared drills can belong to more than one track.

Architecture scenarioHard~12 min

Choose a partition key for an event stream

Explains partition key selection for ordering, load distribution, hot keys, and consumer scalability.

In Message Queues & Events

Azure Service BusKafka

Comparison questionEasy

Drills

Choose a partition key for an event stream

Compare queues and topics for backend messaging

Design a message envelope with correlation metadata

Design for at-least-once delivery with idempotent handlers

Design for broker outage and backpressure

Design retry, backoff, and poison message policy

Design safe event replay and backfill

Distinguish commands and events in message-driven systems

Explain consumer groups and offset commits

Explain the exactly-once messaging caveat

Handle message locks and visibility timeouts for long work

Keep message payloads small with the claim-check pattern

Monitor queue depth, message age, and consumer lag

Move work from the request thread to a queue

Preserve ordering only where it is actually needed

Reconcile an ambiguous distributed workflow

Recover safely from a dead-letter queue

Scale queue processing with competing consumers

Set event retention and compaction for consumer recovery

Use delayed and scheduled messages

Use the inbox pattern to deduplicate consumed messages

Version event schemas without breaking consumers