200-901 Infrastructure and Automation Practice Question
A developer runs the command `git clone https://github.com/example/netconfig.git` on a workstation, then edits a file named `vlans.yml`. Before editing, the developer wants to confirm which remote repository the local clone is tracking for push and fetch operations. Which command should be run?
⚠ Common exam trap
The trap here is assuming that git status reports the remote repository URL, when it only reports local branch and file state.
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 remote -v
The git remote -v command enumerates each configured remote and prints its fetch and push URLs, which directly confirms which repository the local clone is linked to. Other commands inspect working tree state, commit history, or local diffs, none of which expose remote configuration. Verifying remotes before pushing avoids accidentally sending commits to an unintended upstream repository.
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 diff HEAD
Why it's wrong here
This command compares the working tree against the most recent commit, showing uncommitted modifications. It is used to review local edits before staging, but it has nothing to do with remote configuration. It will not reveal the fetch and push URLs of the cloned repository, so it fails to answer the scenario's question about tracked remotes.
- ✓
git remote -v
Why this is correct
This command lists all configured remotes together with their fetch and push URLs. Because the clone was created from a URL, the default remote named origin is registered automatically, and this command confirms the exact repository the local branch will push to and fetch from. It is the fastest way to verify tracking configuration before committing and pushing changes.
- ✗
git log --oneline
Why it's wrong here
This command prints a condensed history of commits on the current branch with abbreviated hashes. While useful for reviewing recent changes, it contains no information about configured remotes or their URLs. It therefore cannot confirm which remote repository this clone is pointed at, making it the wrong choice for verifying remote tracking configuration.
- ✗
git status
Why it's wrong here
This command reports the state of the working tree and the staging area, showing modified, staged, and untracked files. It does not display which remote URL the repository is associated with or which remote branch the local branch tracks, so it cannot answer the question about the tracked remote repository. It only shows local change context and branch name.
Visual reference
Go deeper
Related to this question
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 →
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.