After a developer makes a change in a sandbox org, what step is required to share it with others?

After a developer makes a change in a sandbox org, what step is required to share it with others?

• A. Create a new branch in the source control system and a new DX project.
• B. Test the changes after pushing them to a clean testing org.
• C. Deploy the changes to every teammate's sandbox.
• D. Retrieve the changes from their sandbox to the project in the source repository.

Answer: (D)

In this workflow, the working area (the sandbox) is the place you make changes, but the formal, shared copy of the code lives in the source repository. To share what you’ve done, you bring those sandbox changes back into the shared project by retrieving them into the DX project in the source repository. This makes the changes versioned, visible to the rest of the team, and ready to be committed and pushed so others can pull them into their own work. The other options describe testing, reinventing the project, or deploying to everyone’s sandboxes, which doesn’t establish a single, auditable source of truth for collaboration.

In this workflow, the working area (the sandbox) is the place you make changes, but the formal, shared copy of the code lives in the source repository. To share what you’ve done, you bring those sandbox changes back into the shared project by retrieving them into the DX project in the source repository. This makes the changes versioned, visible to the rest of the team, and ready to be committed and pushed so others can pull them into their own work. The other options describe testing, reinventing the project, or deploying to everyone’s sandboxes, which doesn’t establish a single, auditable source of truth for collaboration.