What is a change freeze, and when is it typically invoked in FOSSE?

• A. A period when changes are allowed only for bug fixes.
• B. A schedule for deploying changes in production.
• C. A period in which changes are not allowed to production (e.g., around market-critical times) to protect stability.
• D. A process for rolling back changes after release.

Answer: (C)

A change freeze is a defined period during which changes are not allowed to go into production to protect system stability during times of heightened risk or critical business activity. In FOSSE, this is typically invoked around market-critical times—such as market open/close, major events, or other high-volume trading periods—so that trading systems, risk controls, and related infrastructure aren’t disrupted by last-minute changes. The goal is to reduce operational risk, maintain predictability, and ensure there’s time for thorough testing, validation, and a rollback plan if needed. During a freeze, normal deployment is paused and only pre-approved emergency fixes (with proper approval) may proceed. Other options describe deployment schedules or rollback processes, or suggest changes are allowed for bug fixes only, which isn’t what a freeze is about.