Which statement is NOT true about org development?

Which statement is NOT true about org development?

• A. Developing programmatically ensures there are fewer changes to manage in the first place.
• B. The team can do all of their development in a single org to avoid conflicting changes to apps.
• C. Changes between team members can be merged in a controlled manner.
• D. They can use a scratch org as their version control system.

Answer: (D)

In org development, the way changes are stored, tracked, and merged matters as much as the environments you use to build and test. Scratch orgs serve as disposable, isolated development and testing environments, not as the place where you permanently store and manage code or configuration. A version control system is the actual repository for history, branching, and controlled merging. Using a scratch org as your version control system would lose history, make audits difficult, and break reliable collaboration, so that statement isn’t true. Developing programmatically can help enforce consistency and automation, but it doesn’t guarantee fewer changes will appear overall. The amount of work and the number of changes depend on requirements and how the team collaborates. Relying on a single org for all development creates bottlenecks and increases the risk of conflicts across developers. Having a centralized, controlled process is what enables safe, coordinated work. And being able to merge changes from multiple team members in a controlled manner is exactly what a proper version control workflow provides, which is why that aspect is true.

In org development, the way changes are stored, tracked, and merged matters as much as the environments you use to build and test. Scratch orgs serve as disposable, isolated development and testing environments, not as the place where you permanently store and manage code or configuration. A version control system is the actual repository for history, branching, and controlled merging. Using a scratch org as your version control system would lose history, make audits difficult, and break reliable collaboration, so that statement isn’t true.

Developing programmatically can help enforce consistency and automation, but it doesn’t guarantee fewer changes will appear overall. The amount of work and the number of changes depend on requirements and how the team collaborates. Relying on a single org for all development creates bottlenecks and increases the risk of conflicts across developers. Having a centralized, controlled process is what enables safe, coordinated work. And being able to merge changes from multiple team members in a controlled manner is exactly what a proper version control workflow provides, which is why that aspect is true.