A model-backed API frequently runs longer than the browser request budget. Users must retrieve completed results later. Which architecture best meets the requirement?

1. Accept a durable job, return an identifier, process asynchronously, and expose authorized job status and results.
2. Keep the only job state in the open HTTP connection.
3. Publish every completed result under a public sequential URL.
4. Restart generation from scratch whenever the user refreshes.