Week Five: Enterprise Essentials [GitHub Foundations Certification Prep Course] #157556
Replies: 68 comments 6 replies
-
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 📚
enterprise_essentials.mp4Step Two: Test Your Knowledge ⚡
|
Beta Was this translation helpful? Give feedback.
-
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). |
Beta Was this translation helpful? Give feedback.
-
Question 1: What is a common benefit of using inner source practices within an organization? Question 2: What is a key difference between a member and a collaborator in a GitHub organization? Question 3: What is the difference between a parent team and a child team in GitHub? Question 4: What is the purpose of using issue and pull-request templates in an InnerSource program? Question 5: Which of the following is NOT a recommended practice for managing user identities on GitHub? <\details> |
Beta Was this translation helpful? Give feedback.
-
Q-1:
B) Improved collaboration and code sharing across different teams within the organization.
Q-2: Q-3: Q-4: Q-5: |
Beta Was this translation helpful? Give feedback.
-
Question 1: B |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
Question 1: B |
Beta Was this translation helpful? Give feedback.
-
Answers: 1.B |
Beta Was this translation helpful? Give feedback.
-
Here are my answers:
Question One: Question Two: Question Three: Question Four: Question Five: |
Beta Was this translation helpful? Give feedback.
-
1.B |
Beta Was this translation helpful? Give feedback.
-
Q1: ✅ B) |
Beta Was this translation helpful? Give feedback.
-
answer as below Question Two: What is a key difference between a member and a collaborator in a GitHub organization? Question Three: What is the difference between a parent team and a child team in GitHub? 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 |
Beta Was this translation helpful? Give feedback.
-
Question One: What is a common benefit of using inner source practices within an organization? Question Two: What is a key difference between a member and a collaborator in a GitHub organization? Question Three: What is the difference between a parent team and a child team in GitHub? Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program? Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub? |
Beta Was this translation helpful? Give feedback.
-
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? Question Three: What is the difference between a parent team and a child team in GitHub? Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program? Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub? |
Beta Was this translation helpful? Give feedback.
-
Week Five Knowledge Check: Question One: What is a common benefit of using inner source practices within an organization? Question Two: What is a key difference between a member and a collaborator in a GitHub organization? Question Three: What is the difference between a parent team and a child team in GitHub? Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program? Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub? |
Beta Was this translation helpful? Give feedback.
-
Question 1: B |
Beta Was this translation helpful? Give feedback.
-
AnswersQuestion 1: B) Improved collaboration and code sharing across different teams within the organization. Question 2: A) Members have access to all repositories, while collaborators only have access to specific repositories. Question 3: B) A parent team can contain other teams, while a child team cannot. Question 4: D) To provide a consistent format for contributions, making it easier to manage them. Question 5: D) Sharing passwords for shared accounts. |
Beta Was this translation helpful? Give feedback.
-
Question One: What is a common benefit of using inner source practices within an organization? Question Two: What is a key difference between a member and a collaborator in a GitHub organization? Question Three: What is the difference between a parent team and a child team in GitHub? Question Four: What is the purpose of using issue and pull-request templates in an InnerSource program? Question Five: Which of the following is NOT a recommended practice for managing user identities on GitHub? |
Beta Was this translation helpful? Give feedback.
-
Question 1: B |
Beta Was this translation helpful? Give feedback.
-
Questão 1: B |
Beta Was this translation helpful? Give feedback.
-
1-B, 2-A, 3-B, 4-D, 5-D |
Beta Was this translation helpful? Give feedback.
-
Sorry, I am late this week. Question One: 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: 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: 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: 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: Sharing passwords violates security best practices. Enabling 2FA, using SSO, and reviewing permissions (A – C) are recommended for secure identity management. |
Beta Was this translation helpful? Give feedback.
-
1.B |
Beta Was this translation helpful? Give feedback.
-
DetailsQuestion 1: B Question 2: A Question 3: B Question 4: D Question 5: D |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Good day. I just came across this certification only today. |
Beta Was this translation helpful? Give feedback.
-
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! |
Beta Was this translation helpful? Give feedback.
-
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: Question Three: Question Four: Question Five: |
Beta Was this translation helpful? Give feedback.
-
We’re in the final week 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 weeks’ to study?
Step One: Prep 📚
Microsoft Learn Modules
Further reading
Video
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
We’ll be sharing the answers in the comments on Friday 🧠 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!
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.
Beta Was this translation helpful? Give feedback.
All reactions