Which action in version control allows a user to obtain exclusive editing permissions on a file?

Getting exclusive editing permissions on a file in version control is typically accomplished through the action of checking out a file. When a user checks out a file, they lock it from being modified by others, ensuring that they have sole access to make changes until they check the file back in. This is crucial in collaborative environments where simultaneous edits can lead to conflicts and inconsistencies in the codebase.

The process of checking out a file allows users to download the version they need for editing, potentially preventing other team members from making modifications during that time. Once the user is finished, they can check it back in, allowing others to access the updated version. This mechanism ensures that the development process remains organized and minimizes the risk of overwriting others' work.

In contrast, actions like checking in and committing are related to saving changes back to the version control system rather than obtaining editing permissions. Cloning refers to making a complete copy of a repository, which does not involve permissions for individual files. Thus, checking out is specifically designed for gaining exclusive control over editing a file, making it the correct choice.