You are managing a software project. You are partway through the project, and your team has just delivered a preliminary version of part of the software. You are holding a weekly status meeting, when one of the team members points out that an important stakeholder is running into a problem with one of the features of the current software. The team member feels that there is a risk that the stakeholder will ask for a change in that feature, even though that change would be out of scope of the current release—and if the stakeholder requests that change, there is a high probability that the change control board would approve the change. What is the BEST action to take next?

A. Mitigate the risk by asking a team member to get familiar with the feature of the software that might be changed B. Schedule a meeting with the stakeholder to discuss the risk C. Add the risk to the risk register and gather information about its probability and impact D. Add the risk to the issue log and revisit it when there is more information