CAPM Practice: Demonstrate an understanding of the various project life cycles and processes

The first statement defines what will be delivered (iOS and Android support), which is part of project scope. The second statement identifies a constraint—a limiting factor requiring approval from a specific person, which restricts the team's freedom to make design decisions independently.

**Why not A:** Neither statement describes a risk. A risk is an uncertain future event that may affect the project. The platform support requirement is a definite scope element, and the approval requirement is a known constraint — neither involves uncertainty about whether they will occur.

**Why not B:** Neither statement is an assumption. Assumptions are factors believed to be true without proof. The platform requirement is a defined scope item, and the approval requirement is a documented constraint on decision-making authority — both are stated facts, not unverified beliefs.

**Why not C:** The first statement is not a constraint — it does not limit the team's options but rather defines what they will build (scope). Constraints restrict how work can be done, while scope defines what will be delivered. The second statement is better classified as a constraint than an assumption.