Microsoft GH-900 - Microsoft GitHub Foundations Certification Exam

GitHub offers a variety of features for different aspects of project management and documentation.
For long-form documentation, the best feature is Wikis. Wikis in GitHub allow you to create detailed,
structured documentation that is easy to navigate and edit. Each repository in GitHub can have its
own Wiki, which acts as a space for collaborators to maintain project documentation, guides,
manuals, or any other long-form content. Wikis are specifically designed to host extensive documentation in a way that is easy to reference
and edit over time. They support Markdown, allowing you to format your documentation effectively.
Unlike the other options, Wikis are explicitly intended for the purpose of long-form content, making
them the best choice for this use case.

In GitHub, issues and pull requests (PRs) are essential tools for managing work and collaboration in a

project. Assigning individuals to these issues or PRs is a way to indicate responsibility for addressing

the issue or completing the PR.
GitHub Docs: Permission Levels for a Repository
GitHub Docs: Assigning Issues and Pull Requests
Anyone with write permissions to the repository:
Anyone who has commented on the Issue or pull request:
Which of the following is the best GitHub feature for long-form documentation for a project?
This detailed explanation provides clarity on GitHub's assignment mechanics for issues and pull
requests, reflecting the platform's collaborative nature.
Users who have write permissions to a repository can be assigned to issues and pull requests. Write
permissions allow users to push changes to the repository, create branches, and modify issues and
pull requests. Assigning them to an issue or PR ensures they are recognized as responsible for the
task.
Option C is incorrect because not all personal GitHub accounts can be assigned to issues or PRs. The
user needs either write permissions to the repository or must have commented on the issue or PR.
Option A is incorrect because having an enterprise GitHub account alone does not necessarily grant
the ability to be assigned to issues or PRs. Permission to assign is based on repository-specific roles
and permissions.
GitHub allows you to assign issues or pull requests to users who have already engaged with the
discussion by commenting on it. This feature is particularly useful for quickly assigning tasks to those
who are already involved in the conversation.

Git is a distributed version control system, meaning that every developer has a full copy of the entire
repository, including its history, on their local machine. This enables greater flexibility, as work can be
done offline and each user has access to the full project history.
Open Source Software:
Git is open-source, meaning its source code is freely available for use, modification, and distribution.
This fosters a large community of users and contributors who continuously improve the software.
Option B is incorrect because Git is not a sequential version control system, nor is it inherently tied to
cloud-based services. GitHub, GitLab, and other platforms offer cloud hosting for Git repositories, but
Git itself is a version control tool. Option C is incorrect because Git is not limited to small projects; it is designed to scale efficiently, and
the other features mentioned are only partial descriptions of Git's capabilities. Option D is incorrect because Git is not a centralized version control system; it is distributed.
Additionally, Git is open-source, not proprietary, and is used for projects of all sizes.

In GitHub, an organization member is a user who has been added to an organization and is subject to
the organization's base permissions and policies. An outside collaborator is a user who is not a
member of the organization but has been granted access to one or more repositories within the
organization. Here’s the difference between an organization member and an outside collaborator:
Organization Members:
Members are subject to the organization's base permissions, which apply across all repositories
within the organization. These permissions might include read, write, or admin access, depending on
what has been set as the default.
Outside collaborators do not have organization-wide permissions. They only have access to specific
repositories to which they have been granted permission. This means organization base permissions
do not apply to them (making option A correct).
Outside collaborators do not consume paid licenses. They are only counted toward the license if they
are made organization members.

To configure a queue for telephone-based cases in Dynamics 365 Customer Service, you need to ensure proper case handling rules and lifecycle control so cases created from phone calls are processed correctly.
Why B is correct:

• Entitlements and SLAs define how cases (including phone-based cases) are prioritized and managed.

• Helps ensure that cases coming from telephone support follow proper service agreements.

• Controls case limits, service levels, and support coverage.

Why C is correct:

• Status reason transitions control how a case moves between states (Active, On Hold, Resolved, etc.).

• Essential for managing workflow of cases coming from queues like telephone support.

• Ensures cases follow a controlled lifecycle once assigned from the queue.

---

Why others are incorrect:

• A. Create a case from email → Email-specific, not telephone queue configuration.

• D. Create a case routing rule → Useful, but not one of the best answers compared to SLA + status transitions in this scenario.

• E. Automatically create or update records → Generic automation, not specific to queue handling for telephone cases.