Download Guidewire Insurance Suite Analyst Exam Questions and Solutions and more Exams Insurance law in PDF only on Docsity!
1 / 23
INSURANCE SUITE ANALYST EXAM
QUESTIONS WITH SOLUTION
1. What is the core programming language for Guidewire? Gosu
- What does application logic control? Detail behavior of the application
- Code is used in....: Rules, Classes, Extensions
- What can be configured?: Validation, Assignment, Function
- Rules: Validation, assignment, approval routing
- Classes: Functions that return calculated values & set values in fields
- Extensions: Added functionality to entities
- Validation: Specific rules for what data is required
- Assignments: Specific criteria for assigning objects to groups and users
- Function: Calculate the number of days since a loss date
- How is configuration done by developers?: Through Guidewire Studio
- What 5 common UI areas do all Insurance Suite products share?: Screen Area, Sidebar, Tab
Bar, Info Bar, Workspace
13. What does having a common UI architecture ensure?: Familiar look and feel & reduced training
time
14. What area displays the business information?: Screen Area
- What area provides navigational menu links?: Sidebar Area
- Quick Jump Box: Provides a fast way to navigate within the GW application
2 / 23
17. What determines the Tab Bar that a user sees?: User's permission
18. What the purpose Info Bar?: Shows summary information relevant to the user's
currently selected item (combo of text and icons)
19. What is the Workspace used for?: Display info while keeping the Screen Area visible to
display additional info
20. What is used to build the GW UI?: Widgets
21. Widgets: - Display app info to the user/render info into displayable format
- Support data entry
- Organize data into logical groupings
22. Different Functions/Types of Widgets: Data entry, Actions, Organize info, Containers
23. List Views: Widget used to display a list of related data
24. How to find location info? (Keyboard shortcut): ALT + SHIFT + I (Location Info window)
25. Why would you what to find the Location info?: To help the developers identify the file
they will need to make changes to in order to satisfy Business requirements
26. How to find widget info? (Keyboard Shortcut): ALT + SHIFT + W (Widget Inspector)
27. What is a developer's role in configuration/project implementation team?-
: To configure IS products to satisfy the customer's reqs by using the GW Studio tool
28. Why is it important for non-developers to understand the basics of the UI architecture and
components?: So that they can request changes to the UI that are consistent with the base product architecture and communicate effectively with developers
4 / 23
42. Typelist: droplist; A set of code/value pairs/typecodes that are valid for a field
43. What 2 main components make up the data model?: Entities and Typelists
44. Fields: Store atomic data about entity (i.e.. claim report date or Weather Related claim)
(dates)
45. Type keys: Reference a single acceptable value in a typelist (i.e.. accident type or claim
source) (dropdowns)
46. Array keys: a set of references to another entity (multiple rows) (i.e.. addresses or incidents)
(lists)
47. Foreign keys: a single reference to another entity (single row) (i.e. catastrophe or assigned
group) (codes/ account numbers)
5 / 23
48. Data field: Where a single value is stored; can be physically in the database or virtually
created by Gosu code
49. Foreign Key Field: Stores a reference to a related object in the data model; unidirectional
relationship ie. Assigned User in Claim IS)
50. Array: Associates a set of related rows with the main entity; multidirectional relationship
51. What are the 3 main sections of the data dictionary?: Data Entities, Typelists and All Fields
52. What are the 2 specialized versions of Data Entities? And who are they used by?: - Database
and Migration view
- Used by the implementation team
53. What does the Data Dictionary show?: - The meaning of a field
- What fields are available
- Where the field is used in GW UI
54. Type filter: Creates a subset of values valid for the type of claim; filter within type key within
type list
55. What can an array key used for in Claim Center?: Linking several exposures with an incident
(lost/damaged things), then linking several incidents with a claim
56. What is the purpose of the Data Dictionary?: To show the data elements that belong to
entities and typelists
57. What are some relationships between entities?: Foreign Keys, Array Keys, and Type Keys
58. Application logic: Code written in Gosu that determines behavior and function- ality within
GW IS
7 / 23
67. Approval Rules: Triggered by creation or update of a financial transaction
68. Assignment Rules: Triggered by creation of business objects that can be assigned (ie.
claims, activities, exposures)
69. Validation Rules: Triggered by creation or update of activity, claim, contact, exposure;
different from assignment rules because it can be triggered by an update and even wider variety of business objects
70. What does a Gosu rule consist of?: A condition that is either true or false, and an action that
is executed
71. Gosu Rules: Non-developer responsibilities: - Determine business reqs for condition and
action logic
- Communicate requirements to developers
72. Gosu Rules: Developer responsibilities: - Determine correct category for rule
- Code and test the rule logic
73. How do non-developers use business rules?: Used to create Activities, Ex- posures, and
Reserves
74. What are the 4 components of a Business rule?: -Basic info
-Applicability criteria -Rule conditions
75. Applicability criteria: Filter to limit the trigger entities this rule applies to; used to get more
8 / 23 specific on what entities a BA wants this rule to apply to
76. What triggers an Exposure rule?: The creation of an incident
77. What triggers a Reserve rule?: The creation of an exposure
78. What are 3 things an activity rule can generate?: -new activity for the claim's workplan
-generate a history event -set the value of a field
79. What logic can be configured in PCFs?: Simple logic can be used in the UI configuration of
field and screen behavior; Screen behavior = Button, links, and menu items to change the screen and navigate the app
80. What logic can be configured in Classes? and what are the responsibilities of each role?: -New
computed values or business logic -Non-developer: documents reqs for calculations or formatting changes -Developer: writes code, determines if the code applies to one or multiple objects, implements the req and tests it
81. How are Gosu classes determined?: They are based on Business objects
82. Utility classes: handle common, reusable tasks and calculations
83. How do GW apps use entity names?: To represent a business object as a text string
84. Entity names: Text displayed in the UI for business objects
85. Can entity names be modified?: Yes, if the insurance carrier wants to include different info.
ONLY developers can create and modify entity names
86. How is logic configured into an entity name?: two or more information/logic fields can be
combined to create an entity name (ie. order number of claim + los party + exposure type +
10 / 23
90. What are the 2 types of rules and who is responsible for developing each?: - Business
Rules; non-developers
91. Integration: The exchange of data or requests to perform work between two systems
92. What does integration allow insurers to do?: Integration allows insurers to continue using
services used with their legacy systems with IS products while adding new capabilities
93. What is the value of Integration?: -Benefit from external applications main- tained by
industry specialists -Outsource common tasks -Eliminate time and expense of building in-house
94. What are common GW Integration points?: -Authentication systems
-Doc management systems -Address book application systems
95. Why understand Integration?: -To assist with documenting reqs and commu- nicating them to
developers (Data mapping between systems) -Integ. logic determines how IS apps communicate with external systems (written in Gosu)
- Timing -Understanding what triggers the integration and triggers in general
96. IS Integration Mechanisms: -Predefined plugins
-Web Services
- Messaging -Startable plugins
11 / 23 -Batch processes
97. Predefined plugins: Gosu classes that a GW app invokes to perform an action or calculate a
result at a specific time in its business logic
98. Web Services: Define request-and-response APIs that let you call an API on a remote
computer or get info from an remote computer; XML-based information exchange system; GW can both publish and consume internet web services
99. Messaging: GW app is programmed to send a message to an external system when an
important event occurs. (ie. A change triggers and event that executes Gosu code) External system only receives messages for successful events and sends an ac- knowledgement that the message was received in response
100. Startable plugins: Custom code that begins executing during server startup; not evoked
by another code but can be stopped and started as required; listens for requests from an external system
101. Batch processes: Run in the background and perform tasks independent of an admin;
execute on a batch server; reports results to a log or the user interface; Runs according to a schedule/periodic basis and is not triggered by a specific event
102. What are 2 examples of predefined plugins?: Authentication plugins and Geocoding
plugins
103. What is a messaging mechanism that can be used in Startable plugins?-
: Java Message Service (JMS)
104. What is the purpose of integration?: To allow two systems to exchange dat or perform
work
105. Names some common examples of IS Integration.: User authentication Geocoding
13 / 23 functionality and identifies requirements for any changes needed -Confirm scope, estimate, and plan the project iterations
14 / 23 -Introduce Agile concepts
113. What are the key Inception deliverables?: -Estimated user stories
-Committed product backlog -Conceptional sprint plan -Infrastructure plan -Integration context diagram -Gap analysis -High-level integration designs -Sandbox installed -Trained resources
114. What are points and T-shirt sizes?: Iteration (3-4 week sprint) = The suitcase Velocity =
How many T-shirts can fit in the suitcase Points = Relative size of T-shirts-Fibonacci 1 pt - XS 2 pts - S 3 pts - M 5 pts - L 8 pts - XL 13 pts - XXL
115. Development - Sprint 0: Goal: Prepare for and plan for development execution 2 to 4
week initial transition sprint to Development Plan development and prepare development team
116. What are the key Sprint 0 deliverables?: -Set up Development environments
16 / 23
124. Deployment: -Goal: To enable End Users to start using the system in produc- tion
-Series of Deployments, typically starting with a Pilot Deployment -Data Migration from Legacy system(s) to New System -Training of New End Users (internal and external) -Communication with Customers
125. Support & Success: -Goal: Realize the value of the production GW system
-Triage Issues, plan regular maintenance updates -Monitor business and system processes for health -Respond to enhancement requests -Assess value realized from new system against business case
126. What are some success factors for Cross-Functional teams?: -Frequent Communication
-Co-located teams -Empowered decision making -Active business involvement -Leverage Value and Product Alignment
127. What are the 4 principles of Sure Path?: -Optimize Scope (eliminate unnec- essary
activities) -Leverage Content (streamline implementation plan) -Drive Value (Apply value alignment to prioritize discretionary spend) -Guided Implementation (provide guide rails for implementation solutions)
128. During the Deployment phase, what happens during the Pilot step?: - Allow a subset of
users to use the system
17 / 23
- Triage feedback
- Implement changes as needed
129. Product Owner (PO): -Key stakeholder representing the voice of the customer
-Business authority to make decisions (can delegate to key SMEs) -Shares vision with the development team -Collaborates with the teams to develop and deliver the work -Defines requirements and answers the development team's questions promptly and with authority -Responsible for signing off on user stories and defects -Does not write requirements or tests during development ~Drives Value~
130. Project Manager: -Supports the sprint team
-Facilities the agile process -Enables self-organization -Resolves impediments -Shields outside interference -Is a participatory leader, not a dictating manager, servant leader -Identifies project resource gaps -Manages change control with the PMO -Manages project issues & risk with the PMO ~Facilitates Progress~
131. Subject Matter Expert (SME): -Define business objectives and future-state processes
-Participate in requirements gathering sessions
19 / 23 Should Have Co- Could Have W- Will Not Have (for now)
141. How are Themes broken down?: Themes > Features/Subthemes > User stories >
Tasks
142. When is a high-level sprint plan developed?: At the end of inception
143. How are User Stories grouped?: By Theme and Feature
144. Accelerators: pre-built code or reference implementations to help reduce de- veloper
work
145. What is the best practice for project planning?: Plan for what you know and then re-
evaluate your plan as needed
146. What does Guidewire provide as a starting point for your project?: GW provides approx.
5000 reusable assets/tools to facilitate progress during the imple- mentation project
147. What are the goals for inception?: Confirm Scope, Validate Sizing, Baseline the Project
148. What are some objectives for inception?: -Formally kick off the project
-Train the team on base product and methodology -Introduce the team to agile concepts -Determine an approach to address any product gaps -Document the high-level design (HLD) for integrations -Explain estimation changes as a result of the workshops
149. What are the 3 activity groupings? and how long should they last?: -
-Overview and Kickoff (1-2 weeks) -User Story Elaboration (2-10 weeks)
20 / 23 -Sizing and Planning (1-5 weeks)
150. Elaboration sessions: The objective of elaboration sessions during Inception is to
identify gaps and refine estimates; not intended to flesh out detailed require- ments
151. What does GW mean by Inception?: An phase to confirm the scope of the project ,
produce an initial sizing, and create the project baseline
152. Who typically attends Inception?: Product owners, SME, BAs, developers, and testers
153. Why does GW timebox Inception?: To avoid collecting excessive details
154. What are the steps to plan a delivery sprint?: 1. Determine team capacity
2.Define Sprint Backlog
3.Validate estimate for each user story
4.Define tasks for each user story in the sprint
-Assign a resource to each task -Estimate each task
5.Add new user stories and tasks as needed
6.Repeat steps 1-5 until sprint capacity is full
155. What are some planning best practices?: -Standardize sizing guidelines and task list
-Move stories to sprints according to the conceptual sprint plan -only estimate tasks and hours for stories in current sprint -decide how you will baseline the project -Define how you will handle group tasks and guiding principles
156. How/When do we estimate stories?: By Points system at the start if the project and
