106.
Which of the following is not a recognized risk response strategy in project
management?
a. Developing contingency plans.
b. Avoiding the risk altogether.
c. Ignoring the risk and hoping for the best.
d. Transferring the risk to a third party.
107. The offshore wind farm project team has logged multiple risks tied to shifting
regulatory reviews. Some permits must be secured in the next three months, while others
are required much later. During qualitative risk analysis, they want their probability-
impact matrix to highlight which regulatory threats need earlier attention so mitigation
funds can be staged promptly. What should they add to their evaluation?
a. Add an earned value schedule performance factor
b. Generate a Monte Carlo schedule dispersion metric covering regulatory milestones across the
entire program lifespan
c. Apply a stakeholder salience index
d. Include a risk urgency rating
108. You are managing a large-scale project that involves multiple vendors across the
globe. During risk planning, you realize the potential risks that might arise from vendor
management, including language barriers, cultural differences, and time zones. What
should be your approach to address these risks?
a. Address these issues as they occur during the project's lifecycle.
b. Ignore the risks as they are negligible.
c. Include mitigation strategies such as using translation services, cultural sensitivity trainings,
and coordination of working hours in the risk management plan.
d. Park the risk and deal with it if it arises.
109. A high-priority risk has been identified in your project, but the probability of it
occurring is less than 2%. How should you handle this risk?
a. Ask a team member to mitigate the risk.
b. Transfer the risk to another project.
c. Ignore the risk since the probability is low.
d. Document the risk and monitor it throughout the project.
110. You are reviewing the risk register and find that some risks no longer apply to the
project. What should you do?
a. Keep these risks in the register as a warning for future projects.
b. Categorize these risks as closed in the risk register and leave a note explaining the reason.
c. Remove these risks from the register entirely.
d. Move these risks to the bottom of the register.