The correct option is Create feature branches and open pull requests for review.

This approach gives each engineer an isolated workspace to implement changes while keeping the main branch stable. It enables asynchronous code review so changes are discussed and approved before merge. It suits distributed teams across many time zones and reduces the risk of unreviewed code reaching production.

Adopt a centralized version control workflow is incorrect because a centralized model encourages direct commits to a shared trunk which reduces isolation and does not provide a built in review gate before merge.

Enable branch protection rules on the main branch is insufficient on its own. Protection rules enforce requirements on the main branch but they do not give contributors a separate workspace to stage changes or a structured proposal process before merging.

Schedule all commits within a shared four hour window each day is a coordination policy rather than a Git workflow and it neither isolates work nor guarantees code review and it is hard to sustain across twelve time zones.

Full AWS Practitioner Certification Question