Courseiva

200-901 Software Development and Design Practice Question

A developer is preparing to add a new feature to a shared Git repository. The team uses a workflow where each feature is developed on its own branch and then merged back into the main branch through a pull request. Which Git operation should the developer perform first to begin work on the new feature?

⚠ Common exam trap

The trap here is thinking that a commit must happen before a branch is created, when branching should come first to keep the main line clean.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

git checkout -b feature/new-feature

Starting a feature requires an isolated branch so commits do not land directly on the shared main branch. Creating and switching to a new branch in one step provides that isolation and prepares the work for a later pull request. Committing, pushing main, or merging does not establish the new branch.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    git merge main

    Why it's wrong here

    Merging main into the current branch assumes a branch already exists and is intended for syncing changes. It does not create a new feature branch, so the developer would still be working on whatever branch was previously checked out.

  • ✓

    git checkout -b feature/new-feature

    Why this is correct

    This command creates a new branch named feature/new-feature and immediately switches to it, giving the developer an isolated workspace. Subsequent commits land on that branch and can later be submitted as a pull request, matching the team's workflow.

  • ✗

    git push origin main

    Why it's wrong here

    Pushing the main branch does not create a feature branch and may publish unrelated local commits. It also does not establish the isolated workspace needed for the new feature, so it does not satisfy the team's branching workflow.

  • ✗

    git commit -m "start feature"

    Why it's wrong here

    Committing before creating a branch records the change on the current branch, which is likely the main branch. That pollutes the shared history and does not create the isolated feature branch the workflow requires, so it is the wrong first step.

About these practice questions

Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Cisco exam blueprint

This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.