TOPIC
Distributed systems
These are the same questions found in the library, grouped here by the capability each one mainly examines.
55 questions
Questions 51–55 of 55 on this page.
A · Professional problem solving and implementation3
- An AI assistant repeatedly calls search, databases, and external APIs for a small share of requests, making latency and cost far higher than average. How would you design per-task budgets, stop conditions, idempotency, and auditable execution records?
- After a dependency slows down, several callers increase retries at the same time; traffic doubles and the outage spreads. How would you design retry budgets, backoff, jitter, and cross-service coordination?
- Multiple regions accept the same request independently. Idempotency records have a TTL and machine clocks may differ by seconds. How would you prevent duplicate writes at expiry boundaries?
No questions in this section match your target. ·
B · Business understanding and domain modeling2
- A customer-ownership field in historical events is wrong and must be corrected in bulk to recompute downstream metrics; the same events may also trigger notifications and partner callbacks. How would you separate data recomputation from side-effect replay?
- An early consumer deduplicates only by order ID, but one order can have several legitimate changes; the key must include an event version and historical messages need replay. How would you migrate keys without losing or duplicating processing?
No questions in this section match your target. ·