If a project’s risk register lists "high severity" for a risk with "low likelihood," no immediate action is needed.

A company purchasing cyber-insurance for data breaches is an example of transferring both financial and operational responsibilities.

Scope creep inherently leads to schedule risk but has no direct impact on cost risk.

Accepting a risk means the project team is no longer accountable for its consequences.

A vendor delivering faulty equipment falls under "External Risk" in the risk register.

Including a buffer in the project schedule is a form of risk mitigation.

New data privacy laws increasing compliance costs are classified as "Tech Changes" in financial risk sources.

A risk register’s "Progress on Action" column is critical for evaluating the effectiveness of mitigation strategies.

If a competitor launches a similar product, reallocating marketing funds to differentiate the project is a risk transfer strategy.

A project faces delays due to a critical developer’s sudden departure. Which action BEST demonstrates risk mitigation?

A company identifies a risk that new AI tools could make their software obsolete. Which strategy prioritizes long-term sustainability?

Which scenario BEST illustrates "Schedule Risk" impacting finances?

A project manager discovers a critical risk not listed in the register. What should they prioritize FIRST?

Which risk response is MOST appropriate for a low-impact, high-likelihood risk?

A project’s budget assumes stable currency rates, but geopolitical events cause fluctuations. This is an example of:

Why is "Severity" in a risk register calculated as a combination of likelihood and impact?

A company faces budget cuts mid-project. Which action aligns with risk acceptance?

Which factor is MOST critical when evaluating the success of a risk mitigation strategy?

A project uses outdated technology to save costs but risks compatibility issues. What is the PRIMARY trade-off?

The primary purpose of financial reporting in an IS project is to simply document all expenses incurred.

If a project's Cost Performance Index (CPI) is 0.95, it indicates that the project is currently delivering more value than the cost incurred.

Implementing a robust change control process primarily helps in avoiding technical problems within an IS project.

A high Expected Monetary Value (EMV) for a risk always means the project should avoid that risk at all costs.

Contingency reserves are primarily used to cover costs associated with identified risks that have known mitigation plans.

The Project Cash Flow Statement is primarily used to assess the project's overall profitability over a specific period.

Transferring a risk means completely eliminating its potential impact on the project.

Regular, transparent financial reporting primarily benefits external stakeholders like investors, not internal project teams.

If an IS project has a negative variance in its schedule performance, it necessarily means it also has a negative variance in its cost performance.

A risk register is a static document created at the beginning of an IS project and rarely updated.

An IS project manager is presenting to stakeholders. They need to justify why the project should continue despite some unforeseen technical challenges that might increase costs. Which core reason for financial reporting is most directly being addressed?

Which financial document is most frequently used by an IS project manager for real-time tracking of planned expenditures versus actual spending on items like labor, software, and hardware?

An IS project costing $150,000 is expected to generate $250,000 in benefits (e.g., cost savings, increased revenue) over its lifespan. What is the Return on Investment (ROI) for this project?

A specific task in an IS project was budgeted at $10,000. The actual cost incurred to complete this task was $12,000. What is the budget variance for this task?

During an IS project, a key stakeholder requests a significant new feature that was not in the original scope. Which best practice for accountability is most critical to apply immediately?

An IS project manager is concerned about having enough funds to pay a large vendor invoice due next month, even though the project is generally on budget. Which financial statement or report would provide the best insight into this specific concern?

To ensure financial discipline in an IS project, the project manager decides to hold weekly meetings to review the past week's spending against the plan and forecast for the upcoming week. This practice primarily supports which aspect of financial accountability?

An IS project has completed work valued at $50,000 (Earned Value). The actual cost incurred to complete this work is $60,000. What is the Cost Performance Index (CPI), and what does it indicate?

A company's IS project to implement a new CRM system went significantly over budget and was delayed by six months, leading to lost sales opportunities. This outcome most closely mirrors the negative impacts seen in which real-world example discussed?

What is the primary benefit of assigning a 'Responsible Party' to each identified financial risk in a project's risk register?

Risk identification is a one-time activity performed at the very beginning of a project and rarely revisited.

A risk with a high probability but low impact typically requires more immediate and extensive mitigation efforts than a risk with low probability but catastrophic impact.

Qualitative risk analysis assigns numerical values to risk probability and impact, allowing for statistical modeling.

The purpose of risk mitigation is to entirely eliminate all identified risks from a project.

Accepting a risk means the project team will develop a detailed contingency plan to be executed if the risk occurs.

A risk register serves as a central repository for documenting identified risks, their assessment, and planned responses.

Transferring a risk always involves purchasing insurance to cover potential financial losses.

Project managers should only focus on identifying negative risks, as positive risks (opportunities) do not require management.

A risk's likelihood and impact are the two primary factors used to prioritize it in a risk matrix.

Continuous risk monitoring is essential because new risks can emerge, and existing risks can change in severity or likelihood throughout the project lifecycle.

An IS project team is debating whether to use a new, cutting-edge technology. While it offers significant performance benefits, there's a high risk of integration issues with existing systems. If the team decides to proceed but allocates extra time and budget specifically for troubleshooting and potential rework related to this technology, which risk response strategy are they primarily applying?

During the risk assessment phase of a software development project, a project manager uses a risk matrix to plot identified risks based on their likelihood of occurrence and the severity of their impact. What is the primary analytical benefit of this approach?

A critical software module is being developed by a third-party vendor. To address the risk of vendor default or significant delays, the project manager includes a penalty clause in the contract for late delivery and requires a performance bond. Which risk mitigation strategy is being implemented?

An IS project relies heavily on a specialized database system. A known risk is that the sole expert on this system might leave the company. To mitigate this, the project manager initiates cross-training for two other team members on the database. This action primarily addresses which aspect of the risk?

A project manager identifies a potential risk: a minor, non-critical bug in a third-party library that rarely manifests and has negligible impact on system performance. After discussion, the team decides not to allocate resources to fix it unless it becomes a recurring problem. Which risk response strategy does this decision represent?

Your project's core functionality relies on a new, unproven API. To assess the actual technical risk, your team builds a small prototype solely to test the API's compatibility and performance before full-scale development. This proactive measure exemplifies which stage of risk management?

A project is facing a risk of budget overrun due to unforeseen material cost increases. To analyze the potential financial impact more thoroughly, the project manager uses Monte Carlo simulation, which generates a range of possible cost outcomes. This is an example of what type of risk analysis?

A key project deliverable is a new customer-facing mobile application. There's an identified risk that user adoption might be lower than expecteTo address this, the project manager plans to launch a beta testing program with a select group of users and gather extensive feedback to refine the UI/UX. This is an example of what kind of risk response?

Why is it critical for project managers to continuously monitor risks, even after mitigation plans are in place?

An IS project has identified a high-impact, high-likelihood risk that a critical development tool might become obsolete mid-project, disrupting the workflow significantly. The project manager decides to purchase a license for an alternative tool and train a subset of the team on it immediately. This action represents which type of risk response and why?