GUIDEWIRE ASSOCIATE EXAM 2024 | ACCURATE REAL EXAM QUESTIONS WITH DETAILED ANSWERS, Exams of Computer Science

Download GUIDEWIRE ASSOCIATE EXAM 2024 | ACCURATE REAL EXAM QUESTIONS WITH DETAILED ANSWERS and more Exams Computer Science in PDF only on Docsity!

GUIDEWIRE ASSOCIATE EXAM 2024 | ACCURATE

REAL EXAM QUESTIONS WITH DETAILED ANSWERS

WITH A STUDY GUIDE | LATEST UPDATE | EXPERT

VERIFIED FOR GUARANTEED PASS

Which of the following are tools or resources that a Developer might use when configuring InsuranceSuite products? (Select 3)

• Guidewire Easy Guide
• Accelerators
• Release Planner
• Guidewire Studio
• Guidewire GO products

2, 4, &

• Accelerators
• Guidewire Studio
• Guidewire GO products

Which of the four principles of the Guidewire SurePath approach does this course (InsuranceSuite Implementation Tools) address?

• Optimize scope for base work and changes
• Follow Guidewire implementation guide rails and advice for solutions
• Leverage Guidewire content for common needs to reduce project effort
• Drive value by applying value alignment to prioritize discretionary spend

3

• Leverage Guidewire content for common needs to reduce project effort

What are the benefits of the Guidewire Community website? (Select 3)

• Provides access to product information in knowledge articles and documentation
• Provides opportunity to participate in discussion groups
• Provides access to training on the Guidewire Education portal

• Provides product accelerators for download
• Provides the ability to contact Guidewire Customer Support and case creation

1,2, & 5

• Provides access to product information in knowledge articles and documentation
• Provides opportunity to participate in discussion groups
• Provides the ability to contact Guidewire Customer Support and case creation

Which of the following are tools or resources that might be leveraged by an implementation team during inception? (Select 3)

• User Story Cards
• Business Process Flows
• Mind Maps
• Deployment Plans
• Accelerators

1, 2, &

• User Story Cards
• Business Process Flows
• Mind Maps

Which of the following are responsibilities of a Business Analyst on a Guidewire project? (Select

• Acts as a liaison with stakeholders to ensure clear communication between business and technical groups
• Participates in application specification discussions to define functional requirements and workflows
• Assists is defining concrete examples of system behaviors in Story Huddles when using BDD
• Facilitates the Agile process

1, 2, &

• Acts as a liaison with stakeholders to ensure clear communication between business and technical groups

• Participates in application specification discussions to define functional requirements and workflows
• Assists is defining concrete examples of system behaviors in Story Huddles when using BDD

What is the purpose of the Mockup UI tab in a story card?

• To describe the functional requirements for the UI
• To show the proposed user interface (UI) for the story
• To show the final user interface (UI) for the story
• To list the options for the Type keys

2

• To show the proposed user interface (UI) for the story

According to the story card best practices, when can you change a requirement number?

• You can change a requirement number before the requirement is published
• You can change a requirement number anytime
• You should never change a requirement number

1

• You can change a requirement number before the requirement is published

What are some common customizations of story cards?

• Adding an additional column for requirement numbers
• Creating an additional tab for integration
• Adding an additional column for dates
• Creating an additional tab for change management
• Removing the Document Control tab

1, 2, 3, &

• Adding an additional column for requirement numbers
• Creating an additional tab for integration
• Adding an additional column for dates
• Creating an additional tab for change management

What are the Product Owner's Responsibilities on a Guidewire project? (Select 3)

• Answers the development team's questions promptly and with authority
• Facilitates the agile process
• Acts as a key stakeholder representing the voice of the customer
• Signs off on user stories and defects

1, 3, &

• Answers the development team's questions promptly and with authority
• Acts as a key stakeholder representing the voice of the customer
• Signs off on user stories and defects

What are the Scrum Master's responsibilities on a Guidewire project (Select 3)

• Facilitates the Agile process
• Supports the sprint team
• Works closely with Developers and Quality Analysts during sprint execution so the right features are built
• Resolves impediments

1, 3, & 4

• Facilitates the Agile process
• Supports the sprint team
• Resolves impediments

What are the benefits of accelerators? (Select 4)

• They are extensions already developed by Guidewire or Partners to fill a common need
• They are easily available for download on the Marketplace website
• They become part of a customer's configuration and are supported by Guidewire
• They offer a complete solution for InsuranceSuite products
• They reduce implementation timelines by providing a good starting point

1, 2, 3, &

• They are extensions already developed by Guidewire or Partners to fill a common need
• They are easily available for download on the Marketplace website

• They become part of a customer's configuration and are supported by Guidewire
• They reduce implementation timelines by providing a good starting point

Place the items in correct order for the naming convention used for user story cards.

• Guidewire ID
• Theme
• xCenter with version
• Sub-Theme

3, 2, 4, 3 xCenter-Theme-Sub-theme-ID Number

When should acceptance criteria be written (Select 2)

• At the same time as the business requirement
• When writing the acceptance test
• Before development begins
• After writing the functional requirements

1, & 3

• Before development begins
• At the same time as the business requirement

Which of the following describe the purpose of a user story card (Select 3)

• To identify changes needed to satisfy business requirements
• To offer details of what has been implemented at the end of the project
• To document acceptance tests
• To hold descriptions of the user interface, business rules, and other requirements
• To describe standard product behavior only

1, 2, &

• To identify changes needed to satisfy business requirements

• To offer details of what has been implemented at the end of the project
• To hold descriptions of the user interface, business rules, and other requirements

What is the name of the tool that generates story cards?

• User Story Card Generator
• Jira
• Conceptual Sprint Planner
• Release Planner

1

• User Story Card Generator

What are the four main areas of configuration in a Guidewire application?

1. User Interface
2. Data Model
3. Application Logic
4. Integration

What are some of the technologies used in InsuranceSuite applications?

• Page Configuration Format (PCF) files
• Gosu (programming language)

What are some reasons for a non-developer to understand the technology stack?

• To determine what data is stored and if new requirements need additional data elements
• To know how and where data is used
• To communicate what data may be needed beyond what is in the base configuration
• To determine valid values or circumstances for the new data

What are some examples of what can be configured in the User Interface?

• The order of fields, change labels, regroup fields (simple changes)
• Fields on a screen (moderate change)

• Screens (complex change)
• Screen-based logic (complex change)

What are some examples of what can be configured in the Data Model?

• Information that the base application does not store (add passport number)
• Values for a Typelist (add valid values for AddressType of PhoneType)
• Data to support regulatory requirements

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

What are the 5 common areas of the UI architecture?

• The Screen Area
• The Sidebar
• The Tab Bar
• The Info Bar
• The Workspace

Name 3 components of a PCF

• Card
• ListView
• Button
• Text Input
• Contact Picker
• Radio Button
• Checkbox

What keyboard shortcut provides just the location information for a screen viewed in an InsuranceSuite product?

ALT + SHIFT + I displays the Location Info window

What tool does a developer use to configure InsuranceSuite products?

Guidewire Studio

What are the two main components of the data model?

Entities & Typelists

What is the purpose of the data dictionary?

• It shows the data elements that belong to entities and typelists
• How existing and custom fields can be configured

What are some of the relationships between entities

1. Fields - atomic data stored about the entity (non-restricted values
2. Type keys - a single reference to a value in a typelist
3. Array keys - a set of references to another entity
4. Foreign keys - a single reference to the id of another entity

Provide an example of why a non-developer should have a basic understanding on application logic?

• Most projects require some changes to application logic
• Non-developers define requirements for UI changes
• Non-developers help define requirements for Gosu rules
• Non-developers define requirements for business rules

Name two places where application logic exists?

• Gosu rules
• Business rules
• The User Interface

• Classes
• Entity Names

What are two types of rules? and who is responsible for developing each?

• Gosu rules: created by developers
• Business rules: created by non-developers

What is the purpose of integration?

Integration allows two systems to exchange data or perform work?

Why is it important for non-developers to have a basic understanding of integration?

Non-developers assist with documenting requirements including data mapping between the two systems and UI changes to communicate the requirements to developers

Name some common examples of InsuranceSuite integrations

• User Authentication
• Geocoding
• Check printing
• Document production
• Document management
• Address verification

What tasks are commonly performed by non-developers for integrations?

Non-developers often prepare data mapping documents and screen mockups needed to support integration development

What are the benefits of implementing InsuranceSuite using the base configuration?

• Transform business operations with innovation
• Keep current with technology trends in the industry
• Leverage product documentation, best practices, standards, and tools

• Leverage Guidewire consultants and expertise
• Leverage industry best practice built into InsuranceSuite applications

All of the Above

What are the potential impacts of reinventing legacy systems or features?

• Increased development time
• Decreased cost
• Performance Issues
• Increased maintenance responsibilities
• Limitations and challenges with upgrades

1, 3, 4, &

• Increased development time
• Performance Issues
• Increased maintenance responsibilities
• Limitations and challenges with upgrades

Identify strategies and tools you can use to avoid reinventing legacy systems and and features when implementing InsuranceSuite applications.

• Prepare for elaborating requirements by reviewing Inception Notes
• Use the legacy system requirements as a starting point
• Compare system changes to business objectives for alignment
• Leverage the benefits of sticking to the base configuration
• Refer to the Strategic Value Map to identify the value of the change
• Demonstrate standard functionality in the InsuranceSuite application that will accomplish the same results
• Point out the impacts to budget development time and maintenance management
• Refer to the process they are familiar with in their current system

1, 3, 4, 5, 6, &

• Prepare for elaborating requirements by reviewing Inception Notes
• Compare system changes to business objectives for alignment

• Leverage the benefits of sticking to the base configuration
• Refer to the Strategic Value Map to identify the value of the change
• Demonstrate standard functionality in the InsuranceSuite application that will accomplish the same results
• Point out the impacts to budget development time and maintenance management

Identify the Business Objective or Business Strategy that this requirement is aligned with:

Succeed Insurance wants users to be able to collect additional information about a business premises. It is important to know details about previous damage to buildings on the property, and any precautionary measures taken to protect the property, prior to issuing new insurance. This would include location, age of structure, evidence of subsidence, details of any structural damage that have occured since constructed, and added monitoring systems such as smoke detectors and burglar alarms. (Select one)

• Bring product and product changes to market faster
• Decrease reliance on IT for product maintenance
• Improve efficiency through increased straight-through processing
• Make changes to base configuration to gain competitive advantage
• Maintain Underwriting excellence with reduced loss experience
• Maintain Underwriting excellence with reduced loss experience

Which of the Guiding Principles below would you reference when making a decision about whether to implement the follow requirement:

For simple, small business that may be very budget conscious, Succeed Insurance currently offers customers the option of splitting their down payment into two payments. Succeed would like for the new system to automatically split a customer's large down payment into two payments. (Select all that apply)

• We are not bound by the way we have always done things in the past

• We will challenge current processes
• We will leverage best practices built into the Guidewire software
• We will drive adherence to product alignment to reduce total cost of ownership
• We will strive for common workflows, processes, and systems across the organization
• We will automate that which can and should be automated
• We will limit scope as far as practical to accelerate time-to-market

When marking a decision to change an InsuranceSuite application, weighing the impacts against ALL of the Guiding Principles can help ensure the decision is correct.

Which of the following describes the unique approach Guidewire recommends for elaborating requirements when leveraging standard features?

• Leverage functional requirements already available in user story cards for standard Guidewire products as a starting point
• Refer to the functional requirements that were used to implement the legacy system
• After everyone agrees to a solution for the requirement, functional requirements are documented from scratch

Leverage functional requirements already available in user story cards for standard Guidewire products as a starting point

Identify the common pitfalls to avoid when elaborating requirements to maximize the value of InsuranceSuite (Select all that apply)

• Referring to the standard user story cards for InsuranceSuite
• Suggesting requirements be placed on the backlog
• Allowing personal filters to influence requirements or solutions
• Accepting a solution offered as a requirement
• Asking questions that do not solicit details
• Assuming the requirement is correct or needed
• Confirming the requirement is aligned with the business objectives
• Determining the solution before the problem has been identified

3, 4, 5, 6, &

• Allowing personal filters to influence requirements or solutions
• Accepting a solution offered as a requirement
• Asking questions that do not solicit details
• Assuming the requirement is correct or needed
• Determining the solution before the problem has been identified

Who is responsible for driving the requirements elaboration workshop?

• Quality Analyst
• Developer
• Project Manager
• Business Analyst

Business Analyst

Match the best practice for elaborating requirements with the timeframe when they should be completed (Before a Requirements Workshop, During a Requirements Workshop, After a Requirements Workshop)

• Review inception notes and the standard system functionality
• Actively listen to the conversation about the requirement
• Escalate any risks or concerns to the Scrum Master
• Review inception notes and the standard functionality BEFORE a Requirements Workshop
• Actively listen to the conversation about a requirement DURING a Requirements Workshop
• Escalate any risks or concerns to the Scrum Master AFTER a Requirements Workshop
• Are used to limit acceptable values for a field
• Used for source of drop-down lists
• They contain a fixed set of values
• May be used by multiple fields
• The Data Dictionary Typelist pages show details
• Represents a predefined set of possible values

Typelist

Gap Analysis is performed in what phase of Guidewire project life cycle?

Inception phase

Definition of Done is considered in what phase of the Guidewire project life cycle?

Sprint 0 (Development phase)

Confirm scope in the goal of which phase of the Guidewire project lifecycle?

Inception

Inception events in order

1. Conceptual sprint plan
2. Infrastructure plan
3. Integration context diagram
4. High-level integrations design
5. Sandbox installed
6. Project resources are trained
7. Introduce Agile Concepts
8. Gap analysis

Role of the Product Owner on a project team

• 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

Common processes within each insurance product; a broad category of requirements, goals, or business priorities

Theme

Order of the layers of planning

1. Plan the program
2. Plan the project
3. Plan each release
4. Plan the iterations or sprints within the Release
5. Plan the daily Scrum

Resource used to drive inception elaboration and scope confirmation

User Story Cards

In what phase is story card reviewed to confirm scope and effort

Inception

A single reference to the id of another entity

Foreign Key

Gosu rules consist of...

1. A business object or Root object (e.g. Contract or Claim or Policy)
2. A condition that evaluates to true or false
3. An Action that executes if the condition is true, nothing happens if the condition is false

Shows definitions of Entities and Typelists

Data Dictionary

Information available in the Data Dictionary

The meaning of a field What fields are available Where the fields are available

Gosu Rules

• Created and maintained by developers
• Managed in Guidewire Studio
• Written in the Gosu language
• Available for many business purposes and business objects
• Capable of handling complex logic

Business Rules

• Created and maintained by non-developers
• Managed by Business Rules UI screens (in the administration screens)
• Available for limited business purposes and business objects
• Meant for simpler logic

Gosu rules high level business purposes

Approval Assignment Validation

Business rules high level business purposes

Activities Exposures Reserves

Components of a Business Rule

• Basic information: contains the name, description (optional) and triggering entity and action for this rule

• Applicability criteria: contains conditions to filter out the trigger entities this rule doesn't apply to (Can be specified or all rule types; Fields available change based on rule type)
• Rule conditions: contains one or more conditions which must be true in order to execute this rule's action
• Actions: contains the action to be performed if this rule's conditions are true

Guidewire Market place provides access to

Accelerators

Data Model makeup

Entities + Typelist

Steps of a Requirements Gathering Session in order

1. Demonstrate OOO product features
2. Identify user stories that support business processes
3. Elaborate requirements for user story
4. Write acceptance criteria for a story
5. Identify requirements that do not fit in standard user stories and user story gaps

Steps of elaboration activities in order

1. Schedule elaboration meeting
2. Discuss high level product functionality
3. Elaborate requirements for each user story related to theme
4. Determine gaps
5. Estimate each user story

Project team member who execute tests and coordinates with Developers accordingly

Quality Analyst

Accelerator

An accelerator is a pre-built solution or framework that provides a head start in implementing Guidewire software for specific insurance lines or business processes Provides good Starting Point

Extension

Functionality that is not part of a base product that have been developed by Guidewire, or Partners, to fill a common need; must be licensed and are supported product extension developed by Guidewire Product Development

Key deliverables of Inception Phase

• Estimated user stories
• Committed product backlog
• Conceptual sprint plan
• Infrastructure plan
• Integration context diagram
• Gap analysis
• High-level integration designs
• Sandbox installed
• Trained resources

Atomic data stored about the entity (non-restricted values)

Field

A set of references to another entity; Defines a set of additional related rows in another entity

Array Key

What are the delivery phases as per GW implementation methodology?

• Pre-Inception
• Inception
• Development

• Stabilization
• Stabilization
• Deployment
• Support and success

Key Deliverables of Pre-Inception Phase

• Business case completed
• Inception logistics established
• Inception workshops scheduled
• Business resources trained
• User stores mapped to business case
• Project governance defined
• Methodology aligned
• Project tools identified

2 key resources attending the elaboration session

SMEs and BA

User story best practices

Adding requirement ID for traceability Reviewing requirements with the team

How to can we modify user story cards? (Select 3)

• Adding tabs
• Adding column for capturing requirement id
• Adding column for capturing test result
• Adding requirements in UI mockup tab
• Adding tabs
• Adding column for capturing requirement id
• Adding column for capturing test result

High-level sprint plan outlined in an Excel template Outcome on Inception

Conceptual Sprint Plan

Benefit of knowing integration mechanism for non-developers

• Integration logic determines how InsuranceSuite applications communicate with external systems
• Non-developers define application requirements supporting integration
• Communicate requirements with integration and application developers

InsuranceSuite integration mechanisms

• Predefined plugins
• Web services
• Messaging
• Startable plugins
• Batch processes

When good requirements are written they ensure...

Viable solutions are created -- Identify what the insurer NEEDS instead of what they WANT or what they HAD in the past

A single reference to a value in a typelist Restricts the valid values to those in the type list

Type Key

Which of the following is available as common processes across Guidewire? (Select 2)

• Theme
• Application guide (User guide)
• Configuration Guide

• Theme
• Application guide (User guide)

What does acceptance criteria describe (Select 2)

• Describe when user story is done
• Value delivered to end user
• Checklist of activities that must be completed before accepting the story
• Describes user role, action and reason

1 & 2

• Describe when user story is done
• Value delivered to end user

Although business analysts are usually not involved in _____________ the design solution, but they are responsible for __________ the design solution.

• Implementing, documenting
• Communicating, Implementing
• Implementing, outsourcing
• Writing, Implementing

Implementing, documenting

Reasons for non-developers to understand the underlying technology

• Determine what data is present in OOTB configuration
• Know how data is used and documents change requests

Reasons for non-developers to understand UI architecture

• Request changes that are consistent with the base product architecture
• Ensure consistent look and feel

Which of the following are true about UI architecture?

• Consists of Screen area, side bar, tab bar, info bar, workspace
• Has familiar look and feel for all products

How are UI changes made?

User Interface (UI) changes are made in components called Page Configuration Format (PCF's)

Non developers define business logic requirements for

• UI functionality
• Rule conditions and actions
• Application processing flow

Common roles on implementation project

BA, QA and DEV

Responsibilities of business analyst (Select 1)

• Documenting requirements and answering questions on system functionality
• Voice of customer
• Acts as liaison between sales, SME and technical team
• Documenting requirements and answering questions on system functionality

Which phase ensures quality of the system for production deployment?

Stabilization

Best practice during elaboration session

Do: a. Listen to the conversation b. Use standard workflows and screens as a starting point c. Focus on "happy path" first, then edge cases d. Use parking lot for off topic items Do not:

a. Permit more than one conversation at a time b. Duplicate the legacy system c. Be afraid to suggest: "Let us put that on the backlog" when out of scope d. Revisit decisions

Key Deliverables of Development Phase

Planned Sprint Sprint Backlog Accepted User Stories Production Quality Burn down Reports Updated Velocity Reports Reprioritized Backlog

Impact of UI changes that are consistent with base product architecture?

• Ensure consistent look and feel
• Simplify new user learning experience
• Reduce development time
• Simplify maintenance and upgrades
• Reduce likelihood of performance impacts

Why Non-Developers should understand Data model

• Understanding the underlying data improves configuration decisions
• When a new field is needed on a screen, it is useful to know if it already exists

Foreign Key example

Claim entity's AssignedUser → User entity's ID Stores a reference to a related object in the data model

Regulatory Requirement

Ensures compliance with state and federal regulations

Non-developers define application requirements supporting integration including...

• Data mapping between systems
• UI changes to support new data
• Timing - will the integration execute automatically, on demand, or on a schedule
• What triggers the integration - user action, creation or update of data, and so on

Non-developer understanding of Integration Mechanisms?

• How data is shared between InsuranceSuite and other systems
• Integrations move data to and from InsuranceSuite

Which phases in the Guidewire project lifecycle are divided into sprints?

• Inception
• Development
• Stabilization

Cross Functional team success factors:

• Frequent communication
• Co-located teams
• Empowered decision making
• Active business involvement
• Leverage value and product alignment

What is a user story?

• Ex: as a , I want to so that
• High-level requirements from a user's perspective
• Often captured on index cards or sticky notes during early planning sessions

Good User Stories

I - Independent N - Negotiable V - Valuable E - Estimable S - Small T - Testable

Story elaboration goal is identifying value driven changes to ootb story, who are key stakeholders?

BA's, SME, PO's

What does it mean to elaborate a user story?

Conversations occur between the users and the team to ensure all requirements are understood Elaboration session benefits Benefits:

• Help the team better understand the requirements
• Are an important part of the knowledge transfer between Guidewire and the project team resources
• Led by Guidewire at the start of the project
• Eventually led by the Customer as the project progresses

How each role uses acceptance criteria (BA, Dev, QAs, POs):

BAs - capture them during requirements gathering Developers - use them to configure and code requirements QAs - use them to define test cases and derive pass/fail status POs - use them to confirm if a user story can be accepted

Guiding principle

• Should be established by the insurer's leadership team
• Leadership can convey how the insurer stands on common challenges and what is important to the company