Free InsuranceSuite-Developer Practice Test Questions 2026

Answer Option (Which option is correct) B. si.pc.enhancements.entity, determineAuditType_Ext()
Explanation:

Place customer code in the customer namespace and organize it by product and purpose. Entity enhancements add reusable functions or computed properties without modifying generated entity classes. Use a getter for a value derived from existing fields and a function when a calculation needs an additional parameter.

Verification note: The selected function suffix is not explained for a custom entity. Verify enhancement naming and package conventions for the course version.

Why the other options are incorrect:

A. si.pc.enhancements.entity, determineAuditType():
The package is customer-specific. The function suffix differs from the selected answer. The need for that suffix on a custom entity is not established.

C. gw.job.audit, determineAuditType():
The gw namespace belongs to delivered Guidewire code. The question concerns an insurer customization. A customer namespace separates the implementation.

D. gw.entity.enhancement, determineAuditType_Ext():
This also uses the delivered gw package. Adding a method suffix does not establish customer package ownership. The package convention is a separate requirement.

References:

Guidewire-authored PolicyCenter 10.1.2 - Gosu naming and declarations

Gosu language project - Operators, loops, functions, and properties

Answer Option (Which option is correct) C. Prioritize errors that are recent and occur in large numbers.

Answer Option (Which option is correct) D. Share analysis with Guidewire Cloud Assurance for final determination.
Explanation:

Investigate the consistency errors, identify the responsible code or data path, and correct the cause before relying on a data repair. Use the appropriate review and testing process for production fixes. Promoting known bad data, waiting for arbitrary counts, or running an unreviewed repair immediately does not address that control process.

Verification note: The exact option selection could not be independently verified from accessible official documentation. Relevant official topic links are provided, but some exact configuration or training rules require the product Configuration Guide or Cloud Standards behind sign-in. The source key is retained.

Why the other options are incorrect:

A. Run the Production Data Fix Tool to correct these errors:
The generic DBCC overview does not prescribe this tool for the named category. Repair methods require the applicable support process. The exact Cloud Assurance policy has not been verified.

B. Fix these errors regardless of age or number of offending rows:
This treats every finding as equally urgent. The source instead distinguishes recency and count. The category-specific prioritization rule needs official confirmation.

E. Schedule weekly deployments of fixes until all errors are resolved:
A weekly schedule does not diagnose or prioritize the defects. It supplies a release cadence. The required review concerns the particular errors.

References:

Guidewire - Database consistency check scope and reports

Guidewire Cloud Standards - Sign-in required

Answer Option (Which option is correct) D. Integrate parent branch to defect branch
Explanation:

Local changes must be committed and synchronized with the shared repository before the shared build pipeline can use them. Integrating the parent branch exposes conflicts before merging, while pushing makes the completed work available to the remote repository and subsequent builds.

Verification note: The exact option selection could not be independently verified from accessible official documentation. Relevant official topic links are provided, but some exact configuration or training rules require the product Configuration Guide or Cloud Standards behind sign-in. The source key is retained.

Why the other options are incorrect:

A. Recreate the development branch:
Recreating the branch discards its existing working history. It is not the synchronization step selected here. Integrate the parent changes into the current fix branch.

B. Merge user story branch into parent branch:
Merging the fix is the destination step. The question asks what happens before that merge. The branch should first be checked against parent changes.

C. Clone the parent branch:
Cloning creates a repository copy. It does not integrate the latest parent commits into the existing fix branch. That integration must occur in the branch being merged.

References:

Guidewire - Source repository and build promotion

Git project - Commits and branch references

Guidewire - TeamCity builds and dependencies

Answer Option (Which option is correct) B. Define an entity name that concatenates the name fields and employee number.
Explanation:

Configure the entity name to combine the identifying fields that users need to see. This gives a consistent label wherever the entity is rendered by widgets that use its name. A setter changes state, a display key supplies localized text, and Post On Change refreshes widgets rather than defining the entity name.

Verification note: The exact option selection could not be independently verified from accessible official documentation. Relevant official topic links are provided, but some exact configuration or training rules require the product Configuration Guide or Cloud Standards behind sign-in. The source key is retained.

Why the other options are incorrect:

A. Enable Post On Change for name fields to modify how they display when the name is referenced:
Post On Change reacts to input edits. It does not define every employee label. The unique number belongs in the reusable entity name.

C. Create a setter property in a Name enhancement class:
A setter stores a value. It does not describe how the dropdown renders an employee. A display calculation is required.

D. Create a Displaykey that concatenates the name fields and employee number:
A display key supplies a text resource. It does not concatenate the fields of each employee automatically. The entity-name configuration targets those record values.

References:

Guidewire product documentation - Configuration Guide access

Answer Option (Which option is correct) D. Auditor_Ext.eti, License
Explanation:

A new custom entity is defined in an .eti file with a customer suffix on the entity name. A field belonging exclusively to that new custom entity generally does not need a second extension suffix. An .etx file instead extends an entity that already exists.

Why the other options are incorrect:

A. Auditor_Ext.eti, License_Ext:
The entity file correctly identifies a new custom entity. The source does not require another extension suffix on its own field. License is already scoped by the custom entity.

B. Auditor.etx, License_Ext:
An etx file assumes an existing Auditor entity. The scenario asks to create one. Use an eti definition for the new entity.

C. Auditor.eti, License_Ext:
The entity name lacks the custom suffix. The suffix on License does not distinguish the entity type. The source uses Auditor_Ext.

E. Auditor_Ext.etx, License:
An etx still extends an existing definition. A suffixed file name does not change that purpose. The new Auditor_Ext requires an eti file.

References:

Guidewire - Custom entity and subtype data model examples

Answer Option (Which option is correct) C. Improves application performance by reducing the size of the database.
Explanation:

Archiving moves eligible older business data out of the active database while retaining it for retrieval. A smaller active dataset can reduce the work involved in routine application operations; archiving is different from permanent purging, compression, or index rebuilding.

Why the other options are incorrect:

A. Re-indexes the contents of the database to increase data retrieval speed:
Reindexing rebuilds an access structure. It does not transfer old business records into an archive. Index maintenance is not the benefit asked about.

B. Reduces database size by permanently removing data marked for purge:
Purging permanently removes data. Archiving retains data outside the active store. The two lifecycle operations should not be equated.

D. Reorganizes and compresses the contents of the database to conserve space:
Compression changes physical storage representation. Archiving instead removes eligible records from the active dataset. These are different database operations.

References:

Guidewire - Archiving and active database performance

Answer Option (Which option is correct) D. Operations
Explanation:

Monitoring and logging are operational capabilities used to observe and support a deployed application. They belong to an Operations assessment rather than an upgrade check or a purely functional configuration check.

Verification note: The exact option selection could not be independently verified from accessible official documentation. Relevant official topic links are provided, but some exact configuration or training rules require the product Configuration Guide or Cloud Standards behind sign-in. The source key is retained.

Why the other options are incorrect:

A. Upgrades:
Upgrade checks address version-transition readiness. Monitoring and logging are operational support capabilities. Those concerns belong to a different assessment area.

B. Security:
Security checks can include observability requirements. The prompt specifically groups monitoring and logging under an assessment type. The PDF selects Operations rather than Security.

C. Performance:
Performance checks evaluate resource use and response behavior. They do not name the overall monitoring framework assessment. The source places this requirement under Operations.

References:

Guidewire - Automated Cloud Assurance and inspection sources

Guidewire Cloud Standards - Sign-in required

Answer Option (Which option is correct) C. Access TeamCity via Guidewire Home.

Answer Option (Which option is correct) E. Select the desired build configuration and trigger the build.
Explanation:

Select and run the appropriate TeamCity build configuration to produce a build for the intended source revision. The source describes subsequent build promotion from development through pre-production to production using Guidewire Home. A direct source-code commit to production is not the same as promoting a verified build.

Why the other options are incorrect:

A. Update the application's configuration resources in Lifecycle Manager:
Lifecycle configuration resources affect application setup. They are not the initial manual-build selection step. Choose the intended TeamCity build configuration.

B. Access the Automated Builds app in Guidewire Home:
The source specifically names access to TeamCity. This alternative uses a different app label. Its availability must be confirmed for the training release.

D. Configure a new monitor in Datadog:
A Datadog monitor observes events or metrics. It does not produce the Docker artifact. The build pipeline performs that task.

References:

Guidewire - TeamCity builds and dependencies

Guidewire - Source repository and build promotion

Answer Option (Which option is correct) D. Create a Detail View for the common properties of all watercraft and a set of Modal InputSets for the distinct property of each watercraft
Explanation:

Keep fields shared by all subtypes in a common DetailView and use modal InputSets for subtype-specific details. The InputSet reference selects its mode from the relevant type or line of business. This avoids duplicating the common layout and scattering visibility logic across many individual widgets.

Verification note: The exact option selection could not be independently verified from accessible official documentation. Relevant official topic links are provided, but some exact configuration or training rules require the product Configuration Guide or Cloud Standards behind sign-in. The source key is retained.

Why the other options are incorrect:

A. Create a Modal Detail View for each type of watercraft, duplicating common fields across each Detail View:
Duplicating common fields across detail views increases maintenance. The watercraft types share those values. A common detail view can hold them once.

B. Create a single page for all watercraft types with the visibility of fields distinct to the type of watercraft controlled at the widget level:
Widget-level visibility mixes every subtype field in one page. The selection rules become scattered. Modal InputSets keep type-specific fields together.

C. Create a set of Modal Pages for each type of watercraft:
Separate modal pages vary the entire page. Only the subtype properties need to vary. That introduces more duplicated structure than the selected design.

References:

Guidewire product documentation - Configuration Guide access

Answer Option (Which option is correct) A. Create more profiler tags to block out sections of code
Explanation:

Profiler tags divide custom processing into named timed sections. Adding tags around the suspected code makes otherwise unaccounted-for own time easier to attribute. Timestamps and ordinary logging do not add those named sections to the profiler result.

Verification note: The exact option selection could not be independently verified from accessible official documentation. Relevant official topic links are provided, but some exact configuration or training rules require the product Configuration Guide or Cloud Standards behind sign-in. The source key is retained.

Why the other options are incorrect:

B. Add more logging statements at the INFO level:
INFO logs create additional log output. They do not add named profiler frames. Use profiler instrumentation for the measured own time.

C. Use print statements to calculate the time spent in the code:
Print statements calculate timing independently. Their output is not automatically part of the profiler stack. The question asks for correlation within that profiler result.

D. Apply extra frames in the profiler output:
Extra frames cannot attribute code without instrumentation. The option does not specify a mechanism that records those frames. Tags around known sections provide the needed boundaries.

References:

Guidewire-authored PolicyCenter 10.1.2 - Web and entry-point profilers

Answer Option (Which option is correct) C. PCServerTestClassBase
Explanation:

A GUnit test needs an appropriate test base class and a valid test lifecycle. Tests that execute Gosu database queries need a server-capable environment. Test method naming and shared setup should follow the conventions of the target Guidewire release.

Verification note: The exact option selection could not be independently verified from accessible official documentation. Relevant official topic links are provided, but some exact configuration or training rules require the product Configuration Guide or Cloud Standards behind sign-in. The source key is retained.

Why the other options are incorrect:

A. PCUnitTestClassBase:
A unit-only base may not provide database-backed application services. The test executes a server query. The source selects a server-capable PolicyCenter base.

B. SuiteDBTestClassBase:
The name differs from the PolicyCenter class selected in the source. Its suitability cannot be confirmed from the question. The exact GUnit inheritance hierarchy needs documentation.

D. GUnitTestClassBase:
A generic GUnit base does not identify PolicyCenter server setup. The query needs the application test environment. Use the product-specific server base described in the PDF.

References:

Guidewire-authored PolicyCenter 10.1.2 - GUnit Testing Guide

Answer Option (Which option is correct) C. var count = job.Activities.countWhere(\act -> act.Priority == TC_HIGH); print(String.format("Count of High Priority Activities: %s", {count}))
Explanation:

countWhere expresses a count of elements satisfying a predicate without explicitly building a separate filtered list. In this question the predicate is the activity priority. An extra list conversion or a manual counter adds work or complexity to the same collection-level calculation.

Why the other options are incorrect:

A. var count = 0; job.Activities.each(\act -> act.Priority == TC_HIGH) { count += 1 }; print(String.format("Count of High Priority Activities: %s", {count})):
The each expression does not implement the displayed conditional counting syntax. It mixes a predicate and a following block. The shown countWhere expression states the count directly.

B. var actList = job.Activities.toList(); var count = actList.countWhere(\act -> act.Priority == TC_HIGH); print(String.format("Count of High Priority Activities: %s", {count})):
Converting to a list creates an additional collection representation. The original activity collection can be counted. That extra conversion is unnecessary here.

D. var count = 0; for (act in job.Activities) { if (act.Priority == TC_HIGH) { count += 1 } }; print(String.format("Count of High Priority Activities: %s", {count})):
A manual loop can count the matching activities. It requires an explicit mutable counter. countWhere expresses the same predicate more directly.

E. var count = 0; job.Activities.where(\act -> act.Priority == TC_HIGH) { count += 1 }; print(String.format("Count of High Priority Activities: %s", {count})):
where normally returns the filtered collection. The trailing counting block is not the shown collection-counting form. Use a count operation for the result.

References:

Gosu language project - Operators, loops, functions, and properties

Guidewire - Query-backed collections and buildBaseQuery