GitHub Foundations GH-900: Modern Development

Topic snapshot

Sample questions

These questions are original IT Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.

Question 1

Topic: Apply Modern Development Practices

A documentation contributor opens a repository in the browser to make a quick Markdown fix and review files without setting up a full development environment. The team does not need a preconfigured cloud workspace, terminal, or long-running environment.

Which GitHub concept best explains this scenario?

Options:

• A. GitHub Desktop

• B. GitHub Codespaces

• C. github.dev

• D. GitHub Actions

Best answer: C

Explanation: This scenario describes lightweight, in-browser editing for a small repository change. That fits github.dev, not Codespaces, because the team does not need a full cloud development environment with terminal access and workspace setup.

The core distinction is lightweight editing versus a full development environment. github.dev is designed for quick browser-based file edits and repository review, which matches a simple Markdown update. Codespaces is a cloud development environment intended for fuller development tasks, often with more tooling and setup than this scenario requires.

A good rule of thumb is:

• Use github.dev for fast browser editing.
• Use Codespaces when you need a complete cloud workspace.

The presence of a quick file change and the absence of terminal or environment needs point to the lightweight option.

• Codespaces mismatch describes a full cloud development environment, which the scenario explicitly says is unnecessary.
• Actions mismatch automates workflows such as build or test tasks rather than providing an editing surface.
• Desktop mismatch is a local application, not the lightweight browser-based experience described here.

Question 2

Topic: Apply Modern Development Practices

A new contributor needs to fix a bug in a GitHub repository from a company-managed laptop where they cannot install development tools. The repository already includes .devcontainer/devcontainer.json, and they need a full cloud-based development environment tied to that repository. What is the best next step?

Options:

• A. Open the repository in GitHub Codespaces

• B. Clone the repository locally with Git and install tools manually

• C. Open the repository in github.dev for the full environment

• D. Change the repository visibility to public before editing

Best answer: A

Explanation: GitHub Codespaces is the best fit when someone needs a ready-to-use development environment without installing tools locally. Because it is associated with the GitHub repository and can use the existing dev container configuration, it provides the full cloud development setup the scenario requires.

GitHub Codespaces provides a cloud development environment connected to a GitHub repository. In this scenario, the contributor cannot install tools on the laptop, so a local clone is not a good next step. The existing .devcontainer/devcontainer.json file is another clue that the repository is prepared to define the environment for Codespaces.

A good way to think about it is:

• GitHub repository stores the code and project context.
• Codespaces starts a cloud-hosted environment for that repository.
• The dev container configuration can predefine tools, settings, and dependencies.

github.dev is useful for lightweight browser editing, but it is not the full cloud development environment described here. Repository visibility settings also do not solve the need for a development environment.

• Local setup required: cloning with Git still depends on local tools and manual environment setup, which the scenario says is not possible.
• Wrong browser tool: github.dev is for lightweight editing, not a full Codespaces-style cloud development environment.
• Unrelated setting change: making the repository public changes who can see it, but it does not create a development environment.

Question 3

Topic: Apply Modern Development Practices

A new team member must investigate a bug in a repository. The project uses a preconfigured dev container and needs several tools and services to run correctly. Their laptop is locked down, so they cannot install software locally. They want a browser-based environment that matches the team’s setup.

What should they do next?

Options:

• A. Open the repository in github.dev

• B. Start a repository discussion about the bug

• C. Create a codespace for the repository

• D. Download the repository as a ZIP file

Best answer: C

Explanation: Codespaces is the better choice when someone needs a ready-to-use development environment in the browser. In this scenario, the repo already depends on a configured setup and the user cannot install tools locally, so a cloud environment is the right next step.

The key concept is that github.dev is mainly for lightweight browser editing, while Codespaces is for full development work in a configured cloud environment. Here, the repository requires tools and services to run properly, and the user cannot install anything on their laptop. That makes consistency and preconfiguration the deciding factors.

A good beginner rule is:

• Use github.dev for quick edits and code review.
• Use Codespaces when the project needs dependencies, runtimes, or a dev container.
• Use local tools only when installation is allowed and practical.

In this case, creating a codespace gives the user a browser-based environment that matches the repository’s expected setup. The lightweight editor is the closest distractor, but it does not replace a full configured runtime environment.

• Lightweight editor is tempting, but github.dev is not intended to provide the full configured runtime environment described in the scenario.
• Download as ZIP fails because it does not give the user a working configured environment and still leaves them without needed tools.
• Open a discussion may help collaboration, but it does not solve the immediate need to start working in the required environment.

Question 4

Topic: Apply Modern Development Practices

A new contributor is assigned a GitHub issue that requires editing code, installing dependencies, and running the app for testing. They are using a shared laptop and do not want to set up tools locally. What should they do next to work in a cloud development environment tied to the repository?

Options:

• A. Open the repository in github.dev

• B. Create a GitHub Codespace from the repository

• C. Publish the repository with GitHub Pages

• D. Create a Gist for the changed files

Best answer: B

Explanation: GitHub Codespaces is designed for this exact workflow: coding, installing dependencies, and running an app in a cloud environment linked to a GitHub repository. It avoids local setup while still giving the contributor a full development workspace.

GitHub Codespaces is a cloud development environment associated with a GitHub repository. In this scenario, the contributor needs more than lightweight file editing—they must install dependencies and run the application for testing. That makes Codespaces the appropriate next step because it provides a ready-to-use development workspace in the browser or through a supported editor, without requiring local tool installation.

A lightweight editor is useful for quick file changes, but it is not the best choice when the task depends on a complete runtime environment. Community and publishing features also do not help with actually developing and testing the code. The key takeaway is that Codespaces fits full repository-based development work in the cloud.

• github.dev is lighter because it is mainly for quick browser-based editing, not a full cloud development environment for running project setup and tests.
• A Gist is separate from the repository workflow and is meant for sharing snippets, not for developing a repository issue.
• GitHub Pages is for publishing website content, not for creating a development workspace.

Question 5

Topic: Apply Modern Development Practices

A student joins a team’s GitHub repository for a small web app. Their laptop does not allow local installation of the required SDK and database tools, but they still need a ready-to-use development environment linked to the repository so they can edit code, run terminal commands, and test changes online. Which GitHub feature best meets this need?

Options:

• A. GitHub Actions

• B. github.dev

• C. GitHub Pages

• D. GitHub Codespaces

Best answer: D

Explanation: GitHub Codespaces is designed for this exact scenario: a full cloud development environment connected to a GitHub repository. It lets a user work without setting up the required tools on their local device.

GitHub Codespaces gives developers a complete development environment in the cloud that is associated with a GitHub repository. For a beginner, the key idea is that it is more than just file editing: it can provide the editor, terminal, and repository-specific setup needed to build and test code online. That fits a situation where the local laptop cannot install required dependencies.

A lightweight browser editor may help with quick edits, but it does not replace a full configured development environment. Automation and site hosting also solve different GitHub needs. The key takeaway is that Codespaces is the GitHub feature for repo-based cloud development work.

• Lightweight editing only The option using github.dev is mainly for quick browser edits, not a full cloud development environment with repo setup and terminal use.
• Automation, not coding workspace The option using GitHub Actions runs workflows automatically and does not give the student an interactive development environment.
• Publishing, not development The option using GitHub Pages is for hosting static content, not for writing and testing application code in a cloud workspace.

Question 6

Topic: Apply Modern Development Practices

A new contributor is using a shared computer and needs to make a small Markdown change to a repository’s README.md. They want to work entirely in the browser and do not need to install dependencies, run the application, or start a full cloud development environment.

Which GitHub tool best fits this scenario?

Options:

• A. GitHub Codespaces

• B. github.dev

• C. GitHub Copilot

• D. GitHub Actions

Best answer: B

Explanation: This scenario matches github.dev because the task is a quick in-browser edit with no need to build, run, or configure a full environment. It is the lightweight GitHub option for simple repository edits directly from the browser.

The key concept is choosing the right GitHub development surface for the amount of work required. When someone only needs to edit a file such as README.md in the browser, github.dev is the best fit because it provides lightweight editing without setting up a complete cloud machine.

A full Codespaces environment is more appropriate when the user needs to run code, install dependencies, or use a richer development setup. GitHub Actions is for automating workflows such as builds and tests, not for interactive editing. GitHub Copilot helps generate or suggest code, but it is an assistant feature rather than the workspace itself.

The deciding clue is “browser only” plus “no full environment needed.”

• Codespaces is heavier because it provides a full cloud development environment, which the scenario explicitly says is unnecessary.
• Actions automates work rather than giving the user a place to edit files interactively.
• Copilot assists writing but does not replace the editing workspace needed for this task.

Question 7

Topic: Apply Modern Development Practices

A team keeps configuration in a repository so that when anyone opens the project in GitHub Codespaces, the same tools, extensions, and runtime versions are set up automatically. Which concept best explains this setup?

Options:

• A. GitHub Codespace

• B. Repository template

• C. Dev container

• D. GitHub Actions workflow

Best answer: C

Explanation: This scenario describes a dev container. A dev container is used to customize a development environment so the same tools and settings are applied each time the project is opened in a compatible environment such as Codespaces.

A dev container is a repository-based way to define a consistent development environment at a high level. It can specify things like runtime versions, tools, and editor extensions so everyone working on the project starts with the same setup. In GitHub, this is commonly used with Codespaces to make onboarding easier and reduce environment differences between contributors.

A Codespace is the actual cloud development environment, but the dev container is what customizes that environment. By contrast, GitHub Actions automates tasks such as builds or tests, and a repository template is for creating new repositories with starter content.

• Codespaces vs. config The cloud environment is a Codespace, but the customization definition for tools and settings is the dev container.
• Automation mismatch A GitHub Actions workflow runs automated tasks and does not define a developer’s interactive coding environment.
• Starter repo mismatch A repository template helps create new repositories, not configure the development tools inside the environment.

Question 8

Topic: Apply Modern Development Practices

A student team uses GitHub Projects to track work items and GitHub Discussions to talk about new ideas. They now want every pull request to automatically run a validation step before anyone reviews it.

What should the team do next?

Options:

• A. Pin an issue with the test instructions

• B. Create a GitHub Actions workflow for the repository

• C. Add a new status field in GitHub Projects

• D. Start a GitHub Discussion for each pull request

Best answer: B

Explanation: Use GitHub Actions when the goal is automation in response to repository events like pull requests. GitHub Projects organizes and tracks work, while Discussions supports conversation, not automated validation.

The core concept is feature purpose. GitHub Actions automates development tasks based on triggers such as pushes or pull requests, so it fits a workflow where checks should run automatically before review. In this scenario, the team already has tools for planning and conversation: GitHub Projects tracks tasks, and Discussions helps people talk through ideas. Neither of those features executes validation steps.

A good beginner rule is:

• Use GitHub Actions for automation.
• Use GitHub Projects for tracking work.
• Use GitHub Discussions for open-ended conversation.

Pinning instructions in an issue can document a manual process, but it does not make the process run automatically. The key takeaway is to match the GitHub feature to the goal: automation requires Actions.

• Project tracking only adding a field in GitHub Projects helps organize work, but it does not run checks on pull requests.
• Conversation only starting a Discussion may help the team talk about review practices, but it does not automate validation.
• Manual guidance only pinning an issue can share instructions, but reviewers would still need to run the test step themselves.

Question 9

Topic: Apply Modern Development Practices

A documentation contributor notices a typo in a repository README.md while using a locked-down shared laptop. They only need to make a quick browser-based text edit and commit the change, without setting up a full development environment or running the code. Which GitHub concept best fits this scenario?

Options:

• A. GitHub Copilot

• B. GitHub Codespaces

• C. github.dev

• D. GitHub Actions

Best answer: C

Explanation: This scenario is about lightweight editing, not automation, AI assistance, or full environment setup. github.dev fits because it lets someone quickly edit repository files in the browser.

The key requirement is a fast, browser-based edit for a small documentation change. github.dev is designed for lightweight editing directly from a GitHub repository, which makes it a good fit when someone only needs to update text like a README and does not need to build, run, or configure the project.

By contrast, GitHub Codespaces is for a fuller cloud development environment, GitHub Copilot is for AI coding assistance, and GitHub Actions is for workflow automation. When the main need is simply editing a file quickly in the browser, github.dev is the best match.

• Automation mismatch GitHub Actions automates workflows such as builds or tests, but the scenario is only about making a quick manual edit.
• AI mismatch GitHub Copilot helps generate or suggest code, but the main need here is browser editing, not AI assistance.
• Too much setup GitHub Codespaces provides a complete development environment, which is unnecessary for a simple README typo fix.

Question 10

Topic: Apply Modern Development Practices

A new contributor joins a team’s GitHub repository. Instead of installing tools locally, they open a ready-to-use development environment from the repository, get a terminal, run the app, and work in the cloud with the repository’s setup already applied. Which GitHub concept best explains this scenario?

Options:

• A. GitHub Codespaces

• B. github.dev

• C. GitHub Actions

• D. GitHub Copilot

Best answer: A

Explanation: This scenario describes a full cloud development environment connected to a GitHub repository. GitHub Codespaces lets users develop in the cloud with repository-based configuration instead of setting up everything on their local machine.

GitHub Codespaces is a cloud development environment associated with a GitHub repository. It is designed for writing, running, and testing code without requiring the contributor to fully configure the project on their own device first. In this scenario, the key clues are the ready-to-use setup, terminal access, and working directly in a cloud environment based on the repository’s configuration.

A lightweight browser editor would not be the best match because the scenario emphasizes a full development environment, not just file editing. The main idea is that Codespaces gives contributors a consistent workspace that is linked to GitHub work.

• Browser editing only the option naming github.dev is less suitable because it focuses on lightweight web-based editing rather than a full cloud dev environment.
• Automation service the option naming GitHub Actions is for workflows and automation, not for interactive coding environments.
• AI assistance the option naming GitHub Copilot helps write code, but it does not itself provide the cloud workspace described.

Continue with full practice

Use the GitHub Foundations GH-900 Practice Test page for the full IT Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Try GitHub Foundations GH-900 on Web View GitHub Foundations GH-900 Practice Test

Related focused pages

• Free GitHub Foundations GH-900 Full-Length Practice Exam
• Git and Github Basics
• Repositories
• Collaborate Using Github
• Github Projects
• Privacy and Administration
• Github Community

Free review resource

Read the GitHub Foundations GH-900 Cheat Sheet on Tech Exam Lexicon, then return to IT Mastery for timed practice.