Question 320
At Harbor Logistics, a distribution operations team is improving shipment exception triage during a least-privilege verification (SF-P09-02). The administrator observes that a team tries to use a fixed sales-email template for an unrelated service incident taxonomy analysis. Any fix must ensure that shipment changes remain attributable and reversible. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Review template types against business inputs before building; require the check in the next release review at Harbor Logistics (SF-P09-02). It complements the corrective action, select a suitable flexible template rather than forcing a narrowly scoped standard template, and protects the explicit condition that shipment changes remain attributable and reversible.
Incorrect Answers
This safeguard, “Version the input schema and regression-test required fields; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: A product description needs account, asset, and customer details as separately defined inputs. The correction must ensure that policy terms come from the current approved revision. That risk depends on: Flex templates allow business-specific inputs beyond a single predefined record field. The recurring problem here is a team tries to use a fixed sales-email template for an unrelated service incident taxonomy analysis. The correction must ensure that shipment changes remain attributable and reversible. The originally selected control “Review template types against business inputs before building; review it with a documented exception process” is more specific because standard prompt types optimize specific tasks while Flex serves custom use cases.
This safeguard, “Test field compatibility and page assignment before activation; review it and retest after dependent metadata changes”, reduces a different source-defined risk: A sales team expects a generated note to populate one writable account field directly. The correction must ensure that capacity limits and customer entitlements are enforced deterministically. That risk depends on: Field Generation templates target supported writable record fields rather than arbitrary output collections. The recurring problem here is a team tries to use a fixed sales-email template for an unrelated service incident taxonomy analysis. The correction must ensure that shipment changes remain attributable and reversible. The originally selected control “Review template types against business inputs before building; review it with a documented exception process” is more specific because standard prompt types optimize specific tasks while Flex serves custom use cases.
This safeguard, “Classify workflows as deterministic updates or content generation during design review; review it before expanding channel availability”, reduces a different source-defined risk: A nightly data cleanup requirement is being treated as a request for open-ended generated prose. The correction must ensure that customer order details stay within each authorized account. That risk depends on: Prompt Builder generates contextual text and should not replace deterministic business-rule execution. The recurring problem here is a team tries to use a fixed sales-email template for an unrelated service incident taxonomy analysis. The correction must ensure that shipment changes remain attributable and reversible. The originally selected control “Review template types against business inputs before building; review it with a documented exception process” is more specific because standard prompt types optimize specific tasks while Flex serves custom use cases.