What is true about both org development and change set development?

What is true about both org development and change set development?

• A. You can include destructive changes (such as deleting a field) in a release.
• B. You can have release artifacts that contain changed and new metadata components.
• C. You can use the Salesforce CLI to script routine tasks.
• D. You can select specific user data records to move to a different environment.

Answer: (B)

Both org development and change set development center on moving metadata changes between Salesforce environments. The most accurate statement is that release artifacts can contain the changed and new metadata components you’ve added or updated. That’s what you’re packaging or assembling when you prepare a deployment: you gather the components that have been altered or created and deploy them so the target org reflects the same configuration and code. Understand that this framing is what makes both approaches comparable: they’re about packaging metadata changes into something that can be deployed to another environment. Destructive changes aren’t typically included in a standard release artifact, and moving specific user data records is not part of the metadata deployment process. While the Salesforce CLI can automate tasks, the essential point common to both methods is bundling changed and new metadata components into a deployable artifact.

Both org development and change set development center on moving metadata changes between Salesforce environments. The most accurate statement is that release artifacts can contain the changed and new metadata components you’ve added or updated. That’s what you’re packaging or assembling when you prepare a deployment: you gather the components that have been altered or created and deploy them so the target org reflects the same configuration and code.

Understand that this framing is what makes both approaches comparable: they’re about packaging metadata changes into something that can be deployed to another environment. Destructive changes aren’t typically included in a standard release artifact, and moving specific user data records is not part of the metadata deployment process. While the Salesforce CLI can automate tasks, the essential point common to both methods is bundling changed and new metadata components into a deployable artifact.