Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

GitHub Exam GitHub-Advanced-Security Topic 6 Question 2 Discussion

Actual exam question for GitHub's GitHub-Advanced-Security exam
Question #: 2
Topic #: 6
[All GitHub-Advanced-Security Questions]

-- [Configure and Use Secret Scanning]

What is the first step you should take to fix an alert in secret scanning?

Show Suggested Answer Hide Answer
Suggested Answer: C

The first step when you receive a secret scanning alert is to revoke the secret if it is still valid. This ensures the secret can no longer be used maliciously. Only after revoking it should you proceed to remove it from the code history and apply other mitigation steps.

Simply deleting the secret from the code does not remove the risk if it hasn't been revoked --- especially since it may already be exposed in commit history.


by Stevie at May 03, 2025, 02:17 AM

Limited Time Offer

25%

Off

Get Premium GitHub-Advanced-Security Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Reita
3 months ago
Ooh, this one's tricky. But I reckon D is the way to go - remove that secret and nip it in the bud!
upvoted 0 times
Kate
1 months ago
User 3: Agreed, let's go with option D.
upvoted 0 times
...
Paulene
2 months ago
User 2: Yeah, that sounds like the best way to fix the alert.
upvoted 0 times
...
Marta
2 months ago
User 1: I think we should remove the secret in a commit to the main branch.
upvoted 0 times
...
...
Andree
3 months ago
I think archiving the repository could also be a valid option to fix the alert in secret scanning.
upvoted 0 times
...
Stephaine
3 months ago
But what if the secret is still valid? Shouldn't we revoke the alert instead?
upvoted 0 times
...
Antonio
3 months ago
Haha, archiving the repository? That's like throwing the baby out with the bathwater! Definitely not A.
upvoted 0 times
Onita
2 months ago
D) Remove the secret in a commit to the main branch.
upvoted 0 times
...
Kyoko
2 months ago
C) Revoke the alert if the secret is still valid.
upvoted 0 times
...
Alayna
3 months ago
B) Update your dependencies.
upvoted 0 times
...
...
Patti
3 months ago
I disagree, I believe the correct step is to remove the secret in a commit to the main branch.
upvoted 0 times
...
Kaitlyn
4 months ago
I'm going with B. Updating dependencies can sometimes help resolve security issues like this.
upvoted 0 times
Gaynell
3 months ago
Updating dependencies can definitely help with security vulnerabilities.
upvoted 0 times
...
Benedict
3 months ago
I agree, it's always a good idea to keep dependencies up to date.
upvoted 0 times
...
Milly
3 months ago
I think B is a good choice. Updating dependencies is important for security.
upvoted 0 times
...
...
Virgina
4 months ago
C seems more logical to me. Revoking the alert if the secret is still valid would be the safest approach.
upvoted 0 times
...
Teri
4 months ago
I think the answer is D. Removing the secret in a commit to the main branch is the first step to fix the alert.
upvoted 0 times
Edelmira
2 months ago
C) Revoke the alert if the secret is still valid.
upvoted 0 times
...
Armando
2 months ago
B) Update your dependencies.
upvoted 0 times
...
Kathryn
3 months ago
A) Archive the repository.
upvoted 0 times
...
...
Stephaine
4 months ago
I think the first step should be to update your dependencies.
upvoted 0 times
...

Save Cancel