Free Microsoft GH-200 Actual Exam Questions - Question 8 Discussion
the file from the repo. In which scenarios would temporarily disabling a workflow be most useful?
(Choose two.)
Option A is solid because if the external service is down, there's no point in triggering the workflow and causing unnecessary failures. Option B also fits since a faulty workflow spamming requests can mess things up quickly, so pausing it avoids further damage. Options C, D, and E don’t really match because disabling a workflow isn’t about runner types, changing trigger types, or enabling logging; those require config changes rather than just disabling. So A and B make the most sense for temporary disabling purposes.
I think A and B fit best since disabling helps avoid running faulty workflows that cause errors or waste.
Probably B, since stopping errors quickly is key, and A to avoid failing calls when services are down.
A imo, prevents waste when services are down, and B stops harmful request floods fast.
Makes sense to pick A since disabling avoids running workflows that would just fail if the service is down. I’d go with B too, because if a workflow is spamming wrong requests, you want a quick way to stop it without deleting anything. D’s about changing triggers, not really about pausing. So definitely A and B.
Maybe A and B make the most sense here. Disabling a workflow when a service is down (A) prevents unnecessary failures and alerts, which can clutter logs and waste resources. Then, B fits because if a workflow is causing wrong or too many requests, stopping it temporarily helps limit damage until fixed. The others feel less about temporarily stopping to prevent immediate issues and more about configuration or logging changes.
I think A makes sense to avoid failures if the service is down. For the second, B could be valid since stopping bad requests quickly helps. D seems more about changing triggers than just disabling temporarily. What do you think?
Maybe B for stopping bad traffic fast, plus A to avoid failures when service is down.
B sounds practical too to stop bad impact before fixing, not just a bug fix.
Stopping a workflow when its target service is down (A) is practical to avoid failures. Also, switching from scheduled runs to manual triggers (D) often needs temporarily disabling the automatic runs. So, A and D.
A, D. Disabling helps when the service is down (A) and when you want to switch how a workflow runs without deleting it, like changing from schedule to manual (D). B feels more like a bug to fix.
A/B