{"id":18955,"date":"2026-09-22T11:01:06","date_gmt":"2026-09-22T11:01:06","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=18955"},"modified":"2026-09-22T11:01:06","modified_gmt":"2026-09-22T11:01:06","slug":"microsoft-gh-200-practice-test-questions-and-exam-dumps-part10-q181-200","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-gh-200-practice-test-questions-and-exam-dumps-part10-q181-200\/","title":{"rendered":"Microsoft GH-200 Practice Test Questions and Exam Dumps Part10 Q181-200"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/gh-200-exam-dumps\"><b>Microsoft GH-200 Exam Dumps<\/b><\/a><b> and Practice Test Dumps<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 181<\/b><\/h3>\n<p><b>Which GitHub feature provides a visual board for tracking work items?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Projects<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Releases<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Pages<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Packages<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">GitHub Projects provides a flexible planning interface for organizing and tracking work. Teams can use project views to manage issues, pull requests, and other work items through tables, boards, or other supported layouts. This makes Projects useful for planning development tasks, monitoring progress, and coordinating work across repositories. Releases are intended for distributing versions of software, Pages provides website hosting, and Packages stores and distributes software packages. Projects therefore focuses on planning and work management rather than publishing or hosting artifacts.<\/span><\/p>\n<h3><b>Question 182<\/b><\/h3>\n<p><b>Which Git command creates a new local branch from the current commit?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">git restore<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">git switch -c<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">git stash<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">git revert<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The git switch -c command creates a new branch and switches the working directory to that branch. It is useful when starting development from the current commit without modifying the existing branch. git restore is primarily used to restore file contents, git stash temporarily stores uncommitted changes, and git revert creates a new commit that reverses the effects of an earlier commit. Understanding these commands helps developers manage branches and working changes safely while using Git repositories connected to GitHub.<\/span><\/p>\n<h3><b>Question 183<\/b><\/h3>\n<p><b>Which GitHub repository file defines how Dependabot groups dependency updates?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.github\/dependabot.yml<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.github\/CODEOWNERS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.github\/ISSUE_TEMPLATE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.github\/PULL_REQUEST_TEMPLATE.md<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The .github\/dependabot.yml file contains Dependabot configuration for supported package ecosystems and update behavior. Its configuration can define update schedules, package directories, version-update behavior, and grouping rules. CODEOWNERS identifies responsible reviewers for specific repository paths. Issue templates guide users when creating issues, while pull request templates provide standardized content for pull request descriptions. Keeping Dependabot configuration in its expected location allows GitHub to recognize and apply the defined dependency-update settings automatically.<\/span><\/p>\n<h3><b>Question 184<\/b><\/h3>\n<p><b>Which GitHub capability automatically assigns reviewers based on repository file ownership?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Milestones<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Labels<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CODEOWNERS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Discussions<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">CODEOWNERS allows a repository to define individuals or teams responsible for specific files and directories. When configured correctly, GitHub can use those ownership rules to request reviews from the appropriate people when pull requests modify matching paths. This helps distribute review responsibilities according to project ownership. Milestones group issues and pull requests around goals or deadlines, labels categorize work items, and Discussions provide a conversational space. CODEOWNERS is therefore the repository feature specifically designed for path-based review responsibility.<\/span><\/p>\n<h3><b>Question 185<\/b><\/h3>\n<p><b>Which GitHub security feature identifies accidentally committed credentials?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dependency graph<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Secret scanning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repository insights<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Project views<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Secret scanning helps detect credentials and other sensitive tokens that may have been committed to repositories. Depending on the configuration and supported secret types, GitHub can identify exposed credentials and provide alerts so maintainers can investigate and respond. The dependency graph focuses on software dependencies, repository insights provide repository activity and metrics, and project views support work management. Secret scanning is particularly important because credentials accidentally committed to source control can create significant security exposure if they remain active.<\/span><\/p>\n<h3><b>Question 186<\/b><\/h3>\n<p><b>Which GitHub Actions feature lets a job execute inside a specified Docker container?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">container<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">permissions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">services<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">defaults<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The container keyword allows a GitHub Actions job to execute within a specified Docker container. This can provide a consistent execution environment with predefined operating-system packages, tools, and runtime dependencies. Containerized jobs are useful when builds or tests require a predictable environment that differs from the default runner configuration. The services keyword is used for supporting service containers, permissions controls token access, and defaults establishes default settings such as shell or working-directory behavior. The container property therefore directly controls the primary execution environment for a containerized job.<\/span><\/p>\n<h3><b>Question 187<\/b><\/h3>\n<p><b>Which GitHub API mechanism is commonly used to authenticate an application acting on behalf of a GitHub App installation?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repository password<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Installation access token<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Git commit hash<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Workflow artifact<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A GitHub App can obtain an installation access token to authenticate API requests made on behalf of a particular installation. The token is scoped according to the permissions granted to that GitHub App installation and is generally more targeted than using broad personal credentials. A commit hash identifies a Git object rather than authenticating an API request. Workflow artifacts are generated files, and repository passwords are not the standard mechanism for GitHub App API authentication. Installation access tokens therefore provide application-specific authorization for interacting with resources available to the installation.<\/span><\/p>\n<h3><b>Question 188<\/b><\/h3>\n<p><b>Which GitHub Actions setting controls the maximum execution time of a job?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">continue-on-error<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">fail-fast<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">timeout-minutes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">max-parallel<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The timeout-minutes setting establishes the maximum number of minutes a GitHub Actions job may run before GitHub terminates it. This helps prevent jobs from consuming runner resources indefinitely because of stalled commands or unexpected conditions. continue-on-error controls whether certain failures are tolerated, fail-fast affects matrix behavior when a matrix job fails, and max-parallel limits concurrent matrix executions. Setting an appropriate timeout can improve workflow reliability and resource management, especially for jobs that interact with external services or execute potentially long-running operations.<\/span><\/p>\n<h3><b>Question 189<\/b><\/h3>\n<p><b>Which GitHub repository setting controls who can directly push to a protected branch?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Branch protection configuration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Issue label settings<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Release metadata<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Discussion categories<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Branch protection configuration can restrict direct pushes to protected branches and enforce additional requirements before changes are integrated. Depending on the configured rules, repositories can require pull requests, reviews, status checks, or other controls. These protections are commonly applied to important branches where uncontrolled direct changes could disrupt development or deployment processes. Issue labels organize work items, release metadata describes published versions, and Discussion categories organize conversational content. Branch protection is therefore the relevant mechanism for controlling direct modification of protected branches.<\/span><\/p>\n<h3><b>Question 190<\/b><\/h3>\n<p><b>Which GitHub Actions component is designed to run database services alongside a job?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Matrix dimensions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Service containers<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repository variables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Workflow inputs<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Service containers provide additional containerized services that a GitHub Actions job can interact with during execution. Common examples include databases, caches, or other supporting services required by integration tests. The primary job container or runner executes the workflow steps, while service containers provide auxiliary processes accessible during the job. Matrix dimensions create multiple job variations, repository variables provide configuration values, and workflow inputs supply values to manually triggered or reusable workflows. Service containers are particularly useful for automated integration testing that requires temporary infrastructure.<\/span><\/p>\n<h3><b>Question 191<\/b><\/h3>\n<p><b>Which GitHub command-line command displays information about the current repository?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">gh repo view<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">gh issue close<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">gh release delete<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">gh workflow disable<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The gh repo view command displays information about a GitHub repository through the GitHub CLI. It can be used to inspect repository details without navigating through the web interface. Other GitHub CLI commands target different operations: gh issue close closes an issue, gh release delete removes a release, and gh workflow disable disables a workflow. The GitHub CLI provides command-line access to many GitHub operations, making it useful for automation and developers who prefer terminal-based repository management.<\/span><\/p>\n<h3><b>Question 192<\/b><\/h3>\n<p><b>Which GitHub Actions feature allows commands to modify workflow behavior through special output syntax?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Git attributes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Workflow commands<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repository topics<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Git notes<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">GitHub Actions workflow commands allow steps to communicate special instructions to the runner through supported command syntax written to standard output. They can be used for tasks such as setting environment variables, creating annotations, grouping log output, or managing other workflow-related behavior. Git attributes control repository-specific Git behavior, repository topics help categorize repositories, and Git notes attach additional information to Git objects. Workflow commands are therefore specifically designed for communication between executing steps and the GitHub Actions runner.<\/span><\/p>\n<h3><b>Question 193<\/b><\/h3>\n<p><b>Which GitHub Actions action is commonly used to download repository contents onto a runner?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">actions\/upload-artifact<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">actions\/cache<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">actions\/checkout<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">actions\/github-script<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The actions\/checkout action retrieves repository content and makes it available in the workflow&#8217;s workspace. It is commonly placed near the beginning of build, test, and analysis jobs because subsequent commands often need access to source files. actions\/upload-artifact stores generated files, actions\/cache manages reusable cached data, and actions\/github-script enables JavaScript-based interaction with GitHub APIs. Checking out repository content is therefore a separate task from artifact storage, caching, or API automation.<\/span><\/p>\n<h3><b>Question 194<\/b><\/h3>\n<p><b>Which GitHub feature lets maintainers define standardized pull request description content?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pull request template<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repository environment<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Deployment rule<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Security advisory<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A pull request template provides predefined content that appears when contributors create a new pull request. Teams can use templates to request information such as testing details, implementation summaries, issue references, or deployment considerations. This encourages consistent pull request descriptions and can make reviews easier to organize. Repository environments manage deployment-related settings, deployment rules control environment access or protection, and security advisories communicate vulnerability information. Pull request templates therefore focus specifically on standardizing the information supplied with new pull requests.<\/span><\/p>\n<h3><b>Question 195<\/b><\/h3>\n<p><b>Which GitHub Actions expression function checks whether a string contains another value?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">join()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">contains()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">hashFiles()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">fromJSON()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The contains() expression function tests whether a specified value contains another value. It can be useful in workflow conditions when execution should depend on text or collection contents. For example, a workflow may use it to check whether a branch name, event-related value, or other expression result contains a particular string. join() combines array values, hashFiles() calculates a hash from matching files, and fromJSON() converts JSON-formatted data into an expression object. Choosing the correct expression function allows workflows to implement precise conditional behavior.<\/span><\/p>\n<h3><b>Question 196<\/b><\/h3>\n<p><b>Which GitHub feature publishes a static website directly from repository content?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Codespaces<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Actions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Pages<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Discussions<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">GitHub Pages provides hosting for static websites using content from GitHub repositories. It can be used for project documentation, personal sites, organizational pages, and other static web content. Depending on the configuration, a site can be published from a selected branch or through an automated deployment workflow. Codespaces provides cloud-based development environments, Actions automates repository workflows, and Discussions supports community conversations. GitHub Pages is therefore the GitHub capability specifically designed to publish static web content.<\/span><\/p>\n<h3><b>Question 197<\/b><\/h3>\n<p><b>Which GitHub Actions setting limits how many matrix jobs can run concurrently?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">max-parallel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">timeout-minutes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">working-directory<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">continue-on-error<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The max-parallel matrix setting limits the number of matrix jobs that can execute simultaneously. This can help control runner consumption and avoid placing excessive load on external services used during testing. A matrix may generate many job combinations, but limiting parallel execution allows workflow authors to balance speed against available resources. timeout-minutes controls job duration, working-directory changes the directory used by commands, and continue-on-error changes failure handling. Therefore, max-parallel is the setting directly associated with controlling concurrent matrix execution.<\/span><\/p>\n<h3><b>Question 198<\/b><\/h3>\n<p><b>Which GitHub security feature analyzes source code for potential vulnerabilities?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dependabot version updates<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Code scanning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repository archiving<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Pages<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Code scanning analyzes repository source code to identify potential security vulnerabilities and coding problems. GitHub code scanning can use CodeQL and other supported analysis approaches to examine code and generate alerts that maintainers can investigate. Dependabot version updates focus on updating dependencies, repository archiving makes a repository read-only for ongoing development purposes, and GitHub Pages hosts static websites. Code scanning therefore addresses vulnerabilities in source code itself, complementing dependency and secret security capabilities.<\/span><\/p>\n<h3><b>Question 199<\/b><\/h3>\n<p><b>Which GitHub Actions feature permits a workflow to receive parameters from its caller?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Artifact metadata<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Runner labels<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Workflow inputs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Commit signatures<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Workflow inputs allow reusable workflows or manually triggered workflows to receive defined parameter values. A reusable workflow can declare input names, types, and other supported properties, allowing calling workflows to supply configuration without duplicating workflow logic. This makes reusable automation more flexible because the same workflow can operate with different parameters. Artifact metadata describes stored workflow files, runner labels influence runner selection, and commit signatures provide information about commit authenticity. Workflow inputs therefore provide a structured way to pass caller-supplied values into workflow execution.<\/span><\/p>\n<h3><b>Question 200<\/b><\/h3>\n<p><b>Which GitHub feature provides a registry for storing container images and other packages?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Packages<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Projects<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Issues<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GitHub Wiki<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">GitHub Packages provides package hosting and distribution capabilities integrated with GitHub. It supports package formats including container images and can connect package management with repositories, workflows, and access controls. This makes it useful for storing artifacts that need to be consumed by development or deployment processes. GitHub Projects focuses on work planning, Issues tracks tasks and problems, and Wiki provides repository documentation. GitHub Packages is therefore the GitHub service specifically intended for hosting and managing software packages and container images.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft GH-200 Exam Dumps and Practice Test Dumps &nbsp; Question 181 Which GitHub feature provides a visual board for tracking work items? GitHub Projects GitHub Releases GitHub Pages GitHub Packages Correct Answer: 1 Explanation: GitHub Projects provides a flexible planning interface for organizing and tracking work. Teams can use project views to manage [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18955"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=18955"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18955\/revisions"}],"predecessor-version":[{"id":18956,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18955\/revisions\/18956"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=18955"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=18955"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=18955"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}