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

Microsoft GH-100 Exam - Topic 4 Question 5 Discussion

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

How does GitHub support compliance requirements for enterprises?

Show Suggested Answer Hide Answer
Suggested Answer: A

GitHub Enterprise gives you a suite of configurable controls - like a comprehensive audit log, enforced SAML single sign-on, and enterprise-level rulesets - that you can tailor and enforce to meet your organization's compliance mandates.


by Letha at Aug 17, 2025, 10:57 PM

Limited Time Offer

25%

Off

Get Premium GH-100 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Tonette
4 months ago
Wait, D says passwords are in plaintext? That can't be right!
upvoted 0 times
...
Marcos
4 months ago
Totally agree, A is the way to go.
upvoted 0 times
...
Charlie
5 months ago
C makes sense, but it feels too restrictive.
upvoted 0 times
...
Shawna
5 months ago
B is just wrong, collaboration is key!
upvoted 0 times
...
Sheridan
5 months ago
A has all the right features for compliance!
upvoted 0 times
...
Cory
5 months ago
I definitely recall that GitHub encrypts passwords, but I thought it was more about security than compliance, so D seems off to me.
upvoted 0 times
...
Tammara
6 months ago
I think I saw a practice question about permissions, and it mentioned that only admins can write changes (C), but I'm not convinced that's the main compliance feature.
upvoted 0 times
...
Darci
6 months ago
I'm not entirely sure, but I feel like disabling all external collaboration (B) wouldn't really support compliance needs.
upvoted 0 times
...
Silvana
6 months ago
I remember studying how GitHub offers features like audit logs and SAML for compliance, so I think A might be the right choice.
upvoted 0 times
...
Georgiann
6 months ago
Whoa, option D about plaintext passwords? That can't be right. GitHub is all about security, so I doubt they would do something that insecure. I'm going to rule that one out right away.
upvoted 0 times
...
Skye
6 months ago
Ah, this is a good one. I remember learning about GitHub's compliance controls in my DevSecOps course. I think option A is the best answer, covering the key features like audit logging and SAML.
upvoted 0 times
...
Erick
7 months ago
Hmm, I'm a bit unsure about this one. I know GitHub has some enterprise-focused features, but I'm not totally clear on the specifics. I'll need to read through the options carefully.
upvoted 0 times
...
Gertude
7 months ago
This seems like a straightforward question about GitHub's compliance features. I'll focus on identifying the key capabilities mentioned in the options.
upvoted 0 times
...
Sabra
7 months ago
Option B? Are you kidding me? Disabling external collaboration is the opposite of what enterprises need.
upvoted 0 times
...
Jaime
7 months ago
Haha, option D is hilarious! Storing passwords in plaintext, that's a surefire way to get hacked.
upvoted 0 times
...
Dominga
7 months ago
Option A is definitely the correct answer. GitHub's configurable controls are essential for enterprise compliance.
upvoted 0 times
Mira
4 months ago
Exactly! Compliance needs those configurable controls.
upvoted 0 times
...
Ricarda
4 months ago
Option B is just not practical for enterprises.
upvoted 0 times
...
Shelba
4 months ago
Yeah, the audit log is crucial for tracking changes.
upvoted 0 times
...
Carlee
4 months ago
I agree, option A makes the most sense.
upvoted 0 times
...
...
Dorethea
7 months ago
I agree with Eladia. Those features help enterprises ensure security and compliance.
upvoted 0 times
...
Eladia
7 months ago
I think GitHub supports compliance requirements by providing configurable controls like audit logs and SAML authentication.
upvoted 0 times
...

Save Cancel