Update 2025/2026| Real-Based Questions with
Verified Answers| Graded A+
2 Ways to create documents - Correct Answers-1. Upload an electronic file to the Document
Management System
2. Create a new doc using a PC template, creating a local copy on the Document Production
system, ultimately uploaded to the Document Management System
3 levels of assignment for external users - Correct Answers-1. fully restricted - only access to
their own org
2. protect internal - can be assigned producer codes from any external org
3. allow internal - allow access to internal or external orgs
3 statuses of policies getting renewed - Correct Answers-Renewed
Not Taken
Non-renewed
4 types of info in a security dictionary - Correct Answers-A series of HTML pages
documenting roels and permissions for the application
1. Application permission keys
2. Pages (in UI)
3. System Permissions
4. Roles
A Policy Line contains: (5) - Correct Answers-1. Exclusions
2. Conditions
3. Modifiers
4. Coverage
5. Forms
,Actions related to a Contingency (3) - Correct Answers-1. Changing the policy
2. Cancelling the policy
3. Cancelling and rewriting the policy
Activity Lifecycle (5) - Correct Answers-1. In Progress - New/Updated (Star icon)
2. In Progress (viewed) - Normal (Star disappears)
3. Overdue - Due date turns red
4. Escalated - exclamation appears
5. Closed - Completed or skipped (disappears from list)
Activity Ownership - Correct Answers-Explicit - calls out person
Implicit - calls out person's role
Activity Patterns - Correct Answers-Standardize the way PC created activities
Activity queue - Correct Answers-an activity repository assocaited with the group so people
can go in and assign themselves the next activity in the queue (need the Actqueuenext
permission)
Audit Process Steps (6) - Correct Answers-1. Audit Task starts an audit job
2. Audit - draft policy transaction ready
3. Each Item becomes a link to the audit wizard so the user can enter info
4. Enter Audit Details
5. Calculate Premiums
6. Submit - Audit Non-editable
BA challenges with documenting functional requirements (7) - Correct Answers-1. Identifying
and defining the business requirement
2. Taking a business requirement to the feature level
3. Breaking down features into user stories
4. Prioritizing and Planning user stories
5. Analyzing "what if" scenarios or edge case management
, 6. Identifying impacts to other systems
7. Writing testable requirements
Best practices in documenting functional requirements (5) - Correct Answers-1. Create
testable requirements
2. Never document a requirement in more than 1 place
3. Document only what you want the system to do (not what you don't want)
4. Keep track of all stories associated with a feature
5. Always review a requirement with the team prior to implementation
Blocking point - Correct Answers-Stops the progress of a job until an issue is approved (some
issues can be informational (non-blocking)
Checking set - Correct Answers-A point in the job where issues can be raised (Pre-quote,
Bind, Pre-issuance)
Clauses and subclauses - Correct Answers-These are groups of coverages
A clause can have 1 or 0 parents clauses
A clause can have multiple subclauses of multiple levels
Color codes in sotry cards - Correct Answers-Dark Green - Coverage attributes
Light Green - Coverage Term Attributes
Lightest green - Coverage Term Option attributes
Components of UW authority - Correct Answers-UW Issue - a specific occurance on a policy
transaction where an UW condition was true. Created when a condition gives undesirable
results based on data on the policy or account. These can stop jobs until approved
UW Rule - Describes how the policy transaction is affected by the UW issues and how issues can
be approved. Rules include conditions which will raise an UW issue
Authority Grant - The ability to approve UW issues and to what degree
Authority profile - a group of authorities that can be given to a user, allowing the user to
approve UW issues