A municipal engineering team needs distributed source history, branching, and a collaboration hub for application and infrastructure code. Which tool purpose is essential?
Select an answer to reveal the explanation.
Short Explanation
Code history, branches, and team collaboration live in Git—the distributed source-control hub almost every DevOps shop leans on. Packet captures and KVM switches solve different problems. Treat Git as the system of record for how the city changes code over time.
Full Explanation
Git provides distributed version control with commit history, branching, and collaboration workflows that underpin modern DevOps. Network capture tools and console hardware do not manage source history. Cloud+ Domain 5 expects recognition of Git’s role as the foundational source-control tool in DevOps environments.