The correct option is Open the repository settings in GitHub and add the person as a collaborator to send an invitation.

In a personal repository, the proper way to grant write access is by adding the person as a collaborator from the repository settings, which triggers an invitation that the contractor must accept. Once accepted, the collaborator has the necessary permissions to push commits and create pull requests on the private repository.

Send an email invite from her work email address is wrong because GitHub access is not granted through email. Permissions must be assigned within GitHub using the repository invitation flow.

Share the repository URL with the person so they can clone it is incorrect because a private repository cannot be cloned or pushed to without explicit access. The URL alone does not grant any permissions.

Add the developer to a GitHub organization team that has access to the repository is not applicable because the repository is owned by a personal account. Teams are an organization feature and cannot be used to grant access to a personal repository.

Full AWS Practitioner Certification Question