A business analyst provided a requirement to create a list of Payment Types accepted by...

When a developer needs to introduce an entirely new set of values that does not exist in the base InsuranceSuite product, they must create anew Typelist. According to the Guidewire Data Model architecture, the proper way to define a new, customer-specific typelist is by creating a.tti (Typelist Interface)file within theExtensionsfolder of the configuration.

Following the naming conventions established for Guidewire Cloud and InsuranceSuite extensions, any new metadata object created by a customer should include the_Extsuffix. Therefore, the typelist should be named PaymentType_Ext.tti (Option C). This suffix clearly distinguishes the insurer's custom metadata from any current or future "Out of the Box" (OOTB) typelists provided by Guidewire. By placing it in the Extensions -> Typelist folder, the developer ensures that the new list is recognized by the metadata compiler and correctly integrated into the application.

It is important to understand why the other options are incorrect:

Option A:Uses a .ttx file. .ttx files are used only toextend existingbase typelists (adding new codes to a list Guidewire already provides). They cannot be used to define a brand-new list.

Option B:Uses a .tix extension, which is not a valid Guidewire metadata extension, and places it in the Metadata folder, which is reserved for base product files.

Option D:Places a .tti in the Metadata folder without the required _Ext suffix, which violates the upgrade-safety principle and risks a name collision with future base product updates.