4 questions

IT and Governance Basics

A software team promotes a change from a development environment, into testing, and finally into production only after validation. What is the main purpose of maintaining these separate environments?

  • a.To increase the number of servers for its own sake
  • b.To avoid ever having to document changes
  • c.To validate changes safely before they affect live users
  • d.To make the project take longer intentionally

Separate development, test, and production environments let teams build and validate changes without risking the live system, catching defects before they reach users. This is a core governance and change-management practice, not a way to add servers or delay work.

IT and Governance Basics

A project will process customer personal information subject to data-privacy regulations. What should the project manager do regarding these requirements?

  • a.Incorporate the compliance requirements into scope, planning, and controls
  • b.Ignore them because they are not technical tasks
  • c.Delay considering them until after go-live
  • d.Assume the vendor is solely responsible with no oversight

Regulatory and data-privacy requirements are constraints that must be built into scope, planning, and controls from the start, because non-compliance carries legal and financial consequences. Deferring or outsourcing accountability without oversight exposes the organization to risk.

IT and Governance Basics

In a fixed-price contract, which party primarily bears the risk of cost overruns if the work takes more effort than expected?

  • a.The end users
  • b.The regulatory agency
  • c.The buyer
  • d.The seller (vendor)

In a fixed-price contract the price is set regardless of the seller's actual costs, so the seller bears the risk of overruns. In a time-and-materials or cost-reimbursable arrangement, more of that risk shifts to the buyer.

IT and Governance Basics

Which best describes the role of a change advisory board (CAB) in IT change management?

  • a.It writes all application source code for the project
  • b.It reviews and authorizes proposed changes, weighing benefit against risk
  • c.It sets the vendor's stock price
  • d.It replaces the need for testing environments

A change advisory board reviews proposed changes, assessing their benefit, risk, and impact, and authorizes or defers them to protect the stability of production systems. It does not write code, set prices, or eliminate the need for testing.

Report