Free Microsoft GH-100 Actual Exam Questions - Question 14 Discussion
.github/dependabot.yml file?
A, since it defines when and what dependencies Dependabot checks and updates.
Probably A, since dependabot.yml mainly sets how updates are managed and scheduled.
A/C? The file sets up the schedule and directories, but C mentions scanning secrets, which is a separate GitHub feature. So A fits better as it’s about update configs, not security scans.
Maybe A, since B and D don't really fit Dependabot's update management role.
Option A, since dependabot.yml defines where and how often to check for updates.
It’s definitely not B or D since those options don’t really align with what Dependabot does. The file’s main role is to tell Dependabot where to look and how often, so A makes the most sense. C is tempting but secret scanning is a separate feature outside of this config. The yml is all about organizing update checks by ecosystem and schedule, so A nails it from a practical standpoint.
It’s A because dependabot.yml is all about configuring when and what dependencies to check, not about excluding SHAs or encrypting anything. That setup file controls the update process directly.
A/C? C seems off since secret scanning isn’t the dependabot.yml’s job, and D looks unrelated too. A fits best because it sets schedules and ecosystems, while B sounds incorrect about SHAs.
Probably A, since dependabot.yml mainly sets update schedules and config details.
Maybe B isn’t right since Dependabot doesn’t really exclude commits by SHA. The yml file is more for setting up when and how updates run, which fits A better here.
D imo, encrypting versions in the repo sounds way too complicated and unnecessary. The file’s main job is clearly about managing update checks and schedules, which points to A as the best fit.
Makes sense to rule out B, C, and D since Dependabot mainly deals with update settings. So, A is the clear choice here.
B tbh I picked A at first, but then I thought about the other options. B sounds off because Dependabot doesn't really exclude commits by SHA; it’s more about update configurations. C and D just don’t fit how Dependabot works—it’s not about scanning secrets or encrypting versions. So A still makes the most sense as it deals with setting schedules and ecosystems for updates.
Definitely A. That file sets up how and when Dependabot checks for updates and where it looks in your repo.