Pega Interview Questions for Freshers

1. Explain the decision table and decision tree in the context of Pega. What are the
differences between them?

Decision Table:

In case of a decision table, the values in a column in a decision table evaluate against the
same property/operator pair, such as Gender =. When developers need to analyse several
different combinations of the same set of properties or conditions in order to produce a single
value or property, they can use a decision table. For example, a corporation determines bonus
eligibility based on the number of years spent at the company and ratings on five employee
assessment measures.

Decision Tree:
In a decision tree, each branch compares the property/operator pair to a single value in order
to take an action, such as returning a value or evaluating a nested condition. When evaluating
requirements on multiple attributes that are reliant on other conditions, developers might
employ a decision tree. In a decision tree, each branch is assessed, and any branches that
evaluate to true perform the action that follows, such as continuing the evaluation to the
nested condition. A language learning software, for example, is doing significant A/B testing,
with some users receiving hearts and others receiving stars for their efforts. Hearts and stars
have their own properties with their own worth. Based on the number of hearts or stars linked
with the account, a decision tree examines the various prizes that users are qualified for.

When a comparison evaluates to true, both decision tables and decision trees analyze
characteristics or conditions to deliver outcomes. Decision trees evaluate against distinct
characteristics or conditions than decision tables, which evaluate against the same set of
qualities or conditions.

A business stakeholder or low-code developer can easily configure and change dependent
conditions that evaluate against distinct characteristics due to the decision tree's line-by-line
layout. When a decision table is used in a circumstance where several criteria evaluate
against the same property, the decision table will include empty boxes where a value is not
required for the conclusion. A business stakeholder or low-code developer can easily
configure and change a decision that evaluates against many of the same properties due to the
decision table's table structure.

Create a free personalised study plan

Get into your dream companies with expert guidance

Real-Life Problems

Prep for Target Roles

 Custom Plan Duration

Create My Plan

2. Explain data pages in the context of Pega.

A data page in a Pega Platform application retrieves data from a specified data source and
caches it in memory. The integration to the data source is managed by a data page, which
separates business activities from any integration details. This separation enables app
developers to use supplied data in their apps without having to know the data source or
connection specifics. Unlike most Pega Platform pages, applications seek to populate the
contents of a data page only when the page is requested, rather than through an explicit
action. Data pages are classified as declarative rules since their content is available on
demand. To distinguish a data page from other pages in memory, Pega Platform
automatically adds the characters D_ to the name.

A developer must give four crucial pieces of information when creating a data page. They are
as follows :

 Structure of the page

 Object Type of the page’s content
 Edit Mode supported
 Scope of the data page

3. What do you mean by an agent in the context of Pega? Explain.

An agent is a server's internal background process that performs actions on a regular basis.
Agents deliver email notifications about assignments and outgoing messages, generate
updated indexes for the full-text search feature, synchronize caches among nodes in a
multiple node system, and other system duties. Agents are self-contained and asynchronous:
the activities they invoke operate on their own timetables, and a second activity execution can
begin before the first one has finished.

Agents are defined by their own set of rules (Rule-Agent-Queue rule type). Agent Queue data
instances are used to enable and schedule agents (Data-Agent-Queue class). If potential
deadlock and other locking issues are appropriately managed by the activities in a multi node
cluster, an agent can execute on numerous nodes, even each node, to achieve high
throughput.

You can download a PDF version of Pega Interview Questions.

Download PDF

4. Explain declarative rule in the context of Pega.

A declarative rule is an instance of a subclass of the Rule-Declare-class.

In a Declare Expression, Constraints, Declare On Change, or Declare Trigger rule, we can

specify needed relationships among attributes. When the value of a property is involved in
any of these declarative rules, the system checks an internal dependency network for other
values that are affected and does other processing based on the network's configuration. This
is referred to as Forward chaining.
Most declarative rules are reevaluated after the following types of events:

 When users upload an input form, it is evaluated at the end of the input processing.
 During the execution of an activity, assessment takes place at each step, after the
method has completed but before the evaluation of a transition in that phase.
 As control passes from one job (one shape on the Visio flow diagram) to the next
during flow execution.
 When the work item progresses from one form to another and within connectors at the
end of a flow transition (if a relevant property is set).
 When the value of any of the attributes involved in the rule changes, index rules are
activated.
 When an object is saved to the database, trigger rules are activated.

Decision tree rules, decision table rules, and case match rules do not employ forward
chaining and are only assessed when explicitly requested.

5. Explain Rule Resolution in the context of Pega. What are its benefits?

The search technique used by the system to discover the best or most appropriate rule
instance to apply in a given is known as rule resolution.

Except for a few rule types — classes that inherit from the Rule- class — rule resolution
applies to all rule types. Instances of classes derived from the Work-, Data-, or any other base
class are not affected by rule resolution.

Despite the fact that the rule resolution process is fast and invisible, it is critical to
comprehend how it works. Make key component value selections based on how you want
rules to be found via rule resolution when you construct applications. The rule resolution
process can be speed up by using an in-memory rule cache. If the system discovers an
instance (or instances) of the rule in question in the cache, it accepts the candidate rules from
the cache and bypasses many steps in the resolution process.

The following are some of the advantages of rule resolution:

 Across apps and organizations, rules can be shared. Object-oriented software

development has many advantages, including sharing and reuse.
  More explicit rules stated at a lower level can override rules defined at a higher level.
While this reduces the value of sharing, it gives much-needed flexibility while
highlighting exceptions.
 Even inside a single rule-set, rules might have many versions, and security rules limit
which users view and execute which versions. This makes application development,
testing, and patching easier.
 With little conflicts and interference, a single Pega Platform system can host many
apps, multiple organizations, and multiple versions of a single application.
 Applications can be built independently of one another, but they can all be based on
the same set of rules that are locked (and hence will not change).

Explore InterviewBit’s Exclusive Live Events

By

No More Events to show!

6. What do you mean by workspace or studio in the context of Pega? What are the
different types of workspaces offered by Pega?

A workspace is a place where you can use specialized tools and functionalities. You may let
team members focus on tasks that fit with their expertise by using different workspaces to
create and administer your application.

Pega Platform offers four studios, or role-based authoring workspaces and they are as
follows:

 App Studio
 Dev Studio
 Prediction Studio
 Admin Studio
Each studio speeds up application development and increases productivity by giving users
role-based capabilities.

Using role-based workspaces in the Pega Platform can help you increase productivity. Users
may see what they require when they require it. Front-end developers, for example, can work
in one workspace to create interface channels, while system administrators can switch
between workspaces to configure additional features and monitor run-time outcomes.

Multiple workspaces are available to users. The system opens the default workspace when
users log in. Users have access to various workstations and can switch between studios.

7. Explain activities in the context of Pega. What are the best practices while using
activities?

Activities in Pega Platform automate processing. Activities are scripted in Dev Studio and
consist of a series of stages that must be completed in the order specified. When more
appropriate rule types are unavailable, usually due to more sophisticated computations or
procedures, or when a rule requires an activity to run, activity rules automate the system.
Declare On change, for example, necessitates the usage of an activity to start a process or
pause work when the value of a particular property changes. Control returns to the rule that
called the action after the activity is completed.

For example, an insurance firm is obligated to upload insurance claims to the Registry of
Motor Vehicles. To minimize the impact on users, automated uploads take place during off-
peak hours. An activity can be configured in Pega Platform to allow the system to automate
claim uploads without the need for user participation.
Following are some of the best practices that one should keep in mind while using activities
in Pega :

 Keep activities to a minimum. Limit your actions to no more than 25 steps, and make
sure that each one is focused on achieving a single goal.
 Use alternate rule types whenever possible, such as a data transform to set a property
value.
 Hand-coded Java should be kept to a minimum. When standard or custom rule types,
library functions, or activity methods are available, skip the Java stages in activities.

Start Your Coding Journey With Tracks

Master Data Structures and Algorithms with our Learning Tracks

Topic Buckets

Mock Assessments

Reading Material

View Tracks

8. Explain PRPC in the context of Pega. What are the benefits of PRPC?

PRPC stands for Pega Rules Process Commander. Pegasystems is built on the PRPC
foundation. It is totally model-driven, allowing the creation of dependable and efficient
applications without the use of any code, including SQL, Java, CSS, or HTML. PRPC is a
software platform that enables companies to combine all of their diverse, complex business
procedures and methods into a single platform. It allows you to combine multi-stream
processing into a single system by automating, documenting, and simplifying business
processes.
Pega PRPC is made up of two unique entities.

 Process Commander: Sets of pre-configured rules that serve as a foundation for

customization and development.
 Pega Rules: A Java-based Object-Oriented Rules Engine powers PEGA Rules.

PRPC attempts to achieve the following business benefits :

 Businesses can use the PRPC platform to combine all of their independent, separate,
and multiple business procedures and rules into a single platform.
 It enables corporate processes to be automated, documented, and streamlined.
 Multi-stream methods can be combined into a single system.
 Data can be transferred between frameworks and processed, segregated, and decoded.
 The purpose of PEGA PRPC is to cut down on the costs of any adjustments.

9. Explain Flow Action in the context of Pega. What are the different types of Flow
Actions available?

A flow action is a decision that users can make as an interim or final disposition for an
assignment they're working on. The Rule-Obj-FlowAction rule type is used to define each
flow action.
There are two sorts of flow actions:

 Connector Flow Actions: On a Visio presentation, connector flow actions appear as

lines in the Diagram tab of a flow rule. A line emerges from an assignment shape and
terminates at the flow's next shape. Users select a connector flow action during
runtime, complete the assignment, and move the work item along the connection to
the next form.
 Local Flow Actions: When a local flow action is selected at runtime, the assignment
remains open and on the worklist of the current user. The Assignment Properties
panel records local flow actions that aren't displayed on the flow diagram.

Take, for example, an application that facilitates employee recruitment operations. When
completing an assignment that requires the employee to evaluate the quality of a candidate
(based on a résumé and application form), the employee enters his judgments and reasoning
in the application and then selects one of three flow actions: Advance, Reject, or MoreInfo.
These flow actions may employ distinct user form displays, such as in the action section of a
perform harness or in a modal dialogue, and may require different input fields.

10. Explain Requestor Type in Pega. What are the different types of Requestor types in
Pega?