The correct selection is A. A shared release calendar aligns internal major and minor releases with Salesforce seasonal upgrades, blackout periods, testing windows, and business readiness. The calendar becomes the common coordination mechanism across teams instead of relying on ad hoc metadata spreadsheets or routing every operational decision through the COE. 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 rejected alternatives weaken release control by mixing development states, skipping required validation, or treating production promotion as an ad hoc administrative task. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (A. Create a release calendar, train and align all the teams.). 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.