Mock Exam. Practise all the questions from the Pega Academy.
Use DCO to enter business requirements for the application to facilitate direct engagement of IT and business resources.
Build and test the application before rolling it out for review by interested parties to ensure the application is ready for release
Identify the departments responsible for the application design and have them work independently to enhance organizational efficiency.
Build the required features as soon as they are needed during application development to keep the project moving quickly.
Guardrails help developers to track compliance with Pega's best practices.
Guardrails help developers build applications that are easier to maintain and have fewer defects.
Guardrails help managers create schedules for efficiently allocating developer resources.
Guardrails help project managers ensure that applications are completed on time.
Guide the development team with guidelines on how to manage the project development.
Show technical users how to use Pega developer tools for collecting customer information.
Ensure all team members have a common understanding of how a case is processed and resolved.
Help estimate the total time required for the case life cycle to produce a new policy.
Conduct interview
Collect personal information
Determine compensation
Assess candidate
Confirm
Employee confirmation
Confirm employee
Confirm employee and employer
Stage
Step
Process
Case
To the current user
To a work queue
To a specific user
To the reporting manager
The amount of time allowed before the case automatically advances to the next assignment
The amount of time in which the case or step must be completed
The amount of time allowed for a user to advance a case to the next stage
The amount of time in which the case or step should be completed
Track assignment status over time
Assign cases to the appropriate case worker
Help ensure timely completion of assignments
Generate service level reports
How will users enter values in those fields?
Will the information be stored in an external database?
Will users want to see information displayed using different styles?
What fields do users need to see?
Can users modify the values or only read the values?
Passwords must be at least eight characters.
Require HR VP approval for sabbatical leave.
Reduce inaccurate claims to less than 10 percent of all claims.
Allow up to 200 concurrent users.
A user should be able to cancel an order at any time.
Eliminate order processing delays due to incorrect routing of requests.
User must be able to select "Add Temporary Member" when "Authorization is Required" notice is displayed.
System displays "Authorization History and Summary" for the last 12 months.
If the complainant type is "Provider," then provider information must be populated during the Triage Stage in the Basic Research Step.
Reduce time needed for time-off approvals from three weeks to one.
The product catalog should be easy to navigate.
User passwords shall be encrypted using AES-256 encryption.
A requirement describes what the business need is, and specifications describe how the application will meet the business need.
A requirement provides a blueprint for how the application will meet the goals defined in a specification.
A requirement defines a specific step in a process; a specification defines a complete process.
There is no difference between a requirement and a specification.
Define the expected flow of events in the life cycle of a case.
Organize process steps that are not part of the normal course of events.
Represent an alternative flow of the case life cycle sequenced from beginning to end.
Define the tasks that users accomplish while the case is in the stage.
Add a local action to the case type.
Add a step in a process.
Add a process in a stage.
Add an optional process to any stage in the case type.
Reassign any task that remains open after three days to another user.
Requiring a separate approval process whenever an order exceeds USD 10,000.
An application randomly sends a survey to customers once their case is resolved.
Allow a user to transfer a case to another employee at any stage of the case.
How will the correspondence be sent?
How often should you send the correspondence?
Who is the user that receives the correspondence?
When does the correspondence need to be sent?
Which email server should the correspondence use?
Automating correspondence allows you to advance a case.
Automating correspondence keeps all interested parties informed of the current status of a case.
Automating correspondence allows you to send timely communication.
Automating correspondence allows for sending consistent information to users.
Defines what the step should do.
Describes to an end user what should be done in the step.
Describes the business value of the step.
Instructs an architect how to build the step.
Only if the user manually updates the case status
The status of a case cannot be automatically updated
At the beginning of the step
At the end of the step
Indicate possible branches of a process.
Indicate an automated action performed by the application.
Identify the order of events in a process.
Indicate an event handled by a user.
Identify an outcome of a decision.
Provide statistics on how work is performed in Pega applications
Describe and measure what the organization's work is
Define the data types for an application
Manage data instances for an application
Create reports
Create process metrics
Delete reports
Create business metrics
Identify business objectives for an application
Define application requirements
Configure UI forms
Develop feature prototypes
System Architect
Senior System Architect
Lead System Architect
Business Architect
Business architects
Business stakeholders
By adding the ruleset that contains the property to the application.
By applying directed inheritance.
By naming PegaRULES as the built-on application.
By applying pattern inheritance.
The class of the rule.
The type of the rule.
The description of the rule.
The status of the rule.
The application that uses the rule.
Create one data element in the organization layer, for both applications to use.
Check the inheritance path to determine if an appropriate data element is already available.
Create a data element for each case type, since they may use different status values.
Create one data element in the framework layer, for both applications to use.
The application runs the checked-out version of the rule, because that is the most up-to-date version of the rule.
The application ignores the checked-out version and uses the previous version in the application ruleset.
The application cannot run because the rule is unavailable.
The application returns and error and stops processing the case, because the rule is unavailable for use.
Application
Access group
Operator ID
Data structure, processes
Case type, cases
Case, case types
Top-level case , child cases
Make both loan request and appraisal peer case types.
Make mortgage a parent case type. Make loan request and appraisal child case types.
Make loan request a parent case type, and appraisal a child case type.
Make appraisal a parent case type, and loan request a child case type.
PO-11 can be resolved when either of Pay-37 and Pac-56 is resolved.
Pac-56 has to be resolved before Pay-37 is resolved.
Both Pay-37 and Pac-56 have to be resolved before PO-11 is resolved.
PO-11 has to be resolved before either of Pay-37 and Pac-56 be resolved.
Page list
Value list
Page group
Page
Field group (list)
Text (paragraph)
Radio button
Picklist
Value group
Single value
Text
Page
Set default values when creating a case
Copy data between pages
Create properties after the case has been created
Execute a flow action
To use the superclass feature
To initialize property values when a case is created
To set internal case properties, never override pyDefault
To propagate property values from a parent to a subcase
The system monitors input properties and determines when to update the target property value.
A declare expression updates the total value on all the forms when any form containing the field is submitted.
To update the calculation, you only update one rule making the application easier to maintain.
A declare expression calculates a specific value that is used on multiple forms.
To calculate the total interest rate value, add the all the declare expression target property values.
Specify forward chaining in the declare expression that calculates the total interest rate value.
Specify backward chaining in the total interest rate declare expression.
Apply the declare expression in the approval flow action.
Total cost for the hotel room
Price of each option
Total cost of options
Number of days at the hotel
Subcases and a spin-off cases
Any cases
Subcases only
Its parent case and any subcases
Whenever a parent's value changes
When a parent's value changes and a data transform is used to configure the data propagation
When a subcase's or spin-off case’s value changes
When the subcase or spin-off case is created
A data transform
A decision tree
The property mapper
A data page
Information about the Pega server.
Information about the current operator.
Data cached from an outside system.
Information about a case.
Test a rule to determine whether the rule executes correctly.
Test case behavior by setting property values for an open case.
Review the current values of case data.
Test whether a declarative expression properly calculates a target value.
Parsing data from an external system
Copying a page into a page list property
Updating properties values from one page using properties of another page
Initializing properties values of a new case instance
Label
Description
When
Jump
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Recent Quizzes
Featured Quizzes
Wait!
Here's an interesting quiz for you.