Question 1

What is the primary purpose of GitHub Pages, and in what scenarios would you typically use them?

Options :

A : GitHub Pages allow you to publish web pages directly from your repository, making them ideal for showcasing project documentation, a portfolio, or project-related content

B : GitHub Pages are meant for hosting and displaying the repository-s source code for public viewing

C : GitHub Pages allow you to run server-side scripts to enhance the functionality of a repository

D : GitHub Pages serve as a version control system for managing changes in a repository

Answer: A

Question 2

When reviewing a pull request on GitHub, what is the purpose of the "Files changed" tab?

Options :

A : the "Files changed" tab shows a list of commits

B : the "Files changed" tab organizes files in descending order based on commit time

C : the "Files changed" tab reveals the proposed changes as they would appear post-merge

D : the "Files changed" tab displays the entire commit history

Answer: C

Question 3

You are participating in a GitHub discussion where comments have been made in response to a question. You've received a helpful response and want to highlight the comment to allow visitors to find the answer quickly. What action should you take?

Options :

A : lock the discussion so it remains the last answer of the discussion

B : create an issue and link the discussion

C : mark the comment as the answer to the discussion

D : instruct users to use discussion insights to find the answer

Answer: C

Question 4

What marks the beginning of a Codespace's lifecycle?

Options :

A : The lifecycle starts with the creation of a repository and ends with its deletion.

B : The lifecycle begins when GitHub is opened and ends upon software closure.

C : The lifecycle of a Codespace begins with the installation of necessary software and ends when the user logs out of their GitHub account.

D : The lifecycle starts with the creation of a Codespace and ends with its deletion.

Answer: D

Question 5

What option do contributors have regarding notifications for their pull request?

Options :

A : They can choose "Not subscribed," "Subscribed," or "Custom" for notifications on the thread, tailoring the level of notifications they receive.

B : Contributors can only receive notifications if they are @mentioned.

C : They must accept all notifications without filtering.

D : Notifications are disabled for pull requests to minimize distractions.

Answer: A

Free GitHub-Foundations Mock Exam – Practice Online Confidently

Buying Options: