CPSA Application Rules and Rulesets 2

Question 1

What is the correct format for a Pega ruleset version number?

Accepted Answer

Major.Minor.Patch (e.g., 01-01-01)

Answer

Year.Month.Day (e.g., 2024.01.15)

Answer

Major.Minor only (e.g., 01-01)

Answer

Sequential integer (e.g., 1, 2, 3)

Question 2

When is a Pega ruleset considered 'locked'?

Accepted Answer

When it is marked as production-ready and no further rule changes are allowed in that version

Answer

When the application is deployed to a production environment automatically

Answer

When an administrator explicitly restricts the ruleset to read-only via security settings

Answer

When the ruleset patch version reaches its maximum numeric value

Question 3

Which ruleset version segment in Pega indicates a major functional change?

Accepted Answer

The first segment (e.g., changing from 01-xx-xx to 02-xx-xx)

Answer

The second segment (e.g., changing from xx-01-xx to xx-02-xx)

Answer

The third segment (e.g., changing from xx-xx-01 to xx-xx-02)

Answer

All three segments equally represent the same level of change

Question 4

What must you do when you need to modify a rule in a locked Pega ruleset?

Accepted Answer

Create a new (higher) ruleset version and make changes in that new version

Answer

Temporarily unlock the ruleset, edit the rule, then re-lock it

Answer

Copy the rule to a completely different ruleset and edit it there

Answer

Request an administrator to override the lock for a single rule

Question 5

What does the patch (third) segment of a Pega ruleset version typically represent?

Accepted Answer

Bug fixes and minor corrections within an existing major.minor release

Answer

New feature additions that extend application functionality

Answer

Compatibility updates for new Pega Platform versions

Answer

Security patches applied automatically by the Pega system

Question 6

Which of the following best describes a 'private edition' ruleset in Pega?

Accepted Answer

A ruleset with access restricted to a single named operator

Answer

A ruleset containing application-specific rules that overlay or extend a base/built-on application

Answer

A ruleset used only in sandboxed development environments and never promoted

Answer

A ruleset that is hidden from the ruleset stack and used only for unit testing

Question 7

What is the effect of selecting the 'Locked' checkbox on a Pega ruleset record?

Accepted Answer

It freezes the ruleset version as read-only, preventing new rules from being added or existing rules from being edited

Answer

It restricts the ruleset from being exported to other Pega environments

Answer

It removes the ruleset from the application's ruleset stack during deployment

Answer

It requires a four-eyes approval before any rule in the ruleset can be executed