CAPM Practice: Determine how to gather requirements

A requirements baseline is the approved requirements at a specific point (typically after stakeholder sign-off). It enables change management — proposed changes are measured against the baseline to assess impact and maintain control of scope.

**Why not A:** Technical infrastructure and security requirements are a category of requirements content, not a definition of a baseline. A baseline is about governance and timing — the formal approval state of a requirements set — not about the subject matter of those requirements.

**Why not B:** A baseline has nothing to do with a minimum count of requirements. Establishing a baseline is a formal change-control action that freezes an approved version for comparison, regardless of how many requirements exist in it.

**Why not C:** An organizational template or standard set of requirements is sometimes called a "requirements library" or "standard requirements," not a baseline. A baseline is project-specific and time-stamped, capturing the exact approved state of requirements for that project at that moment.