Cloud Kicks is developing a prompt template in a sandbox and has created multiple saved versions during testing. Cloud Kicks is now preparing to move the template to production.
What is a consideration when deploying the template to production?
A.
Deploying a template requires all previous versions to be manually activated before deployment can succeed
B.
Deploying a template automatically removes all prior versions and replaces them with the deployed version in production
C.
Deploying a prompt template includes all versions of the prompt template that are in the source org to the target org
The correct answer is C because prompt template versioning is part of the prompt template metadata lifecycle. When a prompt template is moved between environments, specialists must account for versions stored with the template in the source org. That is why template version management matters before deployment; test versions, inactive versions, and production-ready versions can all affect the metadata package. Option A is wrong because earlier versions do not have to be manually activated before deployment. Option B is wrong because deployment does not simply wipe all history and retain only one replacement version. Salesforce’s CLI considerations for Prompt Builder confirm that template versions are represented in deployable XML and can be managed during deployment, including deletion behavior in the target org.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit