試験InsuranceSuite-Developer トピック1 問題65 スレッド

In Guidewire InsuranceSuite development, performance is heavily dependent on how data is retrieved from the relational database. When dealing with potentially large datasets, such as the Claim entity, it is critical to perform filtering at thedatabase level(via SQL WHERE clauses) rather than at theapplication level(in Gosu memory).
The GuidewireQuery APIprovides the primary mechanism for constructing these database-level filters. When a developer creates a query object (e.g., gw.api.database.Query.make(Claim)), they must use specific methods to define the criteria that will be translated into a SQL query. The compare() method is the standard approach for adding these constraints. It allows the developer to specify the property (such as CreateTime), the comparison operator (such as GreaterThan), and the value (the specific date). Because the compare() method is called directly on the Query object before the query is executed, the filtering happens within the database engine.
In contrast, methods like where() or filter() used on acollectionor aQueryBuilderresult (Option A, C, and E) often trigger the execution of the query first, fetching all records into the Gosu application server's memory, and then discarding the ones that don't match. This "in-memory filtering" leads to severe performance degradation, high memory consumption, and potential "Out of Memory" errors. Option D correctly utilizes the Query API's ability to refine the result set at the source. Understanding the lifecycle of a query-from construction using compare() to execution-is a fundamental skill for any Guidewire developer to ensure the application remains scalable and responsive under high data volumes.