Home/microsoft/Free Microsoft GH-200 Actual Exam Questions/Question 10

Free Microsoft GH-200 Actual Exam Questions - Question 10 Discussion

Question No. 10

In which scenarios could the GITHUB_TOKEN be used? (Choose two.)

Select all that apply, then reveal solution.

Usman W.

2026-02-17

D, C. The GITHUB_TOKEN is designed to automate tasks within the repo context, so creating issues (D) fits perfectly since it allows interaction with the repo’s API. Publishing to GitHub Packages (C) also makes sense because packages are tied to repositories. Options like adding members (F) or creating secrets (B) require higher privileges or manual setup, so they’re unlikely. Reading from the file system (E) isn’t related to token permissions but more about runner environment access. Leveraging self-hosted runners (A) is about infrastructure, not token usage.

Usman W.

2026-02-17

C/D? The GITHUB_TOKEN is scoped to the repository, so it makes sense it can be used for publishing packages (C) and creating issues (D). Adding members (F) is definitely org-level, so that’s out. Creating secrets (B) usually requires manual setup, so it’s unlikely the token can do that. Reading from the file system (E) isn’t a token permission thing—it’s about runner access, so probably not right either. A is more about runner config than token use. So C and D feel like the solid picks here.

Usman W.

2026-02-12

C/D, because the token is meant for repo-specific actions like publishing packages and managing issues, but it can't handle org-level stuff or file system access.

Usman W.

2026-02-11

Option C and D for sure, org-level stuff like adding members is out.

Ahmed Q.

2026-01-30

C/D for sure, GITHUB_TOKEN can handle repo tasks like publishing and issues only.

Ahmed Q.

2026-01-26

D The token’s scope is repo-specific, so it can create issues within that repo but definitely can’t manage org members or secrets. That’s a good way to rule out options like F and B.

Ahmed Q.

2026-01-26

C GITHUB_TOKEN is designed for repo-level tasks like publishing packages, and D fits since it allows issue creation within the same repo. Other options deal with broader or unrelated permissions.

Chris K.

2026-01-15

It’s C and D – GITHUB_TOKEN can publish packages and create issues, but not manage org members or secrets.

Chris K.

2026-01-11

I think C and D are correct. GITHUB_TOKEN can publish packages and create issues, but not sure about adding members or reading the runner's file system.