Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft GH-200 Exam - Topic 3 Question 16 Discussion

As a developer, you need to use GitHub Actions to deploy a microservice that requires runtime access to a secure token. This token is used by a variety of other microservices managed by different teams in different repos. To minimize management overhead and ensure the token is secure, which mechanisms should you use to store and access the token? (Choose two.)
C) Use a corporate non-GitHub secret store (e.g., HashiCorp Vault) to store the token. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime. and E) Store the token as an organizational-level encrypted secret in GitHub. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.
A) Store the token in a configuration file in a private repository. Use GitHub Actions to deploy the configuration file to the runtime environment.
B) Store the token as a GitHub encrypted secret in the same repo as the code. Create a reusable custom GitHub Action to access the token by the microservice at runtime.
D) Store the token as a GitHub encrypted secret in the same repo as the code. During deployment, use GitHub Actions to store the secret in an environment variable that can be accessed at runtime.

Microsoft GH-200 Exam - Topic 3 Question 16 Discussion

Actual exam question for Microsoft's GH-200 exam
Question #: 16
Topic #: 3
[All GH-200 Questions]

As a developer, you need to use GitHub Actions to deploy a microservice that requires runtime access to a secure token. This token is used by a variety of other microservices managed by different teams in different repos. To minimize management overhead and ensure the token is secure, which mechanisms should you use to store and access the token? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: C, E

Using a corporate secret store like HashiCorp Vault provides a secure, centralized location for sensitive information. GitHub Actions can then retrieve and store the token securely during deployment by setting it as an environment variable, ensuring the token remains secure and accessible at runtime.

Storing the token as an organizational-level encrypted secret in GitHub ensures it is accessible across multiple repositories, minimizing management overhead. GitHub Actions can then use this secret during deployment by setting it as an environment variable, allowing the microservice to access it securely at runtime.


by Monroe at May 27, 2026, 04:01 PM

Limited Time Offer

25%

Off

Get Premium GH-200 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Gail
4 days ago
Let’s go with E and maybe C for extra security later.
upvoted 0 times
...
Lashawnda
9 days ago
Exactly! Security and ease of use are key.
upvoted 0 times
...
Brandon
14 days ago
I see your point. E does simplify cross-team access.
upvoted 0 times
...
Gail
19 days ago
Right! Plus, option D is good too, but I prefer E for broader access.
upvoted 0 times
...
Lashawnda
25 days ago
True, but it adds complexity. GitHub secrets are easier to manage.
upvoted 0 times
...
Brandon
30 days ago
But what about option C? Using HashiCorp Vault is also secure.
upvoted 0 times
...
Gail
1 month ago
Agreed! It minimizes risk across teams.
upvoted 0 times
...
Lashawnda
1 month ago
I think option E is the best choice. Organizational-level secrets are more secure.
upvoted 0 times
...
Juliana
2 months ago
I’m all for using GitHub encrypted secrets, super convenient!
upvoted 0 times
...
Adolph
2 months ago
Wait, can we really trust GitHub secrets? Seems sketchy.
upvoted 0 times
...
Ula
2 months ago
Storing in a private repo? No way, that’s risky!
upvoted 0 times
...
Lamonica
2 months ago
I think C is a solid choice too, but it adds complexity.
upvoted 0 times
...
Leanora
2 months ago
Definitely go with E and D for security!
upvoted 0 times
...
Catarina
2 months ago
I vaguely remember a practice question about storing secrets as environment variables during deployment. I think option D might be a good choice, but I need to double-check the details.
upvoted 0 times
...
Matilda
3 months ago
I feel like using a corporate secret store like HashiCorp Vault could be more secure, but I can't recall if we practiced that specific integration with GitHub Actions.
upvoted 0 times
...
Delmy
3 months ago
I think option E sounds right because it mentions organizational-level secrets, which could help with managing access across different teams.
upvoted 0 times
...
William
3 months ago
I remember we discussed using GitHub encrypted secrets in class, but I'm not sure if it's better to use repo-level or organizational-level secrets for this scenario.
upvoted 0 times
...

Save Cancel