GitHub-Foundations GitHub Foundations Exam Practice Test

Answer : A

Markdown is a lightweight markup language with plain-text formatting syntax. It is designed to be easy to write and read in its raw form, and it can be converted into HTML and other formats. Markdown is commonly used for formatting readme files, writing messages in online discussion forums, and creating rich text documents.

Markup Language:

Option A is correct because Markdown is indeed a markup language. It is not a programming language, scripting language, version control system, or containerization solution.

Incorrect Options:

Option B is incorrect because Markdown is not a programming language; it does not involve control structures or variables.

Option C is incorrect because Markdown is not used for scripting or automation.

Option D is incorrect because Markdown does not manage version control.

Option E is incorrect because Markdown is not related to containerization technologies like Docker.

GitHub Docs: Basic writing and formatting syntax

Answer : C

A distributed version control system (DVCS) like Git is best described as a system that ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata. This decentralized approach allows developers to work independently, with full access to the project's history and files, and later synchronize their changes with others. Unlike centralized systems, DVCS does not rely on a single central server, which provides greater flexibility and robustness in collaboration.

Answer : B, D

Two recommended ways to improve the discoverability of a repository on GitHub are:

B . Create a README file describing the repository: A well-written README file provides essential information about the project, such as what it does, how to use it, and how to contribute. This is often the first thing potential users or contributors will see, making it critical for discoverability.

D . Add topics to classify the repository: Adding topics to your repository helps classify it under specific categories, making it easier for others to find it through GitHub's search and exploration features. Topics act like tags, helping to connect your project with users interested in similar subjects.

Registering a repository with GitHub search and adding labels are not applicable actions for improving discoverability in the broader sense.

Answer : C

When creating custom issue forms on GitHub, the definition files are stored in the .github/ISSUE_TEMPLATE folder. This directory is used to define issue templates and forms that help standardize the information collected when users open new issues in the repository. The .github folder is a special directory used for various repository configurations and workflows.

Answer : A

Secret gists on GitHub are 'unlisted' gists, meaning they are not publicly discoverable but can be viewed by anyone who has the URL.

Visibility of Secret Gists:

Option A is correct because secret gists can be viewed by anyone who has the direct URL, making them accessible yet unlisted.

Incorrect Options:

Option B is incorrect because secret gists do not require GitHub Enterprise; they are available on all GitHub accounts.

Option C is incorrect because secret gists do not appear on the gist Discover page.

Option D is incorrect because secret gists do not have an 'assigned access' feature; access is determined by sharing the URL.

GitHub Docs: About Gists

Answer : D

Pull requests are created to propose changes from one branch to another. These branches must be different; otherwise, there would be no changes to propose. Typically, pull requests are made from a feature or topic branch to a main branch (such as main or master), allowing for code review and integration before the changes are merged.

Answer : A

The qualifier mentions: is used in GitHub's search functionality to find issues that mention a certain user. For example, if you want to find all issues where a specific user is mentioned, you would use mentions:username. This helps in tracking where a user has been involved in discussions across issues or pull requests.