In the org development model, what mechanism externalizes changes to keep environments in sync?

In the org development model, what mechanism externalizes changes to keep environments in sync?

• A. Externalizes changes in a source control repository to keep environments in sync.
• B. Uses packages to move metadata between environments.
• C. Uses a source control repository so developers don't have to track changes manually.
• D. Requires that you develop all customizations in your sandbox.

Answer: (A)

Externalizing changes into a source control repository creates a centralized, versioned history of all metadata changes, enabling environments to stay in sync through a single source of truth. When metadata is treated as code, each edit is committed, branches can represent features or releases, and deployment processes can pull the latest, validated changes into each org in a repeatable way. This makes it easy to track what changed, why, and when, and to reproduce or roll back deployments across development, staging, and production. Packages can move metadata between environments, but they are a deployment mechanism rather than the central way of externalizing and versioning changes. Relying on a repository to eliminate manual tracking is misleading because version control requires active management of commits and branches. Developing everything in a sandbox ignores the need to propagate and coordinate changes across multiple environments.

Externalizing changes into a source control repository creates a centralized, versioned history of all metadata changes, enabling environments to stay in sync through a single source of truth. When metadata is treated as code, each edit is committed, branches can represent features or releases, and deployment processes can pull the latest, validated changes into each org in a repeatable way. This makes it easy to track what changed, why, and when, and to reproduce or roll back deployments across development, staging, and production.

Packages can move metadata between environments, but they are a deployment mechanism rather than the central way of externalizing and versioning changes. Relying on a repository to eliminate manual tracking is misleading because version control requires active management of commits and branches. Developing everything in a sandbox ignores the need to propagate and coordinate changes across multiple environments.