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

 

Question 341

Which GitHub feature lets administrators define rules across multiple repositories centrally?

1. Repository labels
2. Branch aliases
3. Team settings
4. Organization rulesets

Correct Answer: 4

Explanation:

Organization rulesets allow administrators to establish repository governance policies at an organizational level. Instead of configuring identical controls independently for every repository, administrators can apply rules consistently across multiple repositories that meet the selected scope. Rulesets can address areas such as branch or tag restrictions and can define enforcement behavior and bypass permissions. This centralized approach is useful when an organization wants consistent development controls while still allowing appropriate exceptions. Repository-level settings can continue to provide more specific controls where needed, but organization rulesets provide a broader governance mechanism for managing repositories at scale.

Question 342

Which GitHub repository feature can prevent accidental deletion of important branches?

1. Branch protection rules
2. Release permissions
3. Package policies
4. Issue templates

Correct Answer: 1

Explanation:

Branch protection rules can help prevent destructive actions against important branches. Depending on the configured rules, administrators can require reviews, status checks, or other conditions before changes are accepted. Protection can also restrict force pushes and branch deletion, helping preserve branches that represent production or other critical development states. These controls are useful because a branch can contain work that many contributors depend on. Rather than relying entirely on individual users to avoid dangerous operations, repository governance can enforce restrictions automatically.

Question 343

Which GitHub setting can require conversations to be resolved before a pull request merges?

1. Required deployments
2. Required conversation resolution
3. Required release approval
4. Required issue assignment

Correct Answer: 2

Explanation:

Required conversation resolution can make unresolved review conversations a condition that must be satisfied before a pull request can merge. This encourages teams to address review comments rather than leaving important discussions unresolved. When enabled as part of repository governance, the requirement becomes a merge condition alongside other configured protections. It does not determine whether a conversation exists or who participates in it; instead, it affects whether unresolved review discussions can block integration. This feature is particularly useful for teams that want review feedback to be explicitly addressed before code reaches a protected branch.

Question 344

What does a GitHub pull request template primarily provide?

1. A standard structure for new pull request descriptions
2. Automatic source-code compilation
3. A replacement for branch protection
4. A permanent release record

Correct Answer: 1

Explanation:

A pull request template provides a predefined structure that contributors can use when opening pull requests. It can remind authors to include information such as the purpose of a change, testing performed, related work, or special considerations. Templates improve consistency in pull request descriptions without enforcing technical merge requirements themselves. They are documentation and collaboration aids rather than substitutes for branch protection. A repository can combine templates with required reviews, status checks, and other governance controls to create a more consistent contribution process.

Question 345

Which GitHub issue feature provides structured fields when users submit specific issue types?

1. Repository variables
2. Issue forms
3. Branch forms
4. Commit schemas

Correct Answer: 2

Explanation:

GitHub issue forms provide structured templates for collecting information when users create certain types of issues. Unlike a simple free-form issue template, an issue form can define fields such as text inputs, dropdowns, checkboxes, and other structured elements. This helps maintainers collect the information needed to investigate bugs, requests, or operational problems. Structured submissions can reduce incomplete reports and make incoming issues easier to process consistently. Issue forms are therefore useful when a project needs contributors to provide specific information rather than relying entirely on an unstructured description.

Question 346

Which GitHub project feature allows information to be organized using selectable field values?

1. Project custom fields
2. Repository branches
3. Workflow artifacts
4. Commit references

Correct Answer: 4

Explanation:

GitHub Projects supports custom fields that can organize project items using structured values. Depending on the field type, teams can represent information such as status categories, priorities, dates, numbers, or selectable options. This provides more flexibility than relying only on issue labels. Custom fields can help teams build project views around the information they actually need to track. Because the data is structured, it can also support filtering, grouping, and sorting within project views. This makes custom fields useful for adapting GitHub Projects to different planning and tracking workflows.

Question 347

Which GitHub repository feature can automatically create a web page from repository content?

1. GitHub Pages
2. GitHub Discussions
3. GitHub Packages
4. GitHub Projects

Correct Answer: 1

Explanation:

GitHub Pages provides hosting for websites and project documentation from GitHub repositories. It can publish static content generated from repository files, making it useful for documentation sites, project pages, personal sites, and other static web content. The publishing configuration determines how the repository’s content becomes available as a website. GitHub Pages is separate from GitHub Packages, which focuses on package distribution, and GitHub Projects, which supports planning and tracking. Using Pages allows teams to keep website source content alongside their project repository.

Question 348

Which GitHub repository file commonly communicates contribution guidelines to project participants?

1. PROJECT.md
2. GUIDELINES.txt
3. CONTRIBUTING.md
4. COLLABORATORS.yml

Correct Answer: 3

Explanation:

A CONTRIBUTING.md file is commonly used to explain how people should contribute to a repository. It may describe development setup, coding expectations, testing procedures, branch practices, pull request requirements, or other project-specific instructions. Providing contribution guidance in the repository gives contributors a central reference before they submit changes. The file is documentation rather than an automated enforcement mechanism. Projects can combine contribution guidelines with templates, branch protections, automated checks, and review requirements to create a more predictable contribution process.

Question 349

Which GitHub repository document explains how users can obtain and use the project under its chosen terms?

1. LICENSE
2. OWNERS.md
3. VERSION.txt
4. ACCESS.md

Correct Answer: 1

Explanation:

A LICENSE file communicates the legal terms under which repository content may be used, modified, or redistributed. Choosing and documenting a license is important for projects whose maintainers want users to understand the permissions and obligations associated with the source code. A license is different from contribution guidelines, which describe how people should participate in development. It is also different from repository access controls, which determine who can interact with the repository itself. Including a clear license helps users understand the project’s intended usage conditions.

Question 350

Which GitHub repository file is commonly used to identify the project’s main documentation?

1. ABOUT.md
2. README.md
3. PROJECT_INFO.yml
4. DOCUMENTATION.ini

Correct Answer: 2

Explanation:

A README.md file is commonly used as the primary introductory documentation for a GitHub repository. It can explain what the project does, how to install or use it, how to contribute, and where to find additional information. GitHub displays README content prominently on repository pages, making it an important entry point for contributors and users. Although projects can maintain extensive documentation elsewhere, a well-structured README gives visitors immediate context. It can also contain links to setup instructions, examples, support resources, and other project materials.

Question 351

Which GitHub feature lets users discuss project ideas without treating every discussion as an issue?

1. Discussions
2. Releases
3. Environments
4. Artifacts

Correct Answer: 1

Explanation:

GitHub Discussions provides a space for community conversations that do not necessarily represent actionable software issues. Teams can use discussions for questions, ideas, announcements, polls, and broader project conversations. This separates general communication from issue tracking, where items are typically managed as work requiring attention or resolution. Discussions can therefore provide a more appropriate place for community interaction while allowing the issue tracker to remain focused on actionable tasks. The feature is especially useful for open-source projects and teams that need a structured communication area alongside code collaboration.

Question 352

Which GitHub repository capability stores software packages alongside their source-code ecosystem?

1. GitHub Wiki
2. GitHub Packages
3. GitHub Pages
4. GitHub Discussions

Correct Answer: 2

Explanation:

GitHub Packages is GitHub’s package hosting service for supported package formats. It allows organizations and developers to publish and manage packages associated with their software projects. Packages can be integrated into development and deployment workflows while access can be controlled using appropriate permissions. This differs from GitHub Pages, which hosts websites, and GitHub Wiki, which provides repository documentation. Using a package registry can simplify distribution of reusable libraries, modules, and other build artifacts while keeping package management connected to the development platform.

Question 353

Which GitHub repository option permanently prevents normal repository interaction after archival?

1. Repository archive
2. Repository rename
3. Repository transfer
4. Repository migration

Correct Answer: 1

Explanation:

Archiving a repository places it into a read-only state for normal development activity. This is useful when a project is no longer actively maintained but its history, issues, discussions, or documentation should remain available. Archiving communicates that the repository is preserved rather than actively developed. It is different from deleting a repository because archival retains the repository’s information. Administrators should therefore consider archival when a project needs to remain accessible for reference while preventing ordinary changes from continuing.

Question 354

Which GitHub setting determines whether a repository can be transferred to another owner?

1. Package visibility
2. Transfer eligibility
3. Issue configuration
4. Release status

Correct Answer: 2

Explanation:

Repository transfer eligibility concerns whether a repository can be moved from its current owner to another supported owner. Transfers can involve repositories moving between users or organizations, subject to GitHub’s applicable requirements and permissions. This is different from repository visibility, which controls access, and from release settings, which govern published software versions. Before transferring a repository, administrators should consider dependencies such as permissions, integrations, forks, and automation. Repository ownership affects how users and systems interact with the project, so transfer operations should be planned carefully.

Question 355

Which GitHub feature can automatically assign responsibility for selected repository files during review?

1. CODEOWNERS
2. Release owners
3. Project managers
4. Branch contacts

Correct Answer: 1

Explanation:

The CODEOWNERS mechanism identifies individuals or teams responsible for reviewing changes to specified areas of a repository. When configured appropriately, GitHub can request reviews from the listed owners when relevant files are modified. This helps route changes to people with knowledge of particular components. CODEOWNERS does not replace all branch protection requirements; instead, it can work with protected branches to require appropriate review. Organizations often use it to establish clear ownership boundaries across large repositories where different teams maintain different components.

Question 356

Which GitHub feature can require a deployment to complete before a protected branch accepts a change?

1. Required deployments
2. Repository labels
3. Package retention
4. Issue milestones

Correct Answer: 1

Explanation:

Required deployments can make successful deployment to a designated environment part of the conditions for integrating changes into a protected branch. This is useful when teams need evidence that code has passed a deployment stage before it can enter an important branch. Deployment requirements complement other protections such as reviews and status checks. The exact behavior depends on the repository’s environment and branch configuration. By connecting deployment state with branch governance, teams can incorporate operational validation into the process that controls changes to critical branches.

Question 357

Which GitHub Actions feature can expose values from one reusable workflow to its caller?

1. Workflow outputs
2. Runner labels
3. Environment URLs
4. Artifact names

Correct Answer: 1

Explanation:

Reusable workflows can define outputs that are returned to the workflow that calls them. This allows a reusable automation component to perform work and provide selected results back to the caller. For example, a reusable workflow might calculate a generated version, deployment identifier, or other value needed by later jobs. Outputs create a controlled data interface between workflows instead of requiring callers to reconstruct internal processing. This is particularly useful when organizations standardize common automation while still allowing individual repositories to consume results from that shared workflow.

Question 358

Which reusable workflow syntax allows a caller to pass all available secrets to the called workflow?

1. secrets: share
2. secrets: inherit
3. secrets: forward
4. secrets: export

Correct Answer: 2

Explanation:

The secrets: inherit syntax allows a calling workflow to make its available secrets accessible to a called reusable workflow when the supported organizational or repository relationship permits it. This can simplify reusable workflow configuration when multiple secrets are required. However, secret inheritance should be used carefully because it can expose more credentials than a workflow actually needs. Explicitly passing only required secrets can provide tighter control. Understanding how secrets cross reusable workflow boundaries is therefore important when designing secure, reusable automation.

Question 359

Which GitHub Actions trigger lets another workflow start after a specified workflow completes?

1. workflow_run
2. workflow_after
3. workflow_complete
4. workflow_chain

Correct Answer: 1

Explanation:

The workflow_run event allows one workflow to respond to the completion or activity of another workflow run. This can support multi-stage automation where separate workflows handle different phases of a process. For example, one workflow may perform testing while another performs a later operation based on the first workflow’s result. Because workflow chaining can involve credentials and permissions, security considerations are important when deciding what actions the downstream workflow should perform. The event provides a way to connect automation without placing every stage into one large workflow file.

Question 360

Which GitHub Actions permission controls the ability to read repository contents?

1. contents: read
2. repository: view
3. source: read
4. code: inspect

Correct Answer: 1

Explanation:

The contents: read permission grants a workflow read access to repository contents through the GitHub Actions permission model. It is commonly needed when automation checks out source code or interacts with repository files through supported GitHub interfaces. Permissions should be granted according to the workflow’s actual requirements rather than broadly enabling write capabilities. Separating read and write access supports the principle of least privilege. A workflow that only needs to inspect or retrieve source code generally does not require permission to modify repository contents.