The correct option is Run the repository script by referencing its path with the run keyword.

In GitHub Actions a step that uses the run key executes commands on the runner from the checked out repository. Once the workflow checks out the code the runner has the scripts directory available and you can call the script by its path. You can invoke the file with a shell such as bash followed by the path or ensure it is executable and call it directly. This uses the single source of truth in the repository and meets the requirement to run that exact file without moving or duplicating it.

Make sure your workflow includes a checkout step so the repository content exists on the runner before the run step executes. With the repository present the path scripts/backup_task.sh is resolvable and the command runs as intended.

Embed the script content directly inside the workflow file is incorrect because it duplicates the script and creates drift between the workflow and the repository file. The requirement is to run the existing file without copying it.

Use Google Cloud Build to trigger the script from outside GitHub Actions is incorrect because the task belongs inside the GitHub Actions workflow and introducing an external service adds complexity without benefit. It also does not guarantee that the runner executes the exact repository file by path.

Manually transfer the file to the runner and invoke it with a shell is incorrect because the standard checkout step already places repository files on the runner. Extra transfer steps are unnecessary and increase the chance of errors.

Full AWS Practitioner Certification Question