PEGA SSA Exam with all Correct & 100% Verified Answers
|Actual Complete Update |Already Graded A+
Organization layer ✔Correct Answer-contains the assets used on an enterprise-wide basis.
Such assets are rules for enterprise-wide business logic such as standard properties, decision
tables, and service level rules.
Enterprise Class Structure ✔Correct Answer-class hierarchy structure
Pega Platform Layer ✔Correct Answer-contains the built-in assets necessary for processing
cases and other work in Pega applications. This layer also contains the assets Pega Platform
uses.
Division layer ✔Correct Answer-This layer is the middle level of the three-level organization
hierarchy and is available for use in every application.
Framework Layer ✔Correct Answer-contains assets that can be extended in specific
implementations. It may be comprised of one or more generalized applications, such as a
standard Pega application for a specific industry, or an extendable custom application.
Implementation layer ✔Correct Answer-defines an application customized for a specific
division or line of business. It may extend one or more framework layer applications
Lock and roll ✔Correct Answer-Small changes or patches are ideal for lock and roll. Creates a
new empty ruleset. Minor and major versions require application record and access group
updates. Patches usually do not need the updates. May want to reserve space when updating.
Labor intensive for major updates
Skimming ✔Correct Answer-Skimming is the process of saving the highest version of a rule
into a new, higher ruleset version. Skimming applies mainly to resolved rules. Skimming is useful
when rule changes follow a logical sequence. The two types of skims are minor and major. The
skim types correspond with the update types (major or minor/patch). for minor rules
withdrawn are carried forward
Rule Availability: Yes ✔Correct Answer-This rule is carried forward (multiple answers)
Rule Availability: Blocked ✔Correct Answer-This rule is carried forward (multiple answers)
Rule Availability: Final ✔Correct Answer-This rule is carried forward (multiple answers)
Rule Availability: Withdrawn ✔Correct Answer-This rule is not carried forward but is if its a
minor skim
,Rule Availability: No ✔Correct Answer-This rule is not carried forward
Pega skimming wizard ✔Correct Answer-For each rule instance in a specified ruleset, the
wizard identifies the highest-numbered version and creates a copy with the number you specify.
Accessing lock and roll ✔Correct Answer-Configure > Application > Structure > RuleSet Stack
page
Do not update my application (lock and roll) ✔Correct Answer-You use Do not update my
application when you update the patch version number of a ruleset without updating the
application ruleset list. By default, the application rule only lists the major and minor version
numbers for a ruleset, so incrementing the patch version number does not require a change to
the application rule.
Update my application (lock and roll) ✔Correct Answer-You use Update my Application to
include the new Ruleset Versions when you are rolling out an application and updating the
minor version or when the application rule lists the ruleset patch version number. You may
enter a new application description. The default application description is current. If the current
application is locked, enter the application password.
Create a new version of my application (lock and roll) ✔Correct Answer-You use Create a new
version of my application when:
You want to lock and roll the version and create a new application rule. You may enter a new
application version, if different than the default one increment higher. You may enter a new
application description. The default application description is current. If the current application
is locked, enter the application password.
You want to allow people access to more than one version of the application (for example,
during a phased roll-out or a test period).
Accessing skimming ✔Correct Answer-Configure > System >Refactor > RuleSets page
Skimming (Requirements for updating application rules) ✔Correct Answer-You must update
application rules, the Requires RuleSets and Versions prerequisites array in RuleSet version
rules, and access groups to reference the new major version after the skim completes. Log out
and log in to access the new version.
zipMoveSkim privilege ✔Correct Answer-This is required to run a skim Pega provides a default
role for system architects which includes zipMoveSkim. SysAdm4 is the default system role for
system architects and includes the zipMoveSkim privilege. When an application is in production,
the SysAdm4 role becomes the Administrator role.
The New Application wizard creates the initial application rulesets. ✔Correct Answer-the
created rulesets include two rulesets for the application itself and two organizational rulesets.
,Production rulesets ✔Correct Answer-have at least one unlocked ruleset version in the
production environment. Commonly delegated rules. Configured on the application and access
group
Application validation mode ✔Correct Answer-If the AV mode is used, rules in the ruleset can
reference all rules in the rulesets defined in the:
Same application
Rulesets belonging to any built-on application
Rules in the ruleset cannot reference rules outside the current application stack or above the
defining application.
Validation tool ✔Correct Answer-Dev Studio > Configure > Application >Tools > Validation
allows for quick identification of invalid rules
Ruleset validation mode ✔Correct Answer-each ruleset version defines one or more ruleset
versions on which the ruleset version depends. If your ruleset version does not have any
prerequisite ruleset versions, you need to specify the base product ruleset Pega-
ProcessCommander as a prerequisite.
Ruleset best practices ✔Correct Answer-Only use RV for rulesets that are designed to be used
across multiple applications, such as organizational rulesets, to make them easily portable and
prevent the introduction of dependencies on a specific application.
Create applications for common rulesets; use the built-on functionality to include common
rulesets in the application.
Include unlocked AV rulesets in one application only. Doing so prevents AV rulesets from
referring to rules that may not exist in applications that do not contain the ruleset.
Run the Validation tool after implementation of critical changes or milestones (for example,
changes to the application ruleset list or built-on application as well as changes made before
lock/export).
ruleset list, sometimes referred to as the ruleset stack ✔Correct Answer-governs rule
execution at run time
Accessing ruleset list ✔Correct Answer-Operator > Profile.
personal ruleset ✔Correct Answer-if you are allowed to check out rules and has the name of
the operator ID and contains the rules checked out by the operator.
The ruleset list for the application with built-on applications can be viewed on the ruleset list
landing page ✔Correct Answer-(Dev Studio > Configure > Application > Structure > RuleSet
Stack).
, Ruleset locking ✔Correct Answer-You can lock a ruleset to prevent changes using the Lock and
Save button. Typically, you lock rulesets when development has reached a specific state, and the
application is ready to be promoted to testing. You cannot add or update rules in a locked
ruleset.
Rule checkout and check-in ✔Correct Answer-A team typically develops applications. Multiple
team members may check out rules to work on the same application in a coordinated manner.
The checkout feature ensures that different team members are not editing one rule at the same
time.
The system enforces the use of checkout and check-in operations when a ruleset has the
checkout facility enabled. Before you can change that rule, you must perform either the
standard checkout or private checkout operation.
Configuring ability to check out rules ✔Correct Answer-When you check out a rule, you are
creating a private copy of the rule that you can modify and test.
On the Security tab on the ruleset, select Use check-out? to enable checkout. On the Operator
record Security tab, operators need to have the Allow Rule Check out selected in order to
update rules in rulesets that require checkout. If a rule is not available for checkout, it is already
checked out by someone else, or it is in a locked ruleset version.
Check in a rule ✔Correct Answer-When a rule is checked in, the checked-in rule replaces the
original base rule. Add a comment describing the changes to the rule. You can view the check-in
comments on the rule History tab.
Use the bulk action feature to check in, open, or delete several checked out rules at the same
time. The bulk action feature is located in the Private Explorer menu or under the check mark
icon in the header.
Parallel development ✔Correct Answer-When multiple teams are working in the same
application rulesets, coordinating changes across teams is a challenge. When development
teams configure an application in parallel, rule changes might result in conflicts. Resolving
conflicts disrupts the overall project and may delay time to delivery.
Branch ✔Correct Answer-is a container for rulesets with records that are undergoing rapid
change and development. In Pega, you create a branch for each team. These branches allow
each team to create and update rules without impacting other teams.
Branch rulesets ✔Correct Answer-The rulesets associated with a branch. Is based on
(branched from) another ruleset
Contains rules that are in active development in the associated branch
To develop rules in parallel using branched rulesets, each team follows these steps: ✔Correct
Answer-1. Creates a team application built on the main application
2. Creates one or more development branches in the team application
3. Grants access to the team application
|Actual Complete Update |Already Graded A+
Organization layer ✔Correct Answer-contains the assets used on an enterprise-wide basis.
Such assets are rules for enterprise-wide business logic such as standard properties, decision
tables, and service level rules.
Enterprise Class Structure ✔Correct Answer-class hierarchy structure
Pega Platform Layer ✔Correct Answer-contains the built-in assets necessary for processing
cases and other work in Pega applications. This layer also contains the assets Pega Platform
uses.
Division layer ✔Correct Answer-This layer is the middle level of the three-level organization
hierarchy and is available for use in every application.
Framework Layer ✔Correct Answer-contains assets that can be extended in specific
implementations. It may be comprised of one or more generalized applications, such as a
standard Pega application for a specific industry, or an extendable custom application.
Implementation layer ✔Correct Answer-defines an application customized for a specific
division or line of business. It may extend one or more framework layer applications
Lock and roll ✔Correct Answer-Small changes or patches are ideal for lock and roll. Creates a
new empty ruleset. Minor and major versions require application record and access group
updates. Patches usually do not need the updates. May want to reserve space when updating.
Labor intensive for major updates
Skimming ✔Correct Answer-Skimming is the process of saving the highest version of a rule
into a new, higher ruleset version. Skimming applies mainly to resolved rules. Skimming is useful
when rule changes follow a logical sequence. The two types of skims are minor and major. The
skim types correspond with the update types (major or minor/patch). for minor rules
withdrawn are carried forward
Rule Availability: Yes ✔Correct Answer-This rule is carried forward (multiple answers)
Rule Availability: Blocked ✔Correct Answer-This rule is carried forward (multiple answers)
Rule Availability: Final ✔Correct Answer-This rule is carried forward (multiple answers)
Rule Availability: Withdrawn ✔Correct Answer-This rule is not carried forward but is if its a
minor skim
,Rule Availability: No ✔Correct Answer-This rule is not carried forward
Pega skimming wizard ✔Correct Answer-For each rule instance in a specified ruleset, the
wizard identifies the highest-numbered version and creates a copy with the number you specify.
Accessing lock and roll ✔Correct Answer-Configure > Application > Structure > RuleSet Stack
page
Do not update my application (lock and roll) ✔Correct Answer-You use Do not update my
application when you update the patch version number of a ruleset without updating the
application ruleset list. By default, the application rule only lists the major and minor version
numbers for a ruleset, so incrementing the patch version number does not require a change to
the application rule.
Update my application (lock and roll) ✔Correct Answer-You use Update my Application to
include the new Ruleset Versions when you are rolling out an application and updating the
minor version or when the application rule lists the ruleset patch version number. You may
enter a new application description. The default application description is current. If the current
application is locked, enter the application password.
Create a new version of my application (lock and roll) ✔Correct Answer-You use Create a new
version of my application when:
You want to lock and roll the version and create a new application rule. You may enter a new
application version, if different than the default one increment higher. You may enter a new
application description. The default application description is current. If the current application
is locked, enter the application password.
You want to allow people access to more than one version of the application (for example,
during a phased roll-out or a test period).
Accessing skimming ✔Correct Answer-Configure > System >Refactor > RuleSets page
Skimming (Requirements for updating application rules) ✔Correct Answer-You must update
application rules, the Requires RuleSets and Versions prerequisites array in RuleSet version
rules, and access groups to reference the new major version after the skim completes. Log out
and log in to access the new version.
zipMoveSkim privilege ✔Correct Answer-This is required to run a skim Pega provides a default
role for system architects which includes zipMoveSkim. SysAdm4 is the default system role for
system architects and includes the zipMoveSkim privilege. When an application is in production,
the SysAdm4 role becomes the Administrator role.
The New Application wizard creates the initial application rulesets. ✔Correct Answer-the
created rulesets include two rulesets for the application itself and two organizational rulesets.
,Production rulesets ✔Correct Answer-have at least one unlocked ruleset version in the
production environment. Commonly delegated rules. Configured on the application and access
group
Application validation mode ✔Correct Answer-If the AV mode is used, rules in the ruleset can
reference all rules in the rulesets defined in the:
Same application
Rulesets belonging to any built-on application
Rules in the ruleset cannot reference rules outside the current application stack or above the
defining application.
Validation tool ✔Correct Answer-Dev Studio > Configure > Application >Tools > Validation
allows for quick identification of invalid rules
Ruleset validation mode ✔Correct Answer-each ruleset version defines one or more ruleset
versions on which the ruleset version depends. If your ruleset version does not have any
prerequisite ruleset versions, you need to specify the base product ruleset Pega-
ProcessCommander as a prerequisite.
Ruleset best practices ✔Correct Answer-Only use RV for rulesets that are designed to be used
across multiple applications, such as organizational rulesets, to make them easily portable and
prevent the introduction of dependencies on a specific application.
Create applications for common rulesets; use the built-on functionality to include common
rulesets in the application.
Include unlocked AV rulesets in one application only. Doing so prevents AV rulesets from
referring to rules that may not exist in applications that do not contain the ruleset.
Run the Validation tool after implementation of critical changes or milestones (for example,
changes to the application ruleset list or built-on application as well as changes made before
lock/export).
ruleset list, sometimes referred to as the ruleset stack ✔Correct Answer-governs rule
execution at run time
Accessing ruleset list ✔Correct Answer-Operator > Profile.
personal ruleset ✔Correct Answer-if you are allowed to check out rules and has the name of
the operator ID and contains the rules checked out by the operator.
The ruleset list for the application with built-on applications can be viewed on the ruleset list
landing page ✔Correct Answer-(Dev Studio > Configure > Application > Structure > RuleSet
Stack).
, Ruleset locking ✔Correct Answer-You can lock a ruleset to prevent changes using the Lock and
Save button. Typically, you lock rulesets when development has reached a specific state, and the
application is ready to be promoted to testing. You cannot add or update rules in a locked
ruleset.
Rule checkout and check-in ✔Correct Answer-A team typically develops applications. Multiple
team members may check out rules to work on the same application in a coordinated manner.
The checkout feature ensures that different team members are not editing one rule at the same
time.
The system enforces the use of checkout and check-in operations when a ruleset has the
checkout facility enabled. Before you can change that rule, you must perform either the
standard checkout or private checkout operation.
Configuring ability to check out rules ✔Correct Answer-When you check out a rule, you are
creating a private copy of the rule that you can modify and test.
On the Security tab on the ruleset, select Use check-out? to enable checkout. On the Operator
record Security tab, operators need to have the Allow Rule Check out selected in order to
update rules in rulesets that require checkout. If a rule is not available for checkout, it is already
checked out by someone else, or it is in a locked ruleset version.
Check in a rule ✔Correct Answer-When a rule is checked in, the checked-in rule replaces the
original base rule. Add a comment describing the changes to the rule. You can view the check-in
comments on the rule History tab.
Use the bulk action feature to check in, open, or delete several checked out rules at the same
time. The bulk action feature is located in the Private Explorer menu or under the check mark
icon in the header.
Parallel development ✔Correct Answer-When multiple teams are working in the same
application rulesets, coordinating changes across teams is a challenge. When development
teams configure an application in parallel, rule changes might result in conflicts. Resolving
conflicts disrupts the overall project and may delay time to delivery.
Branch ✔Correct Answer-is a container for rulesets with records that are undergoing rapid
change and development. In Pega, you create a branch for each team. These branches allow
each team to create and update rules without impacting other teams.
Branch rulesets ✔Correct Answer-The rulesets associated with a branch. Is based on
(branched from) another ruleset
Contains rules that are in active development in the associated branch
To develop rules in parallel using branched rulesets, each team follows these steps: ✔Correct
Answer-1. Creates a team application built on the main application
2. Creates one or more development branches in the team application
3. Grants access to the team application
