CRT-403 practice question 2 of 35

An app builder at Ursa Major Solar has been working on a new custom app in a sandbox that has been upgraded to the next major Salesforce version, and their production instance is still on the current Salesforce version. The development is complete and they are ready to deploy a change set. What should the app builder consider when planning the deployment?

Full set: 291 questions
Answer options
A: It will fall if there is a feature only available in the next version. Correct answer
B: The change set components will be upgraded to the next version in production.
C: The change set will be automatically deployed when production is upgraded.
D: The deployment is not possible due to different versions.
Correct Answer:
A. It will fall if there is a feature only available in the next version.
Explanation

When deploying from a sandbox on a newer Salesforce version (a preview instance) to a production org on the current version, the deployment's success is contingent on the contents of the change set. The deployment process will fail if the change set includes any components, metadata types, or features that are only available in the newer version. The target production environment, being on an older version, will not recognize these new features, leading to a deployment error. Therefore, the app builder must ensure all components in the change set are compatible with the production org's current version.

Why Incorrect

B. The change set components will be upgraded to the next version in production. This is incorrect. The production org is on an older version and cannot process or upgrade components to a version it does not yet support.
C. The change set will be automatically deployed when production is upgraded. This is incorrect. Change set deployments are a manual process and are not automatically triggered by a Salesforce version upgrade.
D. The deployment is not possible due to different versions. This statement is too absolute and thus incorrect. Deployment is possible as long as the change set only contains components and features that are compatible with the older version in production.

References

1. Salesforce Help Documentation, Article 000384865, "Considerations for Deploying from a Sandbox with a New Release to Production": This official article directly addresses the scenario. It states, "You can deploy from a sandbox on a preview release to a production org on a non-preview release. However, you can only deploy changes that are compatible with the production org’s release. If your deployment includes features that are new in the sandbox’s release, the deployment fails." This directly supports answer A and refutes D.

2. Metadata API Developer Guide, "Introduction to Metadata API": The principles of the Metadata API, which change sets use under the hood, dictate that a target organization must be able to understand the metadata types being deployed. If a change set contains a metadata type or an attribute of a type that was introduced in the newer API version (e.g., API v58.0), a target org running an older version (e.g., API v57.0) will reject it, causing the deployment to fail. This provides the technical foundation for why answer A is correct.

Scroll to Top