If possible, high-risk requirements are scheduled in early iterations. This allows them to be dealt with, and possibly avoided, in the project because the risks were identified and scheduled earlier in the project’s timeline rather than
later. The other responses are incorrect because the creation of a new requirement doesn’t address the risk event; changing the requirement will not make the project successful; if high-risk requirements are saved for the end of a
project, the risk impact could be more significant than if they were earlier because it can affect work that has already been done.