You are beginning development of a new version of an application while the previous version remains in production. You must continue to deploy fixes and updates to the current production version while developing the new version. The new-version code is stored in AWS CodeCommit. What branching strategy meets these requirements?

This branching strategy allows for parallel development and maintenance. Creating a dedicated feature branch from main for production bug fixes ensures that critical updates can be deployed quickly without interfering with the ongoing development of the new version. Simultaneously, a separate feature branch for the new version's development, also branched from main, isolates its changes. This prevents the new version's potentially unstable code from affecting the production environment and allows both streams of work to progress independently. Incorrect options: Git tags are pointers to specific commits and are primarily used for marking releases, not for active development or managing parallel workstreams. Creating a branch for production code and applying an IAM policy doesn't facilitate parallel development of a new version or bug fixes; it only restricts access to a specific branch. Creating a separate CodeCommit repository for the new version adds unnecessary overhead and complexity, making it harder to merge changes back into a unified codebase later.