Before a production release, a developer needs to freeze changes in an AWS CodeCommit repository while continuing to work on new features. QA will test the release and perform bug fixes isolated from the main branch. After release, all bug fixes must be merged into main. Which workflow meets these requirements?

Creating a release branch from the commit to be released allows the development team to freeze the code for QA and bug fixes without halting new feature development on the main branch. Bug fixes applied to the release branch are isolated, ensuring the production release is stable. New features continue on main. After the release, merging the release branch back into main integrates all bug fixes into the main development line. Incorrect options: Using a Git tag for fixes is not a standard practice as tags are static pointers to specific commits and cannot be directly modified with new commits. Rebasing main onto the release branch would rewrite the history of main, which is generally discouraged for shared branches and can lead to merge conflicts and lost history. Applying commits for fixes directly to a Git tag is not possible; commits are applied to branches.