Maintaining data integrity is the highest priority in a Guidewire implementation. When Database Consistency Checks identify errors that exist in the production environment, the resolution process must be rigorous, audited, and safe.
According to the Guidewire System Health & Quality curriculum, developers should never attempt to fix production data errors using " ad-hoc " methods like Scratchpad (Option B) or standard Import utilities (Option C), as these bypass the complex referential integrity and validation logic inherent in the application.
Instead, the best practice involves two paths. First, for errors rooted in complex application logic, the developer should write a Gosu script and request a review from Guidewire Support (Option D). Guidewire Support provides a " Data Fix " service to ensure the script won ' t have unintended side effects on the database schema or application stability.
Second, if the error is purely at the database level (e.g., a broken foreign key or orphan record), the developer should work with the insurer ' s database group to create a SQL script (Option E). However, this script must be tested in a QA environment (that uses a copy of production data) before execution to verify that it correctly resolves the consistency check failure without damaging other data relationships. Option A is incorrect because " Production Data Fix Tool " is not a standard standalone tool name provided in the base product for this purpose.
