View Full Microsoft GH-900 Exam Dumps and Practice Test Dumps

 

Question 221

What does a GitHub repository’s visibility determine?

1. How commit messages are formatted
2. Who can access the repository
3. Which editor contributors use
4. How branches are named

Correct Answer: 2

Explanation:

Repository visibility determines who can access and discover a repository. GitHub commonly provides public and private visibility options, with additional organizational controls available in some contexts. Visibility is an important administrative consideration because it affects the audience that can access repository contents and related activity. It does not determine how developers format commit messages, which editors they use, or how branches must be named. Understanding visibility helps GH-900 learners distinguish access configuration from development conventions and individual contributor preferences.

Question 222

Which GitHub feature groups related issues toward a larger objective?

1. Milestones
2. Webhooks
3. Repository forks
4. Commit tags

Correct Answer: 1

Explanation:

Milestones group related issues and pull requests around a larger objective, such as a release, project phase, or development target. They help teams track progress toward a defined goal by associating multiple work items with the same milestone. Webhooks communicate repository events to external systems, forks provide separate repository copies, and Git tags identify points in source history. Milestones therefore belong primarily to GitHub’s project-management capabilities and provide a structured way to monitor progress across multiple related tasks.

Question 223

Which Git command shows the branches available in a local repository?

1. git merge
2. git branch
3. git clean
4. git archive

Correct Answer: 2

Explanation:

The git branch command can list local branches and also provides operations for creating, deleting, or managing branch references. When used without additional options, it displays the branches available in the local repository and indicates the currently selected branch. git merge combines histories, git clean removes selected untracked files, and git archive creates an archive from repository content. Understanding the purpose of common Git commands helps developers select the appropriate operation without confusing branch management with file cleanup or history integration.

Question 224

What is a GitHub repository template intended to simplify?

1. Creating repositories with predefined structure
2. Encrypting individual commit messages
3. Replacing organization teams
4. Removing historical commits

Correct Answer: 1

Explanation:

A repository template provides a reusable starting point for creating new repositories with predefined files, folders, configurations, and other project structure. Organizations can use templates to establish consistent starting patterns for similar projects. This can reduce repetitive setup work and encourage standardized practices across repositories. Templates do not encrypt commit messages, replace organization teams, or remove Git history. Their primary purpose is to provide a convenient foundation from which new repositories can be created while retaining useful project-specific structure.

Question 225

Which GitHub capability lets an organization define reusable repository standards?

1. Repository stars
2. Organization-level repository policies
3. Issue comments
4. Release assets

Correct Answer: 2

Explanation:

Organizations can define repository policies and controls that establish consistent standards across repositories. Such policies can support governance by setting expectations or restrictions for repositories within the organization. This is particularly useful when many teams manage projects under the same organizational structure. Stars are primarily for personal discovery, issue comments support discussion, and release assets accompany published releases. Organization-level policies therefore address governance and consistency rather than individual repository bookmarking, conversation, or software distribution.

Question 226

What does a GitHub pull request primarily request?

1. A repository ownership change
2. Integration of proposed changes
3. A new organization account
4. A replacement repository license

Correct Answer: 2

Explanation:

A pull request primarily proposes integrating changes from one branch or repository into another. It provides a collaboration area where maintainers and contributors can review differences, discuss modifications, request changes, and eventually merge the proposed work. Pull requests do not primarily transfer repository ownership, create organizations, or replace licenses. They are a central part of GitHub’s collaborative development workflow because they connect source-code changes with review and controlled integration.

Question 227

Which GitHub feature can automatically apply labels based on issue configuration?

1. Issue automation
2. Git tags
3. Repository licensing
4. Branch aliases

Correct Answer: 1

Explanation:

GitHub issue automation can help apply labels or perform other configured actions based on repository events and workflow logic. Automation can reduce repetitive maintenance work, particularly in projects that receive many issues or pull requests. Git tags identify points in Git history, repository licensing defines legal usage conditions, and branch aliases are not the mechanism for issue classification. Automated labeling can improve consistency by applying predictable metadata to incoming work items according to project-defined rules.

Question 228

What is the purpose of GitHub repository archives?

1. Preserve a repository while making it inactive
2. Convert commits into issues
3. Generate new organization accounts
4. Replace repository branches

Correct Answer: 1

Explanation:

Archiving a repository is used when a project is no longer actively maintained but its contents should remain available for reference. An archived repository becomes read-only for many ordinary development activities while preserving its historical information. This makes archiving useful for completed, discontinued, or superseded projects. Archiving does not convert commits into issues, create organizations, or replace branches. Understanding the difference between archiving and deletion is important because archiving preserves project information rather than removing the repository entirely.

Question 229

Which GitHub feature helps maintainers identify responsible reviewers for specific files?

1. Repository topics
2. CODEOWNERS
3. Project views
4. Release notes

Correct Answer: 2

Explanation:

The CODEOWNERS mechanism identifies individuals or teams responsible for reviewing changes to specified paths within a repository. When configured correctly, GitHub can use these ownership rules to request reviews from the appropriate people when relevant files are changed. Repository topics categorize projects, project views organize work items, and release notes describe published versions. CODEOWNERS therefore connects file paths with review responsibility and is especially useful for larger repositories where different teams maintain different components.

Question 230

What does GitHub’s audit log primarily record?

1. Repository source files
2. Administrative and organizational events
3. Software license text
4. Local Git configuration

Correct Answer: 2

Explanation:

The GitHub audit log records significant activities and events associated with organizations or accounts, depending on the applicable GitHub plan and scope. Administrators can use audit information to investigate actions, understand changes to settings, and support governance or compliance activities. The audit log is not a replacement for repository source files, license documents, or local Git configuration. Its purpose is to provide a historical record of relevant platform activity, making it useful when organizations need visibility into administrative and security-related events.

Question 231

Which Git command creates a new commit from staged changes?

1. git commit
2. git fetch
3. git remote
4. git switch

Correct Answer: 1

Explanation:

The git commit command records staged changes as a new commit in the local repository’s history. Before committing, developers typically inspect changes, stage the intended files, and provide a commit message describing the update. git fetch retrieves information from a remote repository, git remote manages remote references, and git switch changes the active branch. Understanding the sequence of editing, staging, and committing is fundamental to Git workflows because each step represents a different state transition in local source control.

Question 232

Which GitHub feature supports conversations directly attached to lines in a pull request diff?

1. Repository topics
2. Inline review comments
3. Organization billing
4. Release assets

Correct Answer: 2

Explanation:

Inline review comments allow reviewers to discuss specific lines or sections of a proposed change within a pull request diff. This provides precise feedback because the comment is associated directly with the code under discussion. Repository topics classify repositories, billing handles organizational account charges, and release assets accompany published versions. Inline comments are particularly useful during code review because reviewers can identify a concern without requiring contributors to search through a separate general discussion to determine which code the feedback concerns.

Question 233

What does the GitHub repository security policy commonly explain?

1. How to report security vulnerabilities
2. How to rename Git branches
3. How to create project views
4. How to configure repository topics

Correct Answer: 1

Explanation:

A repository security policy, commonly represented by SECURITY.md, can explain how security researchers and users should report vulnerabilities. It may provide preferred reporting methods, supported versions, or other security-related guidance. This gives projects a consistent channel for handling potentially sensitive security issues. Branch naming, project views, and repository topics serve different purposes and are not the primary role of a security policy. Including clear security-reporting guidance can help maintainers receive vulnerability information through an appropriate process rather than through public issue discussions.

Question 234

Which GitHub feature provides a visual comparison of changes between branches?

1. Pull request diff
2. Repository star list
3. Organization member list
4. Discussion category

Correct Answer: 1

Explanation:

A pull request diff presents the changes proposed between the relevant source and target states. Reviewers can inspect added, modified, and removed lines to understand what a contribution changes before deciding whether it should be integrated. A repository star list identifies repositories a user has starred, an organization member list concerns account membership, and discussion categories organize conversations. Reviewing a diff is therefore a core part of code review because it allows contributors and maintainers to evaluate the actual source changes associated with a proposed update.

Question 235

What is the primary purpose of GitHub issue labels?

1. Categorize and organize issues
2. Encrypt repository contents
3. Publish application binaries
4. Change Git commit authors

Correct Answer: 1

Explanation:

Issue labels provide descriptive metadata that helps teams categorize and organize issues. Projects can use labels for concepts such as bug reports, feature requests, priorities, documentation tasks, or areas of responsibility. Labels make it easier to filter and understand work across a repository. They do not encrypt repository contents, publish binaries, or modify Git commit authorship. Effective labeling can improve issue management by giving maintainers a consistent way to classify incoming work and identify groups of related tasks.

Question 236

Which GitHub feature can provide financial support to eligible open-source contributors?

1. GitHub Actions
2. GitHub Sponsors
3. GitHub Pages
4. GitHub Codespaces

Correct Answer: 2

Explanation:

GitHub Sponsors provides a mechanism through which eligible developers and open-source contributors can receive financial support from sponsors. It is designed to help sustain individuals or organizations contributing to open-source projects. GitHub Actions focuses on automation, GitHub Pages supports website publishing, and Codespaces provides cloud-based development environments. These features address different aspects of software development and project participation. Understanding GitHub Sponsors helps learners distinguish community-support functionality from automation, web publishing, and development-environment capabilities.

Question 237

What does a GitHub Actions workflow file define?

1. Automated jobs and their execution logic
2. Repository ownership history
3. Issue discussion categories
4. GitHub account passwords

Correct Answer: 1

Explanation:

A GitHub Actions workflow file defines automation instructions, including events, jobs, steps, permissions, and other workflow configuration. Workflow files are commonly stored in the repository’s .github/workflows directory and can automate testing, builds, validation, deployment, and other development tasks. They do not define repository ownership history, discussion categories, or account passwords. Understanding workflow files is essential for recognizing how GitHub Actions translates repository events into automated processing.

Question 238

Which GitHub capability provides cloud-hosted development environments?

1. GitHub Issues
2. GitHub Codespaces
3. GitHub Discussions
4. GitHub Releases

Correct Answer: 2

Explanation:

GitHub Codespaces provides cloud-hosted development environments that can be configured for working with repositories. Developers can use these environments without depending entirely on a locally configured development machine. Codespaces can provide tools and project dependencies in a consistent environment, which can simplify onboarding and remote development. Issues manage tracked work, Discussions support conversations, and Releases organize published versions. Codespaces therefore belongs to GitHub’s development-environment capabilities rather than its project-management, communication, or release-management features.

Question 239

What does GitHub’s repository insights area help users examine?

1. Repository activity and usage information
2. Personal device hardware specifications
3. External cloud invoices
4. Local operating-system logs

Correct Answer: 1

Explanation:

Repository Insights provides information that can help users understand repository activity and usage patterns. Depending on available permissions and repository configuration, insights can include information related to traffic, contributions, activity, and other repository-level measurements. This information can help maintainers understand how a project is being used and how development activity changes over time. Insights do not provide personal computer hardware specifications, external cloud invoices, or local operating-system logs because those belong to systems outside the repository.

Question 240

Which Git command removes selected untracked files from the working directory?

1. git show
2. git clean
3. git annotate
4. git reflog

Correct Answer: 2

Explanation:

The git clean command can remove untracked files and directories from a working directory according to the options supplied. Because the operation can permanently remove files that are not tracked by Git, developers should review what will be affected before executing it, especially when using more aggressive options. git show displays information about Git objects, git annotate provides line-level history information, and git reflog records updates to references. Git clean is therefore primarily a workspace-cleanup command rather than a history or inspection tool.