Question 130
At Meridian Research, a research support office is improving laboratory service intake during a controlled sandbox pilot (SF-P05-02). The administrator observes that a service representative can see a generated-content feature but the template run is denied. Any fix must ensure that restricted project data remains separated by research group. Which action best addresses the issue while preserving the stated requirement?
Explanation
Correct Answer
The documented failure is that a service representative can see a generated-content feature but the template run is denied. Verify and assign the approved template execution access and required underlying data permissions for Meridian Research's laboratory service intake workflow (SF-P05-02) while respecting that restricted project data remains separated by research group. Its outcome is not established merely by changing instructions: In a controlled Lab_Request__c acceptance test, an authorized representative executes the template while a deliberately unauthorized user remains blocked; the record is retained under Meridian Research's rollout (SF-P05-02). The underlying reason is that Template access alone does not erase record and field permission boundaries. In this laboratory service intake scenario, this separates supported agent behavior from assumptions about the AI model.
Incorrect Answers
The action “Separate template builders from template consumers and reduce grants to the required use capability; implement it within the documented Salesforce configuration” addresses a separate source case: Business users have broad template modification rights merely to generate existing sales drafts. The correction must ensure that restricted project data remains separated by research group. Its underlying reason is: Least privilege applies independently to template creation, activation, and execution. This question instead describes a service representative can see a generated-content feature but the template run is denied. The correction must ensure that restricted project data remains separated by research group. The original answer “Verify and assign the approved template execution access and required underlying data permissions; implement it and keep the business rule enforceable” targets that failure because template access alone does not erase record and field permission boundaries.
The action “Grant the least-privileged approved prompt template management access before authoring templates; implement it with least-privilege execution” addresses a separate source case: An analyst needs to build new production prompt templates but has only permission to use existing ones. The correction must ensure that guest profile fields are used only with permitted access. Its underlying reason is: Creating templates and using templates are distinct authorization responsibilities. This question instead describes a service representative can see a generated-content feature but the template run is denied. The correction must ensure that restricted project data remains separated by research group. The original answer “Verify and assign the approved template execution access and required underlying data permissions; implement it and keep the business rule enforceable” targets that failure because template access alone does not erase record and field permission boundaries.
The action “Select a suitable flexible template rather than forcing a narrowly scoped standard template; implement it with a controlled rollback path” addresses a separate source case: A team tries to use a fixed sales-email template for an unrelated service incident taxonomy analysis. The correction must ensure that billing adjustments require verified eligibility. Its underlying reason is: Standard prompt types optimize specific tasks while Flex serves custom use cases. This question instead describes a service representative can see a generated-content feature but the template run is denied. The correction must ensure that restricted project data remains separated by research group. The original answer “Verify and assign the approved template execution access and required underlying data permissions; implement it and keep the business rule enforceable” targets that failure because template access alone does not erase record and field permission boundaries.