Question 1

Which of the following is NOT a characteristic of a forked repository?

Options :

A : Forks are often used when a user does not have write access to the upstream repository

B : Developers can use forks to propose changes related to fixing a bug

C : A GitHub fork is automatically kept in sync with the original repository

D : A fork is a new repository that shares code and visibility settings with the original “upstream” repository.

Answer: C

Question 2

Which of the following aspects distinguishes Projects Classic from Projects?

Options :

A : Projects Classic provides a simpler and more streamlined project management experience

B : Projects Classic is designed exclusively for open-source projects

C : Projects Classic uses a different version control system than Projects

D : Projects has limited integration capabilities compared to Projects Classic

Answer: A

Question 3

What are helpful topics to include to classify a GitHub repository? (select three)

Options :

A : language

B : license

C : subject area

D : repository-s intended purpose

Answer: A,C,D

Question 4

When using GitHub Actions, what is the proper order of operations when a pull request is opened?

Options :

A : Action ➞ Steps ➞ Job ➞ Workflow ➞ Event

B : Event ➞ Workflow ➞ Job ➞ Steps ➞ Action

C : Action ➞ Steps ➞ Workflow ➞ Event ➞ Job

D : Workflow ➞ Event ➞ Steps ➞ Job ➞ Action

Answer: B

Question 5

While there are default labels for each new repository, what can an organization do to further categorize their issues, pull requests, and discussions based on their needs?

Options :

A : change the name of a default label since there is a limit on the amount of labels a project can have

B : use an external source to import custom labels since there is no option to create custom labels

C : there is nothing a user can do, they are limited to using the default labels

D : create custom labels in their project

Answer: D