Quiz
Retry Wrappers vs. Resource Timeouts
Understanding how URLSession's resource timeout interacts with a per-attempt retry loop.
Your resilient client sets configuration.timeoutIntervalForResource = 30 and wraps requests in a retry loop that creates a fresh URLSessionDataTask for each of up to 3 attempts (with exponential backoff between them). Ignoring the backoff sleeps, what is the maximum wall-clock time the network operations alone can consume across all attempts, and why?