Guidewire Best Practices Exam study guide
ACTUAL EXAM Questions & Answers |
Already Graded A+ UPDATE 2025|2026 –
JUST RELEASED!!
1. Guidewire Query API General Best Practices -
ANSWER ✓ Use the property reference
(EntityType#Property) for type-safe access to the
properties on the query entity type
Use the property reference to filter query results, join to
another entity type, order rows in the result set, or to
specify a column for a row query
Use query.contains() after other query.compare()
operations against indexed columns for better
performance against large data sets
2. Guidewire Query API - Denormalized columns
improve performance of - ANSWER ✓ Ends with
searches
,Case-insensitive searches
3. Guidewire Query API Anti-Patterns - Bring back only
the data you need by - ANSWER ✓ Avoid filtering query
results in memory
Avoid filtering query results in the application server
Perform filtering in the database
Avoid the use of where(), first(), last(), firstWhere(), and
lastWhere()
4. Guidewire Query API Anti-Patterns - use dot notation
with care because - ANSWER ✓ accessing foreign keys
or array fields retrieve additional entities into memory
5. Guidewire Query API Anti-Patterns - Check for
existence of an entity when the number of results is not
important by - ANSWER ✓ Verifying the results of a
targeted query are not empty
Avoiding hasMatch(), countWhere(), and select().Count
,6. Guidewire Query API Anti-Patterns - When a count is
necessary, let the database count the entities and -
ANSWER ✓ Avoid countWhere()
Avoid counting collections
Avoid iterating over entities from the database to count
them
Avoid counting entities before accessing them
Avoid countWhere() and select().Count
7. Guidewire Query API Anti-Patterns - Avoid queries to
check for new or changed entities, instead - ANSWER ✓
Use Boolean methods getChangedFields,
getAddedArrayElements, getChangedArrayElements,
and getRemovedArrayElements
Use specialized methods that test for new or changed
entities when available
(Claim.PolicyChanged)
8. Guidewire Query API Anti-Patterns - Avoid queries to
access new or changed entities by - ANSWER ✓ Use
, Boolean methods getChanged, isFieldChanged,
isArrayElementAddedOrRemoved, and
isArrayElementChanged
Check the Gosu API for specialized methods on entities
9. Guidewire Query API Advanced Concepts - Entity
queries - ANSWER ✓ should be used unless performance
is not adequate
10. Guidewire Query API Advanced Concepts - Row
queries - ANSWER ✓ Use a single database query on the
main entity and related entities to return only the data
columns you select from the database
Allow you to use only the values contained the query
results
Filter the rows returned from the database using
query.compare
Involve more code maintenance and should only be used
when performance issues are encountered with an entity
query
ACTUAL EXAM Questions & Answers |
Already Graded A+ UPDATE 2025|2026 –
JUST RELEASED!!
1. Guidewire Query API General Best Practices -
ANSWER ✓ Use the property reference
(EntityType#Property) for type-safe access to the
properties on the query entity type
Use the property reference to filter query results, join to
another entity type, order rows in the result set, or to
specify a column for a row query
Use query.contains() after other query.compare()
operations against indexed columns for better
performance against large data sets
2. Guidewire Query API - Denormalized columns
improve performance of - ANSWER ✓ Ends with
searches
,Case-insensitive searches
3. Guidewire Query API Anti-Patterns - Bring back only
the data you need by - ANSWER ✓ Avoid filtering query
results in memory
Avoid filtering query results in the application server
Perform filtering in the database
Avoid the use of where(), first(), last(), firstWhere(), and
lastWhere()
4. Guidewire Query API Anti-Patterns - use dot notation
with care because - ANSWER ✓ accessing foreign keys
or array fields retrieve additional entities into memory
5. Guidewire Query API Anti-Patterns - Check for
existence of an entity when the number of results is not
important by - ANSWER ✓ Verifying the results of a
targeted query are not empty
Avoiding hasMatch(), countWhere(), and select().Count
,6. Guidewire Query API Anti-Patterns - When a count is
necessary, let the database count the entities and -
ANSWER ✓ Avoid countWhere()
Avoid counting collections
Avoid iterating over entities from the database to count
them
Avoid counting entities before accessing them
Avoid countWhere() and select().Count
7. Guidewire Query API Anti-Patterns - Avoid queries to
check for new or changed entities, instead - ANSWER ✓
Use Boolean methods getChangedFields,
getAddedArrayElements, getChangedArrayElements,
and getRemovedArrayElements
Use specialized methods that test for new or changed
entities when available
(Claim.PolicyChanged)
8. Guidewire Query API Anti-Patterns - Avoid queries to
access new or changed entities by - ANSWER ✓ Use
, Boolean methods getChanged, isFieldChanged,
isArrayElementAddedOrRemoved, and
isArrayElementChanged
Check the Gosu API for specialized methods on entities
9. Guidewire Query API Advanced Concepts - Entity
queries - ANSWER ✓ should be used unless performance
is not adequate
10. Guidewire Query API Advanced Concepts - Row
queries - ANSWER ✓ Use a single database query on the
main entity and related entities to return only the data
columns you select from the database
Allow you to use only the values contained the query
results
Filter the rows returned from the database using
query.compare
Involve more code maintenance and should only be used
when performance issues are encountered with an entity
query
