Git is a distributed version control system, so every clone holds the whole history. Centralized systems like Subversion or CVS keep the history on one server, and each client holds a working copy of the current files.
Git's history is local. You can commit, read the log, and compare versions with no network.
Aspect
Git (distributed)
Centralized (SVN, CVS)
Full history
in every clone
on the server only
Commit and read history
local, no network
need the server
Branching
cheap and local
server-side, needs network
Server outage
any clone still has the full history
no commits until it returns
The trade-off is that your commits stay private until you push, and teammates see them only after they fetch.
Rewriting in plainer words…
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
If every clone has the full history, how does a team agree on which copy is the real one?A strong answer names a shared remote the team agrees to treat as canonical, and says Git itself does not require one.
When might a centralized system still be the better choice?Look for large binary assets, file locking or per-path access control, plus a mention of Git's own fixes such as LFS.
What you can say
Git is a distributed version control system, so every clone holds the whole history of the project.
In a centralized system like Subversion or CVS, the history lives on one server and each developer has a working copy of the current files.
Because the history is local in Git, I can commit, read the log and compare versions with no network at all.
Branching is cheap and local too, while in a centralized system branches live on the server and need the network.
If the server goes down, any Git clone still has the full history, but a centralized team can't commit until the server is back.
The trade-off is that my commits stay private until I push, and teammates only see them after they fetch.
Weak answers to avoid
Confuses Git with GitHubGitHub is a hosting service and Git is the tool, which runs fine without it. Describe Git's model on its own terms and treat a host as one more copy.
Claims Git has no central serverMost teams still push to one shared remote. The real difference is that you don't need the server to commit or read history, and every clone is a full copy.
Recites commands instead of the modelListing clone, commit and push misses the question. Say where the history lives and what that lets you do offline or during an outage.
Calls distributed strictly betterThat sounds shallow. Name the cost too. Local commits stay invisible until you push, and teammates see them only after they fetch.
Interview lens
Likely follow-ups, what you can say, and the weak answers to avoid.
