200-901 Software Development and Design Practice Question

In version control with Git, which command creates a new branch and switches to it in one step?

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 <branch>

git checkout -b <branch> creates and switches. git branch <branch> creates but does not switch. git switch -c is also valid but not listed.

Answer analysis

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

✓
git checkout -b <branch>
Why this is correct
git checkout -b <branch> creates the new branch at the current HEAD and immediately switches the working tree to it, combining creation and checkout. This single-step behaviour matches the stem's requirement, unlike git branch alone, which only creates.
✗
git checkout <branch>
Why it's wrong here
git checkout <branch> switches to an existing branch and fails if that branch does not exist; it creates nothing. It is the right command when moving between branches already present, but the one-step create-and-switch requires the -b flag or git switch -c.
✗
git branch <branch>
Why it's wrong here
git branch <branch> creates the branch but leaves HEAD on the current branch, so no switch occurs. It is correct for creating a branch to work on later, yet the scenario demands creation and checkout together, which needs git checkout -b or git switch -c.
✗
git switch <branch>
Why it's wrong here
git switch <branch> only moves to an existing branch and errors if it is absent; it creates nothing. It suits switching between branches that already exist, whereas creating and switching in one step requires the -c flag, as in git switch -c <branch>.

Go deeper