The correct option is Ask the repository owner to add the secret in repository settings or grant you admin rights.

Only users with admin access to a repository can create or manage repository secrets that GitHub Actions uses. In a personal repository the owner has admin access and collaborators typically do not. The most direct way forward is to have the owner create the secret or elevate your access so you can add it.

Open a ticket with GitHub support to request elevated permissions to manage secrets on the repository is incorrect because GitHub Support cannot change repository permissions for a personal repository and only the owner can grant admin rights or create secrets.

Fork the repository to your own account and define the secret in the fork is incorrect because secrets are scoped to each repository and the upstream workflow will not use secrets defined only in your fork. In addition, secrets are not exposed to workflows triggered from forks by default which makes this ineffective for deploying from the original repository.

Create the value in Google Secret Manager and expect GitHub Actions to read it automatically without a repository secret is incorrect because GitHub Actions does not automatically pull secrets from external providers. You would need explicit authentication and workflow steps to fetch them which still requires proper configuration rather than relying on automatic access.

Full AWS Practitioner Certification Question