The correct selection is D. A release branch isolates the completed sprint from new sprint development. Final UAT fixes can be made against the release candidate while future features continue on the development branch, after which the release fixes are merged back so both production and ongoing development remain synchronized. 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 (D. Using Git, create a release branch from the develop branch. All fixes must be made in the release branch. After deployment, merge release with develop.). 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.