Zum Inhalt springen

Answers to the GitHub Foundation Quiz

1. What folder is the definition files stored in when creating custom issue forms?

github/ISSUE_TEMPLATE

2. How are commits related to pull requests?

Commits are made on a branch that can have a linked pull request.

3. GitHub Teams offers (vs Free):

authentication with SAML single sign-on and increased GitHub Actions minutes.

4. GitHub Actions workflows distinctive features (Choose two):

built using YAML syntax
stored in the github/workflows directory in a GitHub repository

5. Access to a private repo’s Wiki:

Wikis can be viewed by the same people who have Read access to the repository.

6. Purpose of a GitHub repository:

to provide a collaborative space where developers can share and manage code files, track changes, and store revision history

7. Primary goal of GitHub’s community:

facilitating collaboration and creativity

8. Codespaces lifecycle (Choose three):

Create
Delete
Rebuild

9. Pull request statuses (Choose four):

open
closed
merged
draft

10. To view pre-built visualizations from repo data:

Insights

11. GitHub Actions restrictions from Org settings (Choose three):

Allow actions created by GitHub.
Allow specified actions.
Allow actions by Marketplace verified creators.

12. GitHub Pages:

webpages hosted and published through GitHub repositories

13. Search issues in organization „Avocado“:

Enter query org: Avocado label: guacamole "404 error" in the search bar. Select "Issues" in the "Filter by" section.

14. Workflows can reference actions in (Choose three):

any public repository
the same repository as your workflow file
a published Docker container image on Docker Hub

15. GitHub Actions workflows can be triggered by (Choose three):

creating an Issue
pushing to a GitHub repository
creating a new repository

16. GitHub Copilot:

an AI pair programmer that offers autocomplete-style suggestions

17. Receiving updates about activity:

by customizing the types of notifications you will receive in the future

18. GitHub Projects vs Classic (Choose two):

GitHub Projects has multiple layout views.
GitHub Projects has Insights.

19. Improving discoverability (Choose two):

Add topics to classify the repository.
Create a README file describing the repository.

20. Purpose of creating a new branch:

to experiment with new features or fixes

21. Create public gist based on another user’s gist:

Fork the gist.

22. Info available by default in profile:

public Secure Shell Protocol (SSH) keys

23. Secret gists:

Anyone with the URL for the gist can view the gist.

24. Multiple README files—first displayed one is in:

root

25. Label used to request help:

help wanted

26. Copilot for Business advantages (Choose three):

blocks suggestions matching public code
organization-wide policy management
support for organization or enterprise GitHub accounts

27. Defining features of Git:

distributed version control, open source software, and being designed for handling projects of any size with efficiency

28. What is a branch in Git:

a pointer to an identical snapshot of the project at a specific point in time

29. What is GitHub:

a cloud-based hosting service for version control and collaboration, focused on creating a safe and collaborative environment for developers

30. Advantages of saved replies (Choose two):

Saved replies allow you to create a reusable response to issues and pull requests.
Saved replies are tied to a GitHub user's personal account.

31. Qualifier to find issues mentioning a user:

mentions:

32. Where to discover, browse, and install tools:

GitHub Marketplace

33. Highlight post on Discussions page:

Pin the discussion.

34. Best describes a Codespace:

a development environment hosted in the cloud

35. GitHub Desktop can perform:

adding and cloning repositories

36. „Pinned Repositories“ in user profile:

repositories that were personally selected to be highlighted

37. Finding GitHub-approved vendor action (Choose two):

Confirm that the action has a verification badge.
Search the GitHub Marketplace for Actions by the vendor.

38. Customize in Codespace (Choose three):

shell
default editor
name

39. Default Discussion category:

show and tell

40. Funding new contributors via GitHub Sponsors:

after setting up a sponsored developer profile.

41. Who can be assigned to an issue or PR? (Choose two):

anyone with write permissions to the repository
anyone who has a personal GitHub account

42. Purpose of GitHub Sponsors:

It allows the developer community to financially support open source projects.

43. Markdown is a:

markup language

44. 2FA methods (Choose three):

security keys
authenticator app
GitHub mobile

45. CODEOWNERS file purpose:

sets the reviewers for pull requests automatically

46. What is a gist:

git repository

47. From a discussion post, user can:

Create an issue from the discussion.

48. Innersource development practice:

sharing code between teams within the organization

49. Why deploy from feature branch before merging:

to ensure the changes are verified and validated in a production environment

50. GitHub Desktop vs github.com:

offers a graphical user interface.

51. GitHub syntax format consistency:

# This is a heading

52. Codespace inactivity after 30 minutes:

time out.

53. Always true about Alpha/Beta preview features:

Alpha features are documented.

54. Pre-defined repository roles (Choose three):

Triage
Write
Maintain

55. Valid file states in git (Choose three):

staged
committed
modified

56. Reasons to fork a repository (Choose two):

to create a new repository based on an existing one
to propose changes to the base repository

57. Distributed version control system:

ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata.

58. Key characteristic of GitHub Projects:

ability to create and customize multiple views

59. GitHub Mobile can perform:

managing notifications from github.com

60. Minimum access to contribute to a repository:

Write

61. Auto-subscribe scenarios (Choose three):

opening a pull request or issue
commenting on a thread
being assigned to an issue or pull request

62. Cloning a repository:

It creates a copy of the repository on your local machine.

63. GitHub Projects layouts (Choose three):

Board
Table
Roadmap

64. Org member vs outside collaborator:

Organization base permissions do not apply to outside collaborators.

65. Purpose of a security policy:

to describe how security vulnerabilities should be responsibly disclosed

66. Identify a GitHub Projects template:

Use the is: template filter in the search text box.

67. Benefit of GitHub Enterprise Cloud with EMU:

It provides centralized control and streamlined management of user accounts through their identity provider (IdP).

68. Best feature for long-form documentation:

Wikis

69. Benefits of issue templates (Choose two):

to provide an easy-to-fill-out form for creating new issues
to automatically label or assign newly created issues

70. Feature used to merge changes:

pull requests

71. GitHub flow:

a lightweight workflow that allows for safe experimentation with new ideas and collaboration on projects through branching, pull requests, and merging

72. Create repository template – permissions:

With Admin permissions, navigate to Repository settings and select Template Repository.

73. Key focus areas of GitHub (Choose three):

building a technology platform for secure code sharing and collaboration
providing access and opportunities for developers
nurturing a community

74. What are the key areas of focus for GitHub? (Choose three.)

building a technology platform for secure code sharing and collaboration
providing access and opportunities for developers
nurturing a community of developers around shared projects

75. How can a user create a repository template, and what permissions are required?

With Admin permissions, navigate to Repository settings and select Template Repository

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert