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

Actual exam question for GitHub's GitHub-Advanced-Security exam

Question #: 3
Topic #: 2

[All GitHub-Advanced-Security Questions]

-- [Configure and Use Secret Scanning]

What happens when you enable secret scanning on a private repository?

ARepository administrators can view Dependabot alerts.

BYour team is subscribed to security alerts.

CGitHub performs a read-only analysis on the repository.

DDependency review, secret scanning, and code scanning are enabled.

Show Suggested Answer

Suggested Answer: C

When secret scanning is enabled on a private repository, GitHub performs a read-only analysis of the repository's contents. This includes the entire Git history and files to identify strings that match known secret patterns or custom-defined patterns.

GitHub does not alter the repository, and enabling secret scanning does not automatically enable code scanning or dependency review --- each must be configured separately.

by Viola at May 01, 2025, 10:55 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Erinn

17 days ago

Secret scanning, huh? Sounds like a job for our in-house 'Secret Agent' developer. I'll let them handle this one.

upvoted 0 times

Ludivina

2 days ago

Yes, it helps to detect any exposed secrets in the code.

upvoted 0 times

...

Merissa

3 days ago

I think enabling secret scanning on private repositories is important for security.

upvoted 0 times

...

Gertude

10 days ago

Yes, it helps to detect any exposed secrets in the code.

upvoted 0 times

...

Glenn

13 days ago

I think enabling secret scanning on private repositories is important for security.

upvoted 0 times

...

Hillary

29 days ago

Hold on, is this a trick question? I'm going with A. Gotta keep those admins in the loop, right?

upvoted 0 times

...

Amira

1 months ago

I think enabling secret scanning means your team is subscribed to security alerts as well.

upvoted 0 times

...

Britt

1 months ago

I'm not sure about that, but I know that repository administrators can view Dependabot alerts.

upvoted 0 times

...

Leonard

1 months ago

This is a tough one, but I'm going with B. Securing our team's alerts is the way to go.

upvoted 0 times

Effie

7 days ago

I agree with you, B. Subscribing to security alerts is important for our team.

upvoted 0 times

...

Nicolette

11 days ago

I believe it's D. Dependency review, secret scanning, and code scanning are enabled.

upvoted 0 times

...

Noah

15 days ago

I think it's C. GitHub performs a read-only analysis on the repository.

upvoted 0 times

...

Luke

1 months ago

I believe enabling secret scanning also enables dependency review, secret scanning, and code scanning.

upvoted 0 times

...

Leonor

2 months ago

Hmm, I think it's D. Gotta get all that security goodness enabled, you know?

upvoted 0 times

Pilar

9 days ago

Yeah, D seems like the most comprehensive choice for enabling security measures.

upvoted 0 times

...

Rhea

11 days ago

Definitely, can't be too careful with sensitive information.

upvoted 0 times

...

Ming

14 days ago

Yeah, it's important to have all those security features enabled.

upvoted 0 times

...

Gilma

17 days ago

I think D is the best option too, we need to make sure our repository is secure.

upvoted 0 times

...

Sang

22 days ago

I think it's D too. Better safe than sorry.

upvoted 0 times

...

Franchesca

24 days ago

I agree, D sounds like the right choice for enabling all security features.

upvoted 0 times

...

Peggie

2 months ago

I think when you enable secret scanning, GitHub performs a read-only analysis on the repository.

upvoted 0 times

...

Rana

2 months ago

I'm pretty sure it's C. GitHub just does a read-only scan, no need to worry about any changes to the repo.

upvoted 0 times

...