What are three advantages of using a Source Control system alongside a multi -sandbox development strategy? Choose 3 answers

A Source Control System (SCS) is foundational for collaborative, multi-sandbox development. It maintains a complete history of all metadata changes, attributing each commit to a specific developer (C). This history is crucial for auditing and debugging. The SCS enables branching strategies, allowing developers to work on features or fixes in isolation without impacting others, which is essential in a multi-sandbox environment (D). Furthermore, modern SCS platforms integrate code review processes (e.g., pull/merge requests), which allow for quality checks before code is merged and promoted to subsequent environments like a pre-production sandbox (A).

B. An SCS is a repository; it does not automatically deploy changes. Continuous Integration/Continuous Deployment (CI/CD) tools are required to automate deployments, though they use the SCS as the source of truth.
E. An SCS acts as a backup for metadata (code, configuration), not the organization's record data. The term "data loss" is ambiguous, but typically refers to record data, which requires a separate backup solution.

1. Salesforce Well-Architected Framework, Development Process. (2023). Salesforce. "Version control is the foundation of a healthy development process... It provides a history of all changes... It enables collaboration through branching and merging..."

2. Chacon, S., & Straub, B. (2014). Pro Git. Apress. Chapter 1.1, "About Version Control," discusses tracking history. Chapter 3.1, "Branches in a Nutshell," discusses branching for isolated development.

3. GitHub Docs. (n.d.). "About pull requests." Retrieved from docs.github.com. This official documentation details how pull requests facilitate code review before merging changes into a main branch, a standard practice before promotion.