MENU
-- [Configure and Use Dependency Management]
Which of the following options would close a Dependabot alert?
Suggested Answer: A
Get Premium GH-500 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
A Dependabot alert is only marked as resolved when the related vulnerability is no longer present in your code --- specifically after you merge a pull request that updates the vulnerable dependency.
Simply viewing alerts or graphs does not affect their status. Ignoring the alert by leaving the repo unchanged keeps the vulnerability active and unresolved.
29 comments · newest first
AL
Alline
6 months ago
Yeah, A makes the most sense. Let’s resolve those alerts!
HE
Helaine
7 months ago
I feel confident about A. It’s straightforward.
LO
Loreta
7 months ago
D is definitely not an option. We need to act!
YO
Yolando
7 months ago
Agreed! Merging fixes the issue.
VA
Valentin
7 months ago
I think A is the correct answer. Pull requests are key.
DE
Deangelo
7 months ago
Totally agree, A) is the only way to fix it!
ER
Ernestine
8 months ago
Wait, leaving it as is (D) actually counts? That seems wrong!
DU
Dustin
8 months ago
C) doesn't close anything either, just shows the graph.
DE
Deonna
8 months ago
C) Viewing the dependency graph? Nah, that's not gonna fix the problem. You gotta take action!
EL
Eleni
8 months ago
A) Creating a pull request to resolve the vulnerability is the way to go. Gotta stay on top of those security issues!
HY
Hyman
9 months ago
Haha, I bet the answer is not D) Leaving the repository in its current state. That would be like ignoring the problem and hoping it goes away!
KA
Kattie
9 months ago
B) Viewing the Dependabot alert on the Dependabot alerts tab of your repository
GE
Gertude
9 months ago
I’m a bit confused; I thought just viewing the alerts wouldn’t help, but I can't remember if it was B or C that was mentioned in the study material.
MA
Malcom
9 months ago
I practiced a similar question last week, and I feel like creating a pull request is definitely the way to go, so A seems solid.
VI
Vilma
9 months ago
I'm not entirely sure, but I remember something about just viewing alerts not actually closing them, so maybe B and C aren't correct?
VE
Veta
9 months ago
I think option A is the right choice because resolving the vulnerability is what Dependabot is all about, right?
AU
Augustine
10 months ago
A feels like the right answer to me. Resolving the underlying issue by creating a PR is the most effective way to close the alert, rather than just viewing it.
KA
Kallie
10 months ago
Okay, let me think this through. I know Dependabot alerts are about vulnerabilities, so leaving the repo as-is doesn't seem right. I'm leaning towards A, but I want to make sure I understand the other choices first.
EL
Elke
10 months ago
I think B) is just for viewing, not closing.
YU
Yun
10 months ago
A) Creating a pull request to resolve the vulnerability that will be approved and merged
ED
Edna
10 months ago
A) is definitely the right choice!
MO
Mollie
11 months ago
B and C are just for viewing, not fixing.
IN
In
11 months ago
Hmm, I'm a bit confused. I'm not sure if viewing the alert or the dependency graph would actually close it. I'll need to double-check the options.
JE
Jenelle
11 months ago
I think the answer is A. Creating a pull request to resolve the vulnerability seems like the best way to close a Dependabot alert.
MI
Mireya
6 months ago
A is the best option for sure!
MI
Miesha
6 months ago
B and C don't really solve the problem, right?
BI
Billy
6 months ago
Yeah, pulling a request is essential for fixing issues.
SH
Sheron
6 months ago
I agree, A is definitely the way to go.
LO
Lonny
11 months ago
Exactly, just viewing won't help at all.