Question 270
At Cobalt Mobility, an API platform team is improving partner integration after a knowledge-policy revision (SF-P06-02). The administrator observes that business users have broad template modification rights merely to generate existing sales drafts. Any fix must ensure that partner authentication and least privilege are maintained. Which observable result would best demonstrate that the correction actually worked?
Explanation
Correct Answer
This is the direct acceptance signal for the reported failure: In a controlled Integration_Request__c acceptance test, a normal user can invoke the approved draft but cannot change the production template definition; the record is retained under Cobalt Mobility's rollout (SF-P06-02). The chosen correction was to separate template builders from template consumers and reduce grants to the required use capability; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.
Incorrect Answers
The proposed observation “An authorized representative executes the template while a deliberately unauthorized user remains blocked; confirm this and retain a reproducible test record” would check a different original case: A service representative can see a generated-content feature but the template run is denied. The correction must ensure that escalations preserve only the needed guest context. Its mechanism is: Template access alone does not erase record and field permission boundaries. In the present case, business users have broad template modification rights merely to generate existing sales drafts. The correction must ensure that partner authentication and least privilege are maintained; the more direct acceptance evidence is “A normal user can invoke the approved draft but cannot change the production template definition; confirm this and confirm the resulting trace” because least privilege applies independently to template creation, activation, and execution.
The proposed observation “The analyst can create a test template while ordinary users remain limited to permitted execution; confirm this using a least-privilege test identity” would check a different original 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 mechanism is: Creating templates and using templates are distinct authorization responsibilities. In the present case, business users have broad template modification rights merely to generate existing sales drafts. The correction must ensure that partner authentication and least privilege are maintained; the more direct acceptance evidence is “A normal user can invoke the approved draft but cannot change the production template definition; confirm this and confirm the resulting trace” because least privilege applies independently to template creation, activation, and execution.
The proposed observation “A null-field case produces the approved fallback rather than a fabricated date; confirm this using a representative sandbox fixture” would check a different original case: A template tells the model to use only current CRM values but also to invent friendly dates for empty fields. The correction must ensure that donor details cannot be revealed across accounts. Its mechanism is: Conflicting directions undermine deterministic expectations and reliable evaluation. In the present case, business users have broad template modification rights merely to generate existing sales drafts. The correction must ensure that partner authentication and least privilege are maintained; the more direct acceptance evidence is “A normal user can invoke the approved draft but cannot change the production template definition; confirm this and confirm the resulting trace” because least privilege applies independently to template creation, activation, and execution.