AI-201 · Question #228
Cloud Kicks (CK) recently finished the development of a new prompt template that uses its own large language model (LLM). CK is deploying a prompt template from a sandbox to a production org, and is…
The correct answer is C. The name of the LLM does not match in sandbox and production. When deploying a prompt template that references a Bring Your Own LLM (BYOLLM) model, Salesforce resolves the LLM by its configured API name. If the external model gateway or LLM connection was set up with a different name in production than in sandbox, the deployment will fail…
Question
Cloud Kicks (CK) recently finished the development of a new prompt template that uses its own large language model (LLM). CK is deploying a prompt template from a sandbox to a production org, and is receiving an error. When trying to deploy the change set, CK is getting an error related to the LLM used in the prompt template. What is the cause of the error?
Options
- AThe prompt does not specify that it is a custom LLM.
- BBYOLLM is not yet supported for in prompt templates in production.
- CThe name of the LLM does not match in sandbox and production.
How the community answered
(18 responses)- A6% (1)
- B17% (3)
- C78% (14)
Explanation
When deploying a prompt template that references a Bring Your Own LLM (BYOLLM) model, Salesforce resolves the LLM by its configured API name. If the external model gateway or LLM connection was set up with a different name in production than in sandbox, the deployment will fail because the reference in the prompt template metadata cannot be resolved. The LLM connection must be configured identically (same API name) in both environments before the change set is deployed. Option A is incorrect - the prompt template does not require a special flag for custom LLMs. Option B is incorrect - BYOLLM is supported in prompt templates.
Topics
Community Discussion
No community discussion yet for this question.