Guidewire PolicyCenter Professional Exam with
accurate and verified questions covering
configuration, policy administration, data model
management, product model setup, user interface
customization, and integration points within the
Guidewire platform.
Which policy jobs can not be out of sequence? - ANSWER-
Submissions, renewals, and audits
What is an out of sequence transaction? - ANSWER-When a
change is made after the first one is bound but is supposed to go
effective before the first change (if no conflict, PC will merge
the changes, if there is a conflict, the user decides what to keep)
What is a group - ANSWER-A collection of users, producer
codes, queues, and regions created based on geographic regions,
divisions, and departments
,2|Page
Rules for groups (5) - ANSWER-1. Users can belong to more
than 1 group
2. An internal user can be assigned a producer code for any org
3. External users must be associated with an org
4. If Producer Code Security is set to "Yes" the user can only use
their role permissions against policies with a matching producer
code, even if they have a larger set of permissions available
through their roles
5. "Misassigned" category is for jobs assigned to groups but to
an invalid user. Activities and jobs can be mass reassigned.
How can managers and supervisors see what is going on with
the users in their groups? - ANSWER-The Team Tab allows
them to see all jobs and activities grouped by time and status.
They can mass reassign activities, and jobs, and can view policy
transactions by role or activity
Can view by role or by activity
Types of Producers (2) - ANSWER-1. Producer of Record -
Created the submission, receives commision based on the
premium
,3|Page
2. Producer of service - services the policy (usually the same as
the producer of record if a new policy - if different, they only get
commission after the policy is renewed)
What is a producer code - ANSWER-A unique ID assigned by
the insurer to track which agent/agency is responsible for which
policies and accounts
How to delegate role management to external users - ANSWER-
Use the "User admin role"
The can have access to ao build groups, org and permissions for
their own orgs but not others
Security in PC (2) - ANSWER-1. Role based security - a role is
a named collection of permissions that typically map to a jo
function or title
2. Date based security - defines what data can be access and
typically managed through producer codes
3 levels of assignment for external users - ANSWER-1. fully
restricted - only access to their own org
, 4|Page
2. protect internal - can be assigned producer codes from any
external org
3. allow internal - allow access to internal or external orgs
Samples of forms (5) (4) - ANSWER-1. declaration sheets - a
summary of all exposures and coverages
2. Base forms - attached regardless of what coverages or
exposure units are selected
3. Additional coverage forms - add additional coverage
4. Exclusion forms - limit forms
5. Manuscript forms - blank forms with space for free text
High level:
1. Policy forms form PC
2. Invoices from BC
3. Delinquency Letters from BC
4. Notification letters of new claims from CC