23. Why should fallback usage be monitored?
- Fallbacks are always errors
- A fallback can hide a long-running failure, such as stale data being served for days
- Fallbacks increase CPU usage dramatically
- Fallbacks cannot be logged
Show answer
Answer: A fallback can hide a long-running failure, such as stale data being served for days
Graceful degradation keeps users happy but must not let failures go unnoticed.
Lesson: Observing Resilience Patterns
25. Which combination best protects a caller from a dependency that suddenly becomes very slow?
- Longer timeouts and more retries
- Removing all timeouts
- Caching the dependency's errors forever
- Short timeouts, a circuit breaker with slow-call detection and a bulkhead
Show answer
Answer: Short timeouts, a circuit breaker with slow-call detection and a bulkhead
Timeouts bound waiting, the breaker stops calls to a slow dependency and the bulkhead caps resource use.
Lesson: Revision and Interview Questions