What is the role of version control in MDC3 projects?

• A. Version control is used to deploy to production.
• B. Version control tracks changes to code/configs; enables collaboration, rollback, and auditability.
• C. Version control stores only documentation, not code.
• D. Version control automatically fixes bugs.

Answer: (B)

Version control in MDC3 projects acts as the history and coordination mechanism for code and configurations. By recording every change as a commit, it creates an auditable timeline that shows who changed what and when. Branching lets developers work in parallel on features or fixes without disrupting the main codebase, and merging brings approved work back into the main line after review. If something goes wrong, you can roll back to a previous stable state or revert specific changes, providing a safe safety net. This history also supports auditing and debugging, helping you track when a bug was introduced and by whom. Deployment often relies on CI/CD pipelines that use the version-controlled state, but version control itself doesn’t deploy automatically. It stores code and configuration (and related artifacts) and doesn’t automatically fix bugs.