Question 900
At Silverbrook Nonprofit, a fundraising support team is improving grant review updates after a knowledge-policy revision (SF-T09-01). The administrator observes that a newly activated agent version gives an incorrect action routing during rollout. Any fix must ensure that donor details cannot be revealed across accounts. 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 Opportunity acceptance test, a rollback smoke test restores the approved routing without unauthorized transactions; the record is retained under Silverbrook Nonprofit's rollout (SF-T09-01). The chosen correction was to retain known-good versions and use a controlled activation or rollback procedure; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.
Incorrect Answers
The proposed observation “The production smoke test finds the correct actions, permissions, and configured channels; confirm this while testing the unauthorized case” would check a different original case: A service agent works in sandbox but its production deployment lacks dependent automation and entitlements. The correction must ensure that member records cannot be exposed to other members. Its mechanism is: Agent migration is a dependency and permission deployment task, not just copying text instructions. In the present case, a newly activated agent version gives an incorrect action routing during rollout. The correction must ensure that donor details cannot be revealed across accounts; the more direct acceptance evidence is “A rollback smoke test restores the approved routing without unauthorized transactions; confirm this and retain a reproducible test record” because agent lifecycle requires version control and recoverable release states.
The proposed observation “A least-privilege production test retrieves the intended approved passage; confirm this using a least-privilege test identity” would check a different original case: An Agentforce agent passes preview but cannot access its production knowledge library. The correction must ensure that financial identifiers are masked outside authorized roles. Its mechanism is: Environment-specific data connections can change agent behavior after migration. In the present case, a newly activated agent version gives an incorrect action routing during rollout. The correction must ensure that donor details cannot be revealed across accounts; the more direct acceptance evidence is “A rollback smoke test restores the approved routing without unauthorized transactions; confirm this and retain a reproducible test record” because agent lifecycle requires version control and recoverable release states.
The proposed observation “The test suite flags an unintended topic change before release; confirm this with production-equivalent source conditions” would check a different original case: A new agent topic is released without checking its effect on existing request routing. The correction must ensure that student records never cross program authorization boundaries. Its mechanism is: Testing Center supports repeatable batch checks of agent behavior. In the present case, a newly activated agent version gives an incorrect action routing during rollout. The correction must ensure that donor details cannot be revealed across accounts; the more direct acceptance evidence is “A rollback smoke test restores the approved routing without unauthorized transactions; confirm this and retain a reproducible test record” because agent lifecycle requires version control and recoverable release states.