Question 680
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 continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Test both template invocation and source-record authorization after role changes; require the check in the next release review at Meridian Research (SF-P05-02). It complements the corrective action, verify and assign the approved template execution access and required underlying data permissions, and protects the explicit condition that restricted project data remains separated by research group.
Incorrect Answers
This safeguard, “Review prompt asset permissions during quarterly access certification; review it before expanding channel availability”, reduces a different source-defined risk: 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. That risk depends on: Least privilege applies independently to template creation, activation, and execution. The recurring problem here is 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 originally selected control “Test both template invocation and source-record authorization after role changes; review it after configuration or data-source updates” is more specific because template access alone does not erase record and field permission boundaries.
This safeguard, “Audit template management grants and remove unnecessary author privileges; review it and retest after dependent metadata changes”, reduces a different source-defined risk: 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. That risk depends on: Creating templates and using templates are distinct authorization responsibilities. The recurring problem here is 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 originally selected control “Test both template invocation and source-record authorization after role changes; review it after configuration or data-source updates” is more specific because template access alone does not erase record and field permission boundaries.
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 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 originally selected control “Test both template invocation and source-record authorization after role changes; review it after configuration or data-source updates” is more specific because template access alone does not erase record and field permission boundaries.