A regional operations manager asks why front-desk staff who can execute a claim-summary prompt template cannot also see the raw instructions and grounding configuration behind it. What is the best justification?
Select an answer to reveal the explanation.
Short Explanation
You can give front-desk staff the prompt’s output without exposing the machinery behind it. Separating execution from configuration visibility protects the setup and keeps staff focused on the task they need to do.
Full Explanation
Separating execution from configuration visibility is an intentional security and usability choice: it limits what an attacker or careless user could see or change if front-desk credentials were compromised, and keeps end users focused on the output rather than prompt-engineering details that are not relevant to using the tool. The claim that Salesforce’s metadata model ties instructions and grounding to protected system code, making selective exposure impossible and requiring separate templates for every role, does not explain the permission split; it substitutes an unspecified technical limitation for the intentional design. Saying configuration is always visible to execute users contradicts the scenario and the platform’s permission model, which distinguishes execution from configuration access. Calling the separation a temporary limitation to be removed also mischaracterizes deliberate access control as a bug or gap; separating execute access from viewing or editing configuration is an ongoing least-privilege practice. The exam caveat is that being able to run a prompt does not imply permission to inspect or change its configuration. As a practical check, compare the permissions of an execute-only staff account with those of an administrator to confirm that the staff account can use the prompt without accessing its underlying instructions and grounding settings.