Part Five: Enterprise Essentials [GitHub Foundations Certification Prep Course]

[tuves]

This discussion and its comment have been edited and modified from its original format to enable evergreen learning

We’re in the final section of our prep course 🎉 Just one more part to complete and you’ll be ready to take the GitHub Foundations certification exam. You’re almost at the finish line, now let’s cross it together!

Looking for our previous sections to study?

• Learn about more GitHub Features & Open Source Part Four’s Discussion
• Review Repositories in Part Three’s Discussion
• Study Copilot in Part Two's Discussion
• Cover Foundations of Foundations in Part One's Discussion

---

Step One: Prep 📚

Microsoft Learn Modules

• Manage an Inner Source program by using GitHub
• Introduction to GitHub administration
• Authenticate and authorize user identities on GitHub

Further reading

• Essentials of administration and governance with GitHub Enterprise Cloud by @rhoticity
• Privacy, Security, and Administration from the @LadyKerr’s study guide

Video

• GitHub Foundations Certification Course: GitHub Administrator and GitHub Enterprise

Step Two: Test Your Knowledge ⚡

Question One: What is a common benefit of using inner source practices within an organization?
A) Increased external contributions from the open source community.
B) Improved collaboration and code sharing across different teams within the organization.
C) Reduced need for internal documentation and training.
D) Enhanced security through proprietary code.

Question Two: What is a key difference between a member and a collaborator in a GitHub organization?
A) Members have access to all repositories, while collaborators only have access to specific repositories.
B) Collaborators can create repositories, while members cannot.
C) Members can manage billing information, while collaborators cannot.
D) Collaborators have higher administrative privileges than members.

Question Three: What is the difference between a parent team and a child team in GitHub?
A) A parent team has more permissions than a child team
B) A parent team can contain other teams, while a child team cannot
C) A child team can override the permissions of a parent team
D) A child team has administrative access to all repositories in the organization

Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program?
A) To automate the review process
B) To integrate with third-party tools
C) To limit the number of contributors
D) To provide a consistent format for contributions, making it easier to manage them

Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub?
A) Enabling two-factor authentication for all users
B) Regularly reviewing and updating access permissions
C) Using a single sign-on (SSO) solution
D) Sharing passwords for shared accounts

---

To view the answers, jump to the comment below.

Looking to hide your answers? This markdown formatting will only show your answers if someone clicks to reveal it. Copy the text below to format your answers this way if you’d like!

<details>

Your answers go here!


</details> 

Use the discussion below to share additional study resources, ask questions for our team to answer, and respond to our prep questions.

*No Purchase Necessary. Open only to Github community members 14+. Game ends 5/2/25. For details, see Official Rules.

[Salgado2004]

Let's go for the last week! 🥹 What a ride everybody! I hope it was useful! 🚀 Great studies

If you have followed my contributions, please share your thoughts and feedbacks in the replies 😊💕

Step One: Prep 📚

• Check the GitHub Advanced Security Certification Exam prep
• Check all the domain 6 topics explained

enterprise_essentials.mp4

Step Two: Test Your Knowledge ⚡

1. Question: What is a common benefit of using inner source practices within an organization?

   B) Improved collaboration and code sharing across different teams within the organization.

2. Question: What is a key difference between a member and a collaborator in a GitHub organization?

   A) Members have access to all repositories, while collaborators only have access to specific repositories.

3. Question: What is the difference between a parent team and a child team in GitHub?

   B) A parent team can contain other teams, while a child team cannot

4. Question: What is the purpose of using issue and pull-request templates in an InnerSource program?

   D) To provide a consistent format for contributions, making it easier to manage them

5. Question: Which of the following is NOT a recommended practice for managing user identities on GitHub?

   D) Sharing passwords for shared accounts

[garzuze]

Great!

[DivineBrightness]

Q1: ✅ B) Improved internal team collaboration & code sharing.

Q2: ✅ C) Members manage billing; collaborators don’t.

Q3: ✅ B) Parent teams contain child teams; child teams can’t.

Q4: ✅ D) Standardizes contributions for easier management.

Q5: ✅ D) Never share passwords (use SSO/2FA instead).

[jick0712]

5

[yaya4117]

Your answers go here!

[ImmrBhattarai]

Question 1: What is a common benefit of using inner source practices within an organization?
Answer: B) Improved collaboration and code sharing across different teams within the organization.

Question 2: What is a key difference between a member and a collaborator in a GitHub organization?
Answer: A) Members have access to all repositories, while collaborators only have access to specific repositories.

Question 3: What is the difference between a parent team and a child team in GitHub?
Answer: B) A parent team can contain other teams, while a child team cannot

Question 4: What is the purpose of using issue and pull-request templates in an InnerSource program?
Answer: D) To provide a consistent format for contributions, making it easier to manage them

Question 5: Which of the following is NOT a recommended practice for managing user identities on GitHub?
Answer: D) Sharing passwords for shared accounts

<\details>

[Apexq]

Q-1: B) Improved collaboration and code sharing across different teams within the organization.

Q-2:
A) Members have access to all repositories, while collaborators only have access to specific repositories.

Q-3:
B) A parent team can contain other teams, while a child team cannot.

Q-4:
D) To provide a consistent format for contributions, making it easier to manage them.

Q-5:
D) Sharing passwords for shared accounts.

[gopalcnepal]

Question 1: B
Question 2: A
Question 3: B
Question 4: D
Question 5: D

[yz-rrr]

1. B) Improved collaboration and code sharing across different teams within the organization.
2. A) Members have access to all repositories, while collaborators only have access to specific repositories.
3. B) A parent team can contain other teams, while a child team cannot.
(I am not sure of the intent of this statement. If this statement means that a child's team cannot have more than one parent's team, then I think it is correct. On the other hand, if it means nesting of teams, then it would seem to be wrong, since nesting seems to be possible...? https://docs.github.com/ja/organizations/organizing-members-into-teams/about-teams#nested-teams)
4. D) To provide a consistent format for contributions, making it easier to manage them
5. D) Sharing passwords for shared accounts

[RadNaw1986]

Question 1: B
Question 2: A
Question 3: B
Question 4: D
Question 5: D

[jick0712]

A

[GitHer-Muna]

Answers:

1.B
2.A
3.B
4.D
5. D

[jick0712]

A

[salahtidur]

Here are my answers:

Question One:
B) Improved collaboration and code sharing across different teams within the organization.

Question Two:
A) Members have access to all repositories, while collaborators only have access to specific repositories.

Question Three:
B) A parent team can contain other teams, while a child team cannot.

Question Four:
D) To provide a consistent format for contributions, making it easier to manage them.

Question Five:
D) Sharing passwords for shared accounts.

[skywalkerAlex]

1.B
2.A
3.B
4.D
5.D

[vrajesh0804]

Q1: ✅ B)
Q2: ✅ C)
Q3: ✅ B)
Q4: ✅ D)
Q5: ✅ D)

[solid391]

answer as below
Question One: What is a common benefit of using inner source practices within an organization?
B) Improved collaboration and code sharing across different teams within the organization.

Question Two: What is a key difference between a member and a collaborator in a GitHub organization?
A) Members have access to all repositories, while collaborators only have access to specific repositories.

Question Three: What is the difference between a parent team and a child team in GitHub?
B) A parent team can contain other teams, while a child team cannot

Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program?

D) To provide a consistent format for contributions, making it easier to manage them

Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub?

D) Sharing passwords for shared accounts

[Glamfirth88]

Question One: What is a common benefit of using inner source practices within an organization?
B) Improved collaboration and code sharing across different teams within the organization.

Question Two: What is a key difference between a member and a collaborator in a GitHub organization?
A) Members have access to all repositories, while collaborators only have access to specific repositories.

Question Three: What is the difference between a parent team and a child team in GitHub?
B) A parent team can contain other teams, while a child team cannot

Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program?
D) To provide a consistent format for contributions, making it easier to manage them

Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub?
D) Sharing passwords for shared accounts

[niikwade]

Question One: What is a common benefit of using inner source practices within an organization? **A) Members have access to all repositories, while collaborators only have access to specific repositories.**

Question Two: What is a key difference between a member and a collaborator in a GitHub organization?
D) Collaborators have higher administrative privileges than members.

Question Three: What is the difference between a parent team and a child team in GitHub?
B) A parent team can contain other teams, while a child team cannot

Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program?
D) To provide a consistent format for contributions, making it easier to manage them

Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub?
D) Sharing passwords for shared accounts

[ecole1rllco]

Week Five Knowledge Check:

Question One: What is a common benefit of using inner source practices within an organization?
B. Improved collaboration and code sharing across different teams within the organization.

Question Two: What is a key difference between a member and a collaborator in a GitHub organization?
A. Members have access to all repositories, while collaborators only have access to specific repositories.

Question Three: What is the difference between a parent team and a child team in GitHub?
B. A parent team can contain other teams, while a child team cannot

Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program?
D. To provide a consistent format for contributions, making it easier to manage them

Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub?
D. Sharing passwords for shared accounts

[Jose-C0]

Question One: What is a common benefit of using inner source practices within an organization?
B) Improved collaboration and code sharing across different teams within the organization.

Question Two: What is a key difference between a member and a collaborator in a GitHub organization?
A) Members have access to all repositories, while collaborators only have access to specific repositories.

Question Three: What is the difference between a parent team and a child team in GitHub?
C) A child team can override the permissions of a parent team

Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program?
D) To provide a consistent format for contributions, making it easier to manage them

Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub?
D) Sharing passwords for shared accounts

[K1404-creator]

Question 1: B
Question 2: A
Question 3: B
Question 4: D
Question 5: D

[Bella-my]

Questão 1: B
Questão 2: A
Questão 3: B
Questão 4: D
Questão 5: D

[allubie]

1-B, 2-A, 3-B, 4-D, 5-D

[johnnieng]

Sorry, I am late this week.

Question One:
B) Improved collaboration and code sharing across different teams within the organization.

Inner source practices focus on fostering internal collaboration and code reuse across teams within an organization, mirroring open-source workflows. Other options either contradict the purpose (A, D) or are incorrect (C).

Question Two:
A) Members have access to all repositories, while collaborators only have access to specific repositories.

In GitHub Organizations, members belong to the organization and can be granted access to all repositories (depending on team settings), whereas collaborators are granted access to specific repositories only. Other options misrepresent permissions or roles.

Question Three:
B) A parent team can contain other teams, while a child team cannot.

Parent teams can include child teams to create hierarchical structures, but child teams cannot contain other teams. Other options incorrectly describe permissions or access levels.

Question Four:
D) To provide a consistent format for contributions, making it easier to manage them.

Templates standardize the structure of issues and pull requests, ensuring clarity and efficiency in managing contributions. Other options are either secondary benefits (e.g., automation) or irrelevant (e.g., limiting contributors).

Question Five:
D) Sharing passwords for shared accounts.

Sharing passwords violates security best practices. Enabling 2FA, using SSO, and reviewing permissions (A – C) are recommended for secure identity management.

[6arash6]

1.B
2.A
3.B
4.D
5.D

[hussain0x]

Details

Question 1: B Question 2: A Question 3: B Question 4: D Question 5: D

[rujjal]

1. B
2. A
3. B
4. D
5. D

[msolo-st]

1. B; Improved collaboration and code sharing across different teams within the organization.

2. A; Members have access to all repositories, while collaborators only have access to specific repositories.

3. B; A parent team can contain other teams, while a child team cannot

4. D; To provide a consistent format for contributions, making it easier to manage them

5. D; Sharing passwords for shared accounts

[pohhjie]

1. B
2. A
3. B
4. D
5. D

[sandroffdsantos]

Good day.

I just came across this certification only today.
If i do all the required training from the start will i still be eligible to do the "Exam"?
Or is it a requirement to have been aligned with the weeks sessions from the start?

[queenofcorgis]

@sandroffdsantos no alignment needed at all feel free to start training, the only eligibility that would be affected is for our prizes which we've distributed. We'll actually be working on making this content evergreen so folks can take the course at their own pace.

[queenofcorgis]

Congratulations! Our course is now complete ✅ Find out if you were a winner, how to take an exam, and what's next in our announcement discussion ❤️ Thanks everyone for a great course!

[Dlassoc]

Question One: B) Improved collaboration and code sharing across different teams within the organization Inner source promotes open source practices within a company, enhancing cross-team collaboration.

Question Two:
A) Members have access to all repositories, while collaborators only have access to specific repositories
Members belong to the organization and can be granted broader access, while collaborators are external and added to specific repos.

Question Three:
B) A parent team can contain other teams, while a child team cannot
Parent teams help organize and manage nested team structures in GitHub.

Question Four:
D) To provide a consistent format for contributions, making it easier to manage them
Templates streamline contribution formats, improving clarity and consistency.

Question Five:
D) Sharing passwords for shared accounts
This is a major security risk and not a recommended practice.

[XuanhaoZu]

B A B D D