The customer’s request should be managed by assessing risks together with business value during prioritization because this is the best way to balance the customer’s expectations and the project’s feasibility. Agile projects are characterized by frequent delivery of value to the customer, but also by uncertainty and change. Therefore, risks should not be ignored or deferred, but rather integrated into the decision-making process. By assessing risks together with business value, the customer and the project team can identify the most valuable and viable features to deliver in each iteration, and also plan for risk responses and contingencies. The other options are not the best choices because they do not consider the impact of risks on the project’s success. Accepting risks as they decrease over a period of time (option A) may expose the project to unnecessary threats or missed opportunities, and may also violate the agile principle of responding to change. Creating a risk value profile to track the relative importance of risks (option B) may help to quantify and prioritize risks, but it does not address the customer’s request or the project’s value proposition. Logging and tracking risks separately as only business value is important (option C) may create a false sense of security and satisfaction, and may also neglect the agile principle of delivering working software. References: PMBOK Guide, 6th edition, pages 18-19, 686-687. PMP Questions page 437. PMP Practice Exam 1.