Universal Containers has many development teams deploying into a single org.

The correct selection is C. Major production releases should be avoided during peak commercial periods because unexpected regressions, performance degradation, or integration failures have the greatest business impact then. A release calendar should define blackout windows while retaining a separate hotfix path for genuine emergencies. From a release perspective, approved functionality must be isolated from unfinished work and promoted through a predictable, auditable path. Release calendars, validation, stakeholder approval, rollback planning, and branch discipline reduce the risk that a technically correct change becomes an operational failure during production promotion. The other options do not create a safe production path because they ignore timing, approval, rollback, or branch synchronization requirements. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (C. Avoid releasing near peak business periods.). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: Releasing — release management; branching and hotfixes; production readiness; rollback strategy; seasonal releases; approvals.