The correct option is Commit large binary artifacts such as videos or machine images directly to the repository.

This is not recommended because Git repositories work best with text files that can be diffed and compressed efficiently. Storing large binaries inflates repository size, slows cloning and fetching, makes history rewrites painful, and prevents meaningful code reviews. Platform limits and warnings are easy to hit with big files, and better solutions exist such as using Git Large File Storage, release assets, artifact repositories, or external storage while keeping pointers in the repo.

Enable protected rules on the main branch with required reviews and checks is a recommended practice because branch protection with required reviews and status checks helps maintain code quality and stability. It reduces the chance of breaking changes landing in the default branch and enforces a healthy review and CI workflow.

Use topic branches for new work instead of forking for routine changes is recommended in most internal team settings because feature branches keep changes isolated and easy to review while keeping history organized. Forks are better for external contributions or when permissions require them, while topic branches streamline day to day collaboration within a single repository.

Include a clear README at the root that explains purpose and how to get started is a best practice because it guides contributors on project scope, setup, and usage. A good README improves onboarding, reduces confusion, and sets consistent standards across repositories.

Full AWS Practitioner Certification Question