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

 

Question 101

Which GitHub feature automates security analysis using CodeQL?

1. GitHub Advanced Security
2. GitHub Discussions
3. GitHub Projects
4. GitHub Pages

Correct Answer: 1

Explanation:

GitHub Advanced Security provides additional security capabilities for repositories, including code scanning with CodeQL, secret scanning, and dependency-related security features. CodeQL treats source code as data and allows security queries to identify patterns associated with vulnerabilities. This enables security analysis to become part of the development workflow rather than being performed only after software is released. Organizations can configure security analysis according to repository needs and supported languages. When integrated with pull requests, findings can provide developers with information about potential problems before changes are merged.

Question 102

Which GitHub token is automatically available to Actions workflows?

1. DEPLOY_TOKEN
2. GITHUB_TOKEN
3. ACTION_KEY
4. WORKFLOW_TOKEN

Correct Answer: 2

Explanation:

GITHUB_TOKEN is a special token that GitHub automatically provides to GitHub Actions workflows. It allows workflows to authenticate against GitHub APIs and perform supported repository operations according to its configured permissions. The token is scoped to the repository and its access can be restricted using the workflow permissions setting. Using GITHUB_TOKEN avoids creating a separate personal access token for many common automation tasks. Its permissions should still be minimized because excessive access could increase the impact of a compromised or incorrectly configured workflow.

Question 103

Which GitHub feature stores reusable repository automation definitions?

1. Actions
2. Discussions
3. Milestones
4. Projects

Correct Answer: 1

Explanation:

GitHub Actions provides the automation framework used to define workflows, jobs, and reusable automation components. Workflow files are commonly stored in the .github/workflows directory and can respond to repository events, schedules, manual execution, or other supported triggers. Actions themselves can package reusable functionality that workflows consume. This ecosystem allows development teams to automate testing, validation, packaging, deployment, and administrative processes. Keeping automation definitions in source control also makes workflow changes reviewable and versioned alongside the repository code they operate on.

Question 104

Which GitHub mechanism allows automation to authenticate as an application?

1. SSH deploy key
2. Personal access token
3. GitHub App
4. Repository password

Correct Answer: 3

Explanation:

A GitHub App provides an application-based identity that can authenticate to GitHub and receive specifically defined repository or organization permissions. GitHub Apps are useful for integrations and automation that need controlled access without relying on an individual developer’s personal identity. Installation-based permissions can limit which repositories and resources an application can access. This model can provide clearer ownership and lifecycle management for organizational automation. Compared with personal access tokens, GitHub Apps are designed around an application identity and granular permissions, making them suitable for many service-to-service integrations.

Question 105

Which credential type is commonly used for Git operations over SSH?

1. SSH key
2. Webhook secret
3. Environment variable
4. Issue token

Correct Answer: 1

Explanation:

An SSH key pair can authenticate Git operations when a repository is accessed through an SSH URL. The private key remains with the user or automation system, while the corresponding public key is registered with GitHub or configured for an appropriate deployment scenario. SSH authentication can be useful for automated systems that need Git access without interactive password entry. Keys should be protected carefully because possession of an authorized private key can provide the permissions associated with that key. For automation, teams should use narrowly scoped credentials appropriate to the required repository operations.

Question 106

Which GitHub feature sends HTTP requests when repository events occur?

1. Repository rules
2. Webhooks
3. Commit signatures
4. Issue forms

Correct Answer: 2

Explanation:

GitHub webhooks send HTTP requests to an external endpoint when selected GitHub events occur. They can be configured for events such as pushes, pull requests, issues, releases, and other supported activities. The receiving application can then process the event and perform external automation. Webhooks are useful when an integration needs near-real-time notifications without repeatedly polling GitHub. A webhook should be protected appropriately, commonly by validating its configured secret or signature mechanism. Event selection should also be limited to information the receiving service actually needs.

Question 107

Which GitHub object represents a versioned project snapshot?

1. Commit
2. Issue
3. Discussion
4. Deployment

Correct Answer: 1

Explanation:

A Git commit represents a versioned snapshot of changes in a repository. It records information such as the tree of tracked files, parent commit references, author information, and commit metadata. Commits form the history used by Git to track how a project changes over time. Branches and tags can reference particular commits, while pull requests commonly organize proposed changes that eventually become commits in repository history. Understanding commits is fundamental to GitHub because many repository operations, automation triggers, and development workflows ultimately operate around commit references.

Question 108

Which GitHub feature groups work items into an organized planning space?

1. Releases
2. GitHub Projects
3. Packages
4. Codespaces

Correct Answer: 2

Explanation:

GitHub Projects provides a planning and tracking environment for organizing work items. Projects can incorporate issues and pull requests and arrange them using views such as tables, boards, or roadmaps depending on the configured project capabilities. Teams can use fields, filters, and grouping to organize work according to their development process. This differs from GitHub Issues, which represent individual work items or discussions, while Projects provide a broader planning structure across multiple items. Proper project configuration can help teams visualize priorities, progress, and workflow states.

Question 109

Which GitHub feature creates a browser-based development environment?

1. Codespaces
2. Discussions
3. Packages
4. Wikis

Correct Answer: 1

Explanation:

GitHub Codespaces provides cloud-hosted development environments that can be accessed through a browser or supported development tools. A codespace can be configured with project-specific tools, dependencies, extensions, and development settings, helping contributors work in a consistent environment. Configuration can be customized through repository development-container files. Codespaces are different from GitHub Actions runners because a codespace is primarily an interactive development environment, while Actions runners execute automated workflow jobs. Using standardized development environments can reduce setup differences between contributors and simplify onboarding for complex projects.

Question 110

Which configuration file customizes a GitHub Codespace environment?

1. codespace.json
2. devcontainer.json
3. environment.json
4. workspace.yml

Correct Answer: 4

Explanation:

The devcontainer.json configuration file defines development-container settings that can be used by GitHub Codespaces and compatible development-container environments. It can specify items such as the base image, features, extensions, commands, and other development environment settings. Storing this configuration in the repository allows teams to describe a repeatable development environment alongside their source code. This helps contributors create consistent environments without manually installing every required tool. The configuration can be adapted as project dependencies and development requirements change.

Question 111

Which GitHub feature packages repository documentation collaboratively?

1. GitHub Wiki
2. GitHub Packages
3. GitHub Actions
4. GitHub Releases

Correct Answer: 2

Explanation:

GitHub Wiki provides a repository-associated space for maintaining collaborative documentation. Teams can use wiki pages for guides, architectural notes, operational information, and other documentation that may not belong directly in the repository’s source tree. Wiki content is maintained separately from normal repository files while remaining associated with the project. This differs from GitHub Packages, which hosts software packages and container images. Choosing the right documentation location depends on whether information is intended to live alongside source code, in repository documentation, or in a collaboratively maintained wiki.

Question 112

Which GitHub capability attaches files to a published release?

1. Release assets
2. Issue attachments
3. Project resources
4. Workflow bundles

Correct Answer: 3

Explanation:

GitHub Releases can include release assets associated with a particular published release. These assets can include compiled binaries, archives, installers, or other files that users need to obtain a specific version of software. Releases are typically associated with Git tags, allowing users to identify the source version represented by the release. Release assets differ from workflow artifacts, which are generally associated with workflow runs and their generated outputs. A release is therefore useful when distributing stable, versioned software to users or downstream consumers.

Question 113

Which GitHub feature automatically summarizes repository security risks?

1. Security overview
2. Project roadmap
3. Repository wiki
4. Release dashboard

Correct Answer: 4

Explanation:

GitHub’s security-related views and overviews can provide organizations and repository administrators with information about configured security capabilities and identified risks. Depending on the GitHub plan and enabled features, security information can include alerts from code scanning, secret scanning, and dependency-related analysis. These views help teams understand the security state of repositories and identify areas that may require attention. Security reporting should be interpreted alongside the underlying alerts and repository configuration rather than treated as a substitute for reviewing individual findings.

Question 114

Which GitHub feature lets users discuss repository-wide questions?

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

Correct Answer: 1

Explanation:

GitHub Discussions provides a space for community or team conversations that do not necessarily represent actionable issues. Discussions can be used for questions, ideas, announcements, polls, and broader conversations around a repository. This separates open-ended collaboration from GitHub Issues, which are generally more suited to trackable bugs, tasks, or feature requests. Repository administrators can configure whether Discussions are enabled. A clear distinction between discussions and issues can help maintain an organized development process while still providing contributors with a place to exchange information.

Question 115

Which GitHub feature provides structured forms for new issues?

1. Issue templates
2. Issue forms
3. Project fields
4. Discussion forms

Correct Answer: 3

Explanation:

GitHub issue forms provide structured interfaces for collecting specific information when users create issues. Forms can request predefined fields such as descriptions, environment details, reproduction information, or other project-specific data. This can improve the consistency and usefulness of submitted reports compared with relying entirely on free-form text. Issue forms are configured using YAML definitions in the repository’s configuration area. They are different from traditional issue templates because forms can provide structured input controls. Teams can use them to guide contributors toward providing information required for effective triage.

Question 116

Which GitHub feature manages planned work through custom fields?

1. GitHub Projects
2. GitHub Wiki
3. GitHub Pages
4. GitHub Releases

Correct Answer: 1

Explanation:

GitHub Projects supports custom fields that can be used to organize and track work according to project-specific requirements. Fields can represent values such as status, priority, dates, teams, or other planning information. Projects can combine these fields with issues and pull requests to create tailored planning views. This makes Projects different from basic repository issue lists because teams can construct broader workflows around structured project data. Custom fields are particularly useful when a team needs planning information that does not fit into GitHub’s standard issue metadata.

Question 117

Which GitHub service hosts static websites directly from repositories?

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

Correct Answer: 2

Explanation:

GitHub Pages is a hosting service for publishing static websites from GitHub repositories. It can be used for project documentation, personal sites, technical guides, and other static web content. Depending on the configuration, a Pages site can be built from repository content and published through an associated Pages deployment process. GitHub Pages is different from GitHub Wiki, which provides repository documentation pages, and GitHub Packages, which hosts software packages. Pages is particularly useful when a project needs a publicly accessible static site closely connected to repository content.

Question 118

Which GitHub feature verifies commit authorship cryptographically?

1. Commit signing
2. Repository labels
3. Issue locking
4. Branch naming

Correct Answer: 1

Explanation:

Commit signing allows GitHub to associate a cryptographic signature with a Git commit, helping verify that the commit was signed by the expected identity. Supported signing methods can provide additional assurance around authorship and integrity. Organizations may use signed commits as part of their repository governance or branch protection policies. Signing does not by itself determine whether the code is secure or correct; it provides information about the authenticity of the commit signature. Teams should therefore treat commit verification as one control within a broader development security process.

Question 119

Which GitHub capability helps review dependency changes in pull requests?

1. Dependency review
2. Repository archive
3. Release comparison
4. Issue triage

Correct Answer: 4

Explanation:

Dependency review helps identify changes to dependencies introduced by a pull request and can provide information about associated security or licensing considerations depending on the available configuration. This allows teams to examine dependency changes before merging them into a repository. Dependency review complements tools such as Dependabot, which can propose dependency updates, and code scanning, which analyzes source code. Reviewing dependency changes during pull requests can provide an additional checkpoint before new packages or versions become part of the project’s normal dependency set.

Question 120

Which GitHub feature allows repositories to be archived as read-only?

1. Repository archive
2. Repository locking
3. Project freeze
4. Source preservation

Correct Answer: 3

Explanation:

Archiving a GitHub repository places it into a read-only state and indicates that the repository is no longer actively maintained. Archived repositories can remain available for historical reference while preventing normal ongoing development activity. Archiving can be useful for completed projects, obsolete experiments, or repositories retained for historical purposes. It is different from deleting a repository because archived content remains accessible according to the repository’s visibility and access settings. Before archiving, teams should consider whether active automation, dependencies, integrations, or users still rely on the repository.