A partner API returns a continuation token and sometimes responds with HTTP 429 and Retry-After. A daily ingestion job must retrieve the complete authorized dataset and resume interrupted runs. Which behaviors should the client implement? Select 2 answers.

1. Honor Retry-After and use bounded retry behavior for retryable responses, with an idempotent destination.
2. Ignore continuation tokens because a successful HTTP response always contains the entire dataset.
3. Retry every response immediately without a bound, including authentication failures.
4. Follow continuation tokens until the API indicates completion and persist progress only after safely processing the corresponding data.
5. Treat HTTP 429 as an empty successful page and mark the entire dataset complete.