What API version merges changes on permission sets and profile with the target org?

What API version merges changes on permission sets and profile with the target org?

• A. API version 39.0 or earlier
• B. API version 40.0 and later
• C. API version 38.0
• D. API version 41.0

Answer: (A)

Merging changes for permission sets and profiles with the target org depends on the Metadata API version you use. In API version 39.0 and earlier, deployments for profiles and permission sets are merged with the existing metadata in the target org, so only the fields you include are updated and the rest remains intact. This additive behavior helps prevent unintended overwrites during incremental updates. Starting with API version 40.0, Salesforce changed how these metadata types are applied, making deployments more likely to replace or require complete definitions rather than merge partial updates. So the version that merges changes with the target org is API version 39.0 or earlier.

Merging changes for permission sets and profiles with the target org depends on the Metadata API version you use. In API version 39.0 and earlier, deployments for profiles and permission sets are merged with the existing metadata in the target org, so only the fields you include are updated and the rest remains intact. This additive behavior helps prevent unintended overwrites during incremental updates. Starting with API version 40.0, Salesforce changed how these metadata types are applied, making deployments more likely to replace or require complete definitions rather than merge partial updates. So the version that merges changes with the target org is API version 39.0 or earlier.