During iteration planning, the team identifies a new technical risk: the third-party authentication service they planned to integrate may not handle the expected user load during peak usage periods, potentially causing system failures. This could impact the upcoming release. What should the project manager do FIRST?

Add the risk to the risk register and schedule detailed analysis and planning for the next iteration

Remove the authentication service integration from the current iteration to avoid the risk entirely

Conduct a technical spike to test the authentication service's capacity limits and identify potential solutions or alternatives

Escalate the risk to the product owner for a scope and priority decision