GitHub Exam GitHub-Actions Topic 4 Question 9 Discussion

Actual exam question for GitHub's GitHub-Actions exam

Question #: 9
Topic #: 4

Your organization is managing secrets using GitHub encrypted secrets, including a secret named SuperSecret. As a developer, you need to create a version of that secret that contains a different value for use in a workflow that is scoped to a specific repository named MyRepo. How should you store the secret to access your specific version within your workflow?

ACreate a duplicate entry for SuperSecret in the encrypted secret store and specify MyRepo as the scope.

BCreate MyRepo_SuperSecret in GitHub encrypted secrets to specify the scope to MyRepo.

CCreate a file with the SuperSecret. information in the .qithub/secrets folder in MyRepo.

DCreate and access SuperSecret from the secrets store in MyRepo.

Show Suggested Answer

Suggested Answer: B

To scope a secret to a specific repository, you can create a new secret with a name like MyRepo_SuperSecret in the secrets section of the MyRepo repository's settings. This ensures that the secret is specific to that repository and can be used within its workflows.

by Chanel at Mar 05, 2025, 08:21 AM

Limited Time Offer

25%

Off

Get Premium GitHub-Actions Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Kizzy

2 months ago

Option B is the way to go. Keep it simple and specific to the repository. No need to mess around with duplicate secrets or local files.

upvoted 0 times

Gianna

29 days ago

Yeah, it's important to keep things simple and avoid unnecessary duplication or local storage.

upvoted 0 times

...

Lorrine

1 months ago

I agree, having MyRepo_SuperSecret in GitHub encrypted secrets makes it easy to manage and access.

upvoted 0 times

...

Vinnie

1 months ago

Option B is definitely the best choice. It keeps things organized and specific to the repository.

upvoted 0 times

...

Lilli

2 months ago

I'm not sure, but I think creating a duplicate entry for SuperSecret in the encrypted secret store and specifying MyRepo as the scope could also work.

upvoted 0 times

...

Adelina

2 months ago

Haha, I bet the person who came up with option C was trying to be 'creative'. That's just adding unnecessary complexity.

upvoted 0 times

...

Corrinne

2 months ago

I disagree, I believe the correct answer is D) Create and access SuperSecret from the secrets store in MyRepo.

upvoted 0 times

...

Leslie

2 months ago

Hmm, I'm not sure. Creating a file in the .github/secrets folder seems a bit convoluted. I'd go with B or D.

upvoted 0 times

Alfred

20 days ago

Yeah, D could work too, but B is more specific to the repository scope.

upvoted 0 times

...

Florencia

21 days ago

I agree, B seems like the most logical choice for accessing the specific version of the secret.

upvoted 0 times

...

Oretha

1 months ago

I think B is the way to go. It's clear and straightforward.

upvoted 0 times

...

Catrice

2 months ago

Option D sounds like the way to go. Accessing the secret directly from the repository's secrets store is the most straightforward approach.

upvoted 0 times

...

Blossom

2 months ago

I think the answer is B) Create MyRepo_SuperSecret in GitHub encrypted secrets to specify the scope to MyRepo.

upvoted 0 times

...

Denny

2 months ago

I think the correct answer is B. Creating a specific secret for the repository makes the most sense, rather than duplicating the original secret.

upvoted 0 times

Veronique

2 months ago

Yes, it's important to keep secrets scoped to specific repositories to minimize the risk of exposure.

upvoted 0 times

...

Paz

2 months ago

I agree, having a unique secret for each repository is a good practice for security.

upvoted 0 times

...

Lillian

2 months ago

I think the correct answer is B. Creating a specific secret for the repository makes the most sense, rather than duplicating the original secret.

upvoted 0 times

...