Refer to the exhibit. The self-service Webex bot fails when many users try to interact with it simultaneously. Drag the code snippets from the left to the matching item numbers to complete the code for this high-load situation. <DragDrop items={["429","backoff","backoff","RETRIES","i"]} slots={[{"answer":"429","id":"item1"},{"answer":"RETRIES","id":"item2"},{"answer":"backoff","id":"item3"},{"answer":"backoff","id":"item4"},{"answer":"i","id":"item5"}]} template={"RETRIES = 6\ni = 0\nbackoff = 1\n\nwhile True:\n try:\n response = requests.request(*args, **kwargs)\n response.raise_for_status()\n return response\n except Exception as e:\n if (response.status_code != {{item1}}) or i == {{item2}}:\n return response\n\n time.sleep({{item3}})\n {{item4}} *= 2\n {{item5}} += 1"} reuse={true} explanation={"HTTP 429 indicates rate limiting, so it is the status that should be retried. The retry counter must be compared with RETRIES to stop after the configured maximum. Exponential backoff sleeps for the current backoff duration, doubles that duration before the next retry, and increments the attempt counter."} />