nerdexam
CompTIA

PK0-004 · Question #29

A project team member highlights to the project manager that expensive licensing for critical software in use across the project may expire before the completion of the project. Which of the…

The correct answer is A. Place a risk on the risk register and arrange a risk review with the appropriate stakeholders to. A potential software licensing expiration is a threat to project delivery and must be formally logged on the risk register and reviewed with stakeholders before any response action is taken.

Tools and documentation

Question

A project team member highlights to the project manager that expensive licensing for critical software in use across the project may expire before the completion of the project. Which of the following would the project manager MOST likely do?

Options

  • APlace a risk on the risk register and arrange a risk review with the appropriate stakeholders to
  • BRaise a purchase order to purchase the licensing and ask the team member to install it.
  • CAmend the project scope and raise a project change request to obtain approval of the
  • DAmend the project schedule and work breakdown structures to remove the use of the

How the community answered

(23 responses)
  • A
    78% (18)
  • B
    4% (1)
  • C
    13% (3)
  • D
    4% (1)

Why each option

A potential software licensing expiration is a threat to project delivery and must be formally logged on the risk register and reviewed with stakeholders before any response action is taken.

APlace a risk on the risk register and arrange a risk review with the appropriate stakeholders toCorrect

Placing the issue on the risk register formalizes the threat so it can be tracked, assigned an owner, and evaluated for probability and impact. Arranging a risk review with appropriate stakeholders follows the risk management process and ensures the response - whether renewal, substitution, or schedule adjustment - is approved and coordinated rather than unilateral.

BRaise a purchase order to purchase the licensing and ask the team member to install it.

Raising a purchase order without first completing a risk review and obtaining proper approvals bypasses governance and assumes renewal is the correct response without stakeholder input.

CAmend the project scope and raise a project change request to obtain approval of the

Amending project scope addresses what is delivered, not how a risk to an existing dependency is managed, making it the wrong process for a licensing threat.

DAmend the project schedule and work breakdown structures to remove the use of the

Removing the software from the WBS eliminates project capability as a first action without evaluating other risk responses such as renewal or substitution.

Concept tested: Risk identification and risk register documentation

Topics

#risk register#risk management#software licensing#risk review

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PK0-004 Practice