Microsoft GH-900 Exam With Confidence Using Practice Dumps

When multiple README files exist in different locations within a GitHub repository, the README.md file located in the root directory of the repository will be displayed first by default. This file serves as the main documentation for the repository and is automatically rendered on the repository's home page.

Root Directory:

Option C is correct because the README.md file in the root directory is prioritized and displayed first on GitHub. This is the standard behavior for how GitHub presents documentation.

Incorrect Options:

Option A (.github) is incorrect because while a README.md file in the .github directory might be used for certain configurations, it is not the first to be displayed.

Option B (/src) is incorrect because the README.md in the src directory is not prioritized over the root.

Option D (/docs) is incorrect because documentation in the /docs folder is typically secondary to the root README.md.

The feature you can use to merge proposed changes in a repository on GitHub is Pull requests. Pull requests are a core feature of GitHub, allowing developers to propose changes to a codebase, review code, discuss the changes, and eventually merge them into the main branch. This collaborative workflow ensures that code is reviewed and vetted before becoming part of the project.

=================

The primary purpose of creating a security policy in a GitHub repository is to guide users and contributors on how to report security vulnerabilities in a responsible and secure manner. This policy outlines the preferred method of communication, timelines, and any other pertinent information related to handling security issues.

Security Policy:

Option C is correct because a security policy provides guidelines for responsibly disclosing security vulnerabilities. This helps maintainers respond to and address security concerns promptly and securely, thereby protecting the project and its users.

Incorrect Options:

Option A is incorrect because ensuring peer code review is a best practice for code quality, but it is not the primary purpose of a security policy.

Option B is incorrect because push protection for secrets is managed through repository settings, not the security policy.

Option D is incorrect because customizing Dependabot configuration is related to dependency management, not directly to security policies.