An insurer wants to add a new typecode for an alternate address to a base typelist EmployeeAddress that has not been extended.
Correct Answer: D
In the Guidewire InsuranceSuite framework, maintaining the integrity of the base configuration is paramount for ensuring a smooth upgrade path. This is achieved through a strict "extension-only" philosophy for out-of- the-box (OOTB) components. When a developer needs to modify a base typelist-like EmployeeAddress- they must understand the distinction between.tti (Typelist Interface)files and.ttx (Typelist Extension)files. A .tti file defines the original structure and initial typecodes of a typelist. These files are considered "base" and should never be edited directly (making Option C incorrect). If a developer were to modify the base .tti, those changes would be overwritten during the next platform update. To safely add a new typecode to an existing base typelist, Guidewire requires the creation of a .ttx file with the exact same name as the base typelist (e.g., EmployeeAddress.ttx). This extension file tells the Guidewire metadata engine to merge the new entries with the existing ones at runtime. Furthermore, Guidewire best practices for metadata extensions require specific naming conventions to prevent future "namespace collisions." While the .ttx file itself adopts the base name, the newtypecodeadded within that file should be suffixed with _Ext (e.g., alternate_Ext). This ensures that if Guidewire later releases a product update that adds an "alternate" code to the base EmployeeAddress typelist, the customer's custom code remains unique and does not conflict with the new base code. Option B is incorrect because you do not create a new .tti with an _Ext suffix for an existing list. Option E is incorrect because .tix is not a valid Guidewire metadata file extension; the correct extension is .ttx. Therefore, Option D is the only choice that follows the correct file creation and naming convention protocols required by the Guidewire development lifecycle.
Question 47
As a developer you are creating a new Gosu class for Succeed Insurance. According to the course material, which of the following statements define how you should implement logging in your new class? (Choose Two)
Correct Answer: C,D
In Guidewire development, logging is a critical tool for troubleshooting and monitoring, but it must be implemented with a focus on system performance and security. According to the Guidewire InsuranceSuite Developer guidelines, "excessive logging" is a common source of performance degradation. Developers are instructed to provide meaningful context for errors so that support teams can diagnose issues without needing to reproduce them manually. However, logging should be used judiciously; logging too much data (Option D) increases I/O overhead and can clutter logs, making it difficult to find relevant information. A specific best practice highlighted in the course material involves the use of theDebuglog level. Because debug messages often involve complex string concatenation or data retrieval that consumes CPU cycles, developers should wrap these calls in a conditional check. By using if (logger.isDebugEnabled()) (Option C), the system avoids the cost of constructing the log message entirely if the current logging level is set to a higher priority, such as INFO or WARN. This practice is essential for maintaining high throughput in a production environment where debug logging is typically disabled. Other options provided are contrary to Guidewire standards. For instance,Personal Identifiable Information (PII)(Option F) shouldneverbe logged in plain text due to data privacy regulations (GDPR/CCPA), and logging it at an INFO level would be a major security violation. Furthermore, while exceptions should be logged, not all exceptions are errors (some are expected business logic flows), and when they are logged, the stack trace is vital for debugging (refuting Option B). Guidewire Cloud primarily standardizes on structured logging (JSON) for observability, but the fundamental developer best practices regarding performance (C and D) remain the primary focus of the Fundamentals course.
Question 48
The Panel Ref in the screenshot below displays a List View with a toolbar. Add and Remove buttons have been added to the toolbar, but they appear in red, indicating an error. The Row Iterator has toAdd and toRemove buttons correctly defined. What needs to be configured to fix the error?
Correct Answer: C
In the GuidewirePage Configuration Framework (PCF), there is a strict functional relationship between toolbar buttons and the data they manipulate. When dealing withList Views (LVs), the "Add" and "Remove" buttons are specialized widgets known asIterator Buttons. According to theInsuranceSuite Developer Fundamentalscurriculum, placing an Iterator Button in a toolbar is only the first step. For the button to be valid, it must be linked to a specificRow Iteratorlocated within the List View. This is accomplished by setting theiteratorproperty on the Add or Remove button to theIDof the target Row Iterator. The red error in Guidewire Studio signifies a metadata validation failure. Even if the Row Iterator has the correct toAdd and toRemove logic defined (the "how" of the operation), the buttons themselves do not yet know "where" that logic resides. By setting the iterator property, you create a direct reference that tells the button which array of objects it is responsible for managing. Why other options are incorrect: * Option A:toCreateAndAdd is an optional property of the Row Iterator used for overriding the default object creation logic; it does not resolve the connection error between the button and the iterator. * Option B:addVisible and removeVisible are boolean expressions used to hide buttons based on user permissions or object state; they do not fix structural metadata errors. * Option D:The Visible property on an iterator affects whether the list is rendered, not whether the toolbar buttons are correctly linked. Linking the button to the iterator ID is a fundamental best practice that ensures the UI remains synchronized with the underlying data bundle.
Question 49
An insurer would like to include the Law Firm Specialty as part of the Law Firm ' s name whenever the name is displayed in a single widget. Which configurations follow best practices to meet this requirement?
Correct Answer: D
In Guidewire InsuranceSuite, the standard and most efficient way to define how an object identifies itself visually across the entire application is by using Entity Names. This is a declarative configuration found in the metadata layer (specifically within .en files). 1. The Centralized Approach (Option D) According to the InsuranceSuite Developer Fundamentals course, whenever a requirement asks for a consistent display format across " every widget " or " anywhere the name is displayed, " developers should use Entity Name configuration. By modifying the EntityName metadata for the Law Firm entity, you can define a template that concatenates the firm ' s name with its specialty (e.g., Name + " ( " + Specialty + " ) " ). This approach is considered a best practice for several reasons: * Consistency: It ensures that every dropdown, list view, and detail view automatically displays the firm in the correct format without needing to modify hundreds of individual PCF files. * Maintenance: If the business logic changes (e.g., they want to add the City instead of the Specialty), the change is made in exactly one place. * Performance: Entity Names are handled efficiently by the platform ' s display engine, avoiding the overhead of custom Gosu calculations every time a widget renders. 2. Why Other Options are Discouraged * Option B (Getter Method): While implementing a getter works, it requires you to manually point every single widget to this new property (e.g., LawFirm.FullDisplayName_Ext) instead of just using the standard entity reference. * Options C and G: These only solve the problem for a single List View. They do not address the requirement to show the combined information " whenever the name is displayed " in other parts of the UI, such as Detail Views or search results. * Option E (Custom Field): Storing a concatenated string in the database is a data redundancy anti- pattern. It creates extra storage overhead and requires complex logic to keep the concatenated string in sync whenever the Name or Specialty changes. By utilizing the Entity Name configuration, developers leverage the Guidewire platform ' s built-in " stringify " logic, which is the architecturally sound way to manage entity identity in the UI.
Question 50
What type of Assessment Check ensures that applications have monitoring and logging frameworks in place?
