Microsoft GH-200 Exam - Topic 3 Question 9 Discussion

Actual exam question for Microsoft's GH-200 exam

Question #: 9
Topic #: 3

[All GH-200 Questions]

Which of the following scenarios would require the use of self-hosted runners instead of GitHub-hosted runners?

Arunning more than the three concurrent workflows supported by GitHub-hosted runners

Bexceeding 50,000 monthly minutes of build time

Cusing Docker containers as part of the workflow

Dusing specialized hardware configurations required for workflows

Eperforming builds on macOS

Show Suggested Answer

Suggested Answer: A, D

GitHub-hosted runners have a limit on the number of concurrent workflows (typically 20 for free-tier accounts and 5 for enterprise). If your organization needs to run more workflows simultaneously, you would need to use self-hosted runners to increase the available concurrency.

Self-hosted runners allow you to configure specialized hardware or software setups that are necessary for certain workflows. GitHub-hosted runners may not have access to custom hardware configurations like GPUs or other specialized resources, so self-hosted runners are required in such cases.

by Jolene at Nov 24, 2025, 04:04 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Vallie

1 month ago

All options have merit, but A feels most urgent for teams.

upvoted 0 times

...

Miles

2 months ago

E is relevant too. macOS builds need specific setups.

upvoted 0 times

...

Nohemi

2 months ago

C is my pick. Docker is essential for many workflows.

upvoted 0 times

...

Alva

2 months ago

I lean towards D. Specialized hardware can’t be ignored.

upvoted 0 times

...

Leonard

2 months ago

Definitely! But B is also important. Those minutes add up fast.

upvoted 0 times

...

Earnestine

2 months ago

I think option A is a solid reason for self-hosted runners. More concurrency is crucial.

upvoted 0 times

...

Sharita

2 months ago

E) is a bit misleading, though. GitHub has macOS runners too!

upvoted 0 times

...

Tanja

3 months ago

D) is definitely a must for specialized setups.

upvoted 0 times

...

Eliseo

3 months ago

I think C) is also a reason.

upvoted 0 times

...

Sina

3 months ago

A) and B) for sure!

upvoted 0 times

...

Alfreda

4 months ago

I'm with Tom on this one, gotta go with D for that sweet, sweet hardware.

upvoted 0 times

...

Nakisha

4 months ago

D) all the way, can't beat that custom silicon!

upvoted 0 times

...

Gilma

4 months ago

That's a tough one, I'd have to go with D. Specialized hardware is a dealbreaker for GitHub-hosted.

upvoted 0 times

...

Zoila

4 months ago

E) performing builds on macOS

upvoted 0 times

...

Frank

4 months ago

C) using Docker containers as part of the workflow

upvoted 0 times

...

Yasuko

4 months ago

I practiced a question similar to this, and I think exceeding the monthly minutes is a reason too, but I’m not completely confident.

upvoted 0 times

...

Timothy

5 months ago

I feel like using Docker containers might also require self-hosted runners, but I can't recall the exact details.

upvoted 0 times

...

Iraida

5 months ago

I'm not entirely sure, but I remember something about GitHub-hosted runners having limits on concurrent workflows. Is that A?

upvoted 0 times

...

Mona

5 months ago

Hmm, this is a tricky one. I'm not super familiar with the differences between the GitHub-hosted and self-hosted runners. I'll need to review the documentation to make sure I understand the specific limitations and capabilities of each. I don't want to guess and risk getting this wrong on the exam.

upvoted 0 times

...

Jacob

5 months ago

I've got this! The key is understanding the capabilities and limitations of the GitHub-hosted runners. Scenarios A, B, C, and D all describe situations where the GitHub-hosted runners wouldn't be sufficient, so self-hosted runners would be required. E is the only one that's a bit more ambiguous, but the others are pretty straightforward.

upvoted 0 times

...

Delila

5 months ago

I think self-hosted runners are definitely needed when you have specialized hardware configurations, right? That sounds familiar.

upvoted 0 times

...

Eloisa

5 months ago

Okay, let's think this through step-by-step. The GitHub-hosted runners have limits on concurrent workflows and monthly build time, so A and B are clear cases for self-hosted. C and D also seem like they would require more customization that the GitHub-hosted runners may not provide. E is an interesting one, I'll have to double-check the supported platforms.

upvoted 0 times

...

Catarina

6 months ago

D) using specialized hardware configurations required for workflows

upvoted 0 times

...

Eugene

6 months ago

Wait, can you really exceed 50,000 minutes? That seems high!

upvoted 0 times

...

Nenita

6 months ago

Hmm, I'm a bit unsure about this one. I know the GitHub-hosted runners have some limitations, but I'm not sure I fully understand all the differences. I'll need to review the documentation on self-hosted runners to make sure I'm clear on when to use them.

upvoted 0 times

...

Miesha

6 months ago

I think the key here is to identify the limitations of the GitHub-hosted runners and when self-hosted runners would be a better option. Scenarios C and D seem like they would require more specialized configurations that the GitHub-hosted runners may not support.

upvoted 0 times