GUIDEWIRE BEST PRACTICES
ACTUAL EXAM 2026/2027 | Study
Guide | Examination Questions | Verified
Q&A | Pass Guaranteed - A+ Graded
SECTION 1: CONFIGURATION BEST PRACTICES
Study Notes: PCF Guidelines & Gosu Coding Standards
PCF (Page Configuration File) Best Practices:
● Avoid placing code in the CODE tab of PCF files; create UI helper classes instead
● Avoid extending entity enhancements with UI-specific code
● Follow upgrade-safe naming conventions with _Ext suffix for customizations
● Use appropriate widget selection based on data type and user interaction needs
Gosu Coding Standards:
● Package Naming: Use format customer.application.featurecategory.feature (e.g.,
si.suite.integration.authentication)
● Class Naming: Use UpperCamelCase; do NOT add _Ext suffix to classes within customer
package spaces
● Function Naming: Use lowerCamelCase with descriptive verbs (e.g., verifyAddress)
● Variable Naming: Member variables use lowerCamelCase with leading underscore (e.g.,
_pluginCallbackHandler); local variables use short descriptive lowerCamelCase names
● Logical Operators: Use text "and", "or", "not" instead of symbols "&&", "||", "!"
● Typecode References: Use static properties (e.g., LossCause.TC_REAREND) instead of string
literals ("rearend")
● Whitespace: Add spaces around operators; indent logical blocks by two spaces only; add
blank line after code blocks; add two blank lines after methods
● Comments: Use Javadoc-style comments for classes/functions; use single-line comments
within functions to clarify intent; use GosuDoc annotations
Upgrade-Safe Naming (_Ext suffix required for):
● Columns added to existing entities
● Typecodes added to existing typelists
, ● Custom entity names
● Custom typelist names
● New PCF files
● Script parameters
Anti-patterns to Avoid:
● Using com.guidewire.* internal paths (subject to change during upgrades)
● Placing code in PCF CODE tabs
● Using deprecated classes/methods
● Extending entity enhancements with UI code
● Using string literals for typecodes instead of static properties
Practice Questions: Configuration Best Practices
Q1. A developer needs to add a new custom field to the Policy entity. According to Guidewire
upgrade-safe naming conventions, how should this column be named?
A) customField
B) CustomField
C) customField_Ext [CORRECT]
D) PolicyCustomField
Rationale: The _Ext suffix must be added to columns added to existing entities to ensure
upgrade safety and distinguish customizations from base product. Option A lacks the suffix,
B uses incorrect casing, and D doesn't follow the entity field naming pattern .
Q2. Which of the following is the correct way to reference a typecode in Gosu code?
A) "rearend" (string literal)
B) LossCause.TC_REAREND [CORRECT]
C) LossCause.rearend
D) Typecode("rearend")
Rationale: Always use the static property on the typelist class (TC_REAREND) instead of
string representations. This provides compile-time checking and prevents errors from typos
or typecode changes .
, Q3. According to Gosu coding standards, which logical operator format should be used?
A) &&, ||, !
B) AND, OR, NOT
C) and, or, not [CORRECT]
D) &, |, ~
Rationale: Guidewire standards specify using text words "and", "or", and "not" instead of
symbols for better readability and consistency .
Q4. A developer is creating a new PCF file for a custom screen. Where should business logic
code be placed?
A) In the CODE tab of the PCF file
B) In a UI helper class [CORRECT]
C) In an entity enhancement
D) Directly in the PCF XML
Rationale: Avoid placing code in PCF CODE tabs; create UI helper classes instead. This
promotes separation of concerns, reusability, and easier maintenance. Entity enhancements
should not contain UI-specific code .
Q5. What is the correct package naming convention for a custom authentication feature in
the suite application for a customer named "acme"?
A) com.guidewire.authentication
B) acme.suite.authentication
C) acme.suite.security.authentication [CORRECT]
D) authentication.acme.suite
Rationale: The format is customer.application.featurecategory.feature. Here:
customer=acme, application=suite, featurecategory=security (implied),
ACTUAL EXAM 2026/2027 | Study
Guide | Examination Questions | Verified
Q&A | Pass Guaranteed - A+ Graded
SECTION 1: CONFIGURATION BEST PRACTICES
Study Notes: PCF Guidelines & Gosu Coding Standards
PCF (Page Configuration File) Best Practices:
● Avoid placing code in the CODE tab of PCF files; create UI helper classes instead
● Avoid extending entity enhancements with UI-specific code
● Follow upgrade-safe naming conventions with _Ext suffix for customizations
● Use appropriate widget selection based on data type and user interaction needs
Gosu Coding Standards:
● Package Naming: Use format customer.application.featurecategory.feature (e.g.,
si.suite.integration.authentication)
● Class Naming: Use UpperCamelCase; do NOT add _Ext suffix to classes within customer
package spaces
● Function Naming: Use lowerCamelCase with descriptive verbs (e.g., verifyAddress)
● Variable Naming: Member variables use lowerCamelCase with leading underscore (e.g.,
_pluginCallbackHandler); local variables use short descriptive lowerCamelCase names
● Logical Operators: Use text "and", "or", "not" instead of symbols "&&", "||", "!"
● Typecode References: Use static properties (e.g., LossCause.TC_REAREND) instead of string
literals ("rearend")
● Whitespace: Add spaces around operators; indent logical blocks by two spaces only; add
blank line after code blocks; add two blank lines after methods
● Comments: Use Javadoc-style comments for classes/functions; use single-line comments
within functions to clarify intent; use GosuDoc annotations
Upgrade-Safe Naming (_Ext suffix required for):
● Columns added to existing entities
● Typecodes added to existing typelists
, ● Custom entity names
● Custom typelist names
● New PCF files
● Script parameters
Anti-patterns to Avoid:
● Using com.guidewire.* internal paths (subject to change during upgrades)
● Placing code in PCF CODE tabs
● Using deprecated classes/methods
● Extending entity enhancements with UI code
● Using string literals for typecodes instead of static properties
Practice Questions: Configuration Best Practices
Q1. A developer needs to add a new custom field to the Policy entity. According to Guidewire
upgrade-safe naming conventions, how should this column be named?
A) customField
B) CustomField
C) customField_Ext [CORRECT]
D) PolicyCustomField
Rationale: The _Ext suffix must be added to columns added to existing entities to ensure
upgrade safety and distinguish customizations from base product. Option A lacks the suffix,
B uses incorrect casing, and D doesn't follow the entity field naming pattern .
Q2. Which of the following is the correct way to reference a typecode in Gosu code?
A) "rearend" (string literal)
B) LossCause.TC_REAREND [CORRECT]
C) LossCause.rearend
D) Typecode("rearend")
Rationale: Always use the static property on the typelist class (TC_REAREND) instead of
string representations. This provides compile-time checking and prevents errors from typos
or typecode changes .
, Q3. According to Gosu coding standards, which logical operator format should be used?
A) &&, ||, !
B) AND, OR, NOT
C) and, or, not [CORRECT]
D) &, |, ~
Rationale: Guidewire standards specify using text words "and", "or", and "not" instead of
symbols for better readability and consistency .
Q4. A developer is creating a new PCF file for a custom screen. Where should business logic
code be placed?
A) In the CODE tab of the PCF file
B) In a UI helper class [CORRECT]
C) In an entity enhancement
D) Directly in the PCF XML
Rationale: Avoid placing code in PCF CODE tabs; create UI helper classes instead. This
promotes separation of concerns, reusability, and easier maintenance. Entity enhancements
should not contain UI-specific code .
Q5. What is the correct package naming convention for a custom authentication feature in
the suite application for a customer named "acme"?
A) com.guidewire.authentication
B) acme.suite.authentication
C) acme.suite.security.authentication [CORRECT]
D) authentication.acme.suite
Rationale: The format is customer.application.featurecategory.feature. Here:
customer=acme, application=suite, featurecategory=security (implied),
