Question 330
At Silverbrook Nonprofit, a fundraising support team is improving grant review updates during a controlled sandbox pilot (SF-P18-01). The administrator observes that a template tells the model to use only current CRM values but also to invent friendly dates for empty fields. Any fix must ensure that donor details cannot be revealed across accounts. Which action best addresses the issue while preserving the stated requirement?
Explanation
Correct Answer
The documented failure is that a template tells the model to use only current CRM values but also to invent friendly dates for empty fields. Remove the conflicting instruction and define what happens when a required value is null for Silverbrook Nonprofit's grant review updates workflow (SF-P18-01) while respecting that donor details cannot be revealed across accounts. Its outcome is not established merely by changing instructions: In a controlled Opportunity acceptance test, a null-field case produces the approved fallback rather than a fabricated date; the record is retained under Silverbrook Nonprofit's rollout (SF-P18-01). The underlying reason is that Conflicting directions undermine deterministic expectations and reliable evaluation. In this grant review updates scenario, this separates supported agent behavior from assumptions about the AI model.
Incorrect Answers
The action “State the task, approved sources, output length, and expected format in explicit prompt instructions; implement it with a controlled rollback path” addresses a separate source case: A field generation prompt produces variable-length paragraphs where downstream users require a brief summary. The correction must ensure that member records cannot be exposed to other members. Its underlying reason is: Clear role, context, constraints, and output format improve prompt consistency. This question instead describes 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. The original answer “Remove the conflicting instruction and define what happens when a required value is null; implement it and keep the business rule enforceable” targets that failure because conflicting directions undermine deterministic expectations and reliable evaluation.
The action “Instruct the template to use grounded facts only and state uncertainty when required facts are missing; implement it with a named deployment owner” addresses a separate source case: A generative service reply fills missing delivery dates with invented estimates. The correction must ensure that financial identifiers are masked outside authorized roles. Its underlying reason is: Prompts need explicit abstention behavior when grounding does not supply an answer. This question instead describes 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. The original answer “Remove the conflicting instruction and define what happens when a required value is null; implement it and keep the business rule enforceable” targets that failure because conflicting directions undermine deterministic expectations and reliable evaluation.
The action “Bind the required template inputs in Flow and test execution with representative records; implement it with least-privilege execution” addresses a separate source case: A Flow invokes a prompt template without supplying the record inputs expected by its definition. The correction must ensure that escalations preserve only the needed guest context. Its underlying reason is: A template invocation depends on correct input bindings and execution context. This question instead describes 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. The original answer “Remove the conflicting instruction and define what happens when a required value is null; implement it and keep the business rule enforceable” targets that failure because conflicting directions undermine deterministic expectations and reliable evaluation.