A Linux administrator needs to update a script that is stored in the team's Git repository. After the administrator clones the repository, which of the following is the BEST method to ensure merging c

Forking or creating a new repository severs the shared history and makes synchronizing upstream changes unnecessarily complex, defeating the purpose of a shared team repository.

Adding a folder named after the administrator is not a version-control strategy - it duplicates files outside of Git's branching model and does not prevent merge conflicts.

Committing directly to the master branch bypasses any review process and risks overwriting or conflicting with commits other team members have already pushed.

Creating a new branch gives the administrator an isolated workspace where commits do not interfere with the main branch or other contributors' commits. When the work is ready, it can be merged via a pull or merge request, which Git tracks per-commit so no other user's history is lost. This is the standard Git collaboration workflow designed specifically to prevent overwriting concurrent changes.