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

Microsoft GH-100 Exam - Topic 2 Question 7 Discussion

Actual exam question for Microsoft's GH-100 exam
Question #: 7
Topic #: 2
[All GH-100 Questions]

What additional capability does secret scanning offer for private repositories on GitHub Enterprise Cloud?

Show Suggested Answer Hide Answer
Suggested Answer: A

Secret scanning in private repositories on GitHub Enterprise Cloud lets you define and use custom regular-expression patterns - so you can detect internal or proprietary secret formats beyond the default partner-provided types.


Contribute your Thoughts:

0/2000 characters
Barb
2 days ago
Wait, does it really disable code with secrets? Sounds too extreme.
upvoted 0 times
...
Jeanice
7 days ago
Custom patterns? Sounds like a job for the secret police!
upvoted 0 times
...
Quentin
25 days ago
Rewriting history? That's like trying to unring a bell. Good luck with that!
upvoted 0 times
...
Glenna
1 month ago
B) Disables any code that contains a secret. Hmm, that might be a bit too heavy-handed.
upvoted 0 times
...
Leota
1 month ago
D) Revokes GitHub access tokens automatically. That's a good way to mitigate the damage from a leaked secret.
upvoted 0 times
...
Marget
1 month ago
C) Rewrites history to remove secrets. Seems like a risky approach, but could be effective.
upvoted 0 times
...
Jesusita
2 months ago
A) Allows custom pattern definitions for internal secret formats. This is the most comprehensive solution.
upvoted 0 times
...
Adelina
2 months ago
I’m leaning towards the custom pattern definitions option, but I also remember something about rewriting history in a different context.
upvoted 0 times
...
Telma
2 months ago
I feel like disabling code with secrets is a feature, but I can't recall if it's specifically for private repositories.
upvoted 0 times
...
Aileen
2 months ago
I remember a practice question about secret scanning, and I think it was related to revoking access tokens automatically.
upvoted 0 times
...
Vernell
2 months ago
I think secret scanning might allow for custom pattern definitions, but I'm not entirely sure if that's the only capability it offers.
upvoted 0 times
...
Mertie
2 months ago
Hmm, I'm a bit stumped on this one. I don't have much experience with the enterprise version of GitHub. I'll have to make an educated guess and hope for the best.
upvoted 0 times
...
Sherita
3 months ago
Ah, secret scanning - that rings a bell. I think I read about that feature before. I'll try to recall what it does and match that to the options.
upvoted 0 times
...
Corinne
3 months ago
Okay, let's see. I know GitHub has some security features for private repos, so I'm guessing this is asking about one of those. I'll try to eliminate the options that don't sound right.
upvoted 0 times
...
Peggie
3 months ago
I think A is the best choice. Custom patterns are super useful.
upvoted 0 times
...
Yasuko
3 months ago
A) Allows custom pattern definitions for internal secret formats.
upvoted 0 times
...
Cecil
4 months ago
Totally agree, that's super useful!
upvoted 0 times
...
Ozell
4 months ago
I agree, A makes sense. Tailored patterns help catch specific secrets.
upvoted 0 times
...
Alease
4 months ago
Hmm, this seems like a tricky one. I'm not super familiar with the details of GitHub Enterprise Cloud, so I'll need to think through the options carefully.
upvoted 0 times
...
Leonor
4 months ago
I think this is asking about a specific GitHub Enterprise Cloud feature, so I'll need to focus on understanding the capabilities of that product.
upvoted 0 times
Miriam
3 months ago
I believe it’s about custom patterns.
upvoted 0 times
...
...

Save Cancel