The correct option is Add a workflow step that runs chmod +x on the script before executing it.

Unix like runners require the executable permission bit for a script to run as a program. Although Git can track the execute bit in the repository, it is common for a file to be missing that bit when checked in or when created during the job. Adding an explicit step in the workflow to grant execute permission guarantees that the script will be runnable at job time on any runner and avoids permission denied errors.

Use a special YAML key in the workflow to set the script as executable is incorrect because the workflow syntax does not include a key to change file permissions. You must set permissions within a run step or commit the executable bit in the repository.

Cloud Build is incorrect because it is a separate Google service that is not part of GitHub Actions and it does not affect how a GitHub Actions runner handles file permissions.

Reference the script path in the workflow and rely on the runner to handle permissions is incorrect because runners do not automatically mark files as executable. Without the execute bit the step will fail with a permission error.

Full AWS Practitioner Certification Question