CPSA Application Rules and Rulesets 2 — Questions and Answers
Question 1: What is the correct format for a Pega ruleset version number?
- Major.Minor.Patch (e.g., 01-01-01) (Correct answer)
- Year.Month.Day (e.g., 2024.01.15)
- Major.Minor only (e.g., 01-01)
- Sequential integer (e.g., 1, 2, 3)
Correct answer: Major.Minor.Patch (e.g., 01-01-01)
Pega ruleset versions follow a three-part Major.Minor.Patch format such as 01-01-01.
Question 2: When is a Pega ruleset considered 'locked'?
- When it is marked as production-ready and no further rule changes are allowed in that version (Correct answer)
- When the application is deployed to a production environment automatically
- When an administrator explicitly restricts the ruleset to read-only via security settings
- When the ruleset patch version reaches its maximum numeric value
Correct answer: When it is marked as production-ready and no further rule changes are allowed in that version
A locked ruleset is finalized as production-ready, preventing any modifications to rules within that version.
Question 3: Which ruleset version segment in Pega indicates a major functional change?
- The first segment (e.g., changing from 01-xx-xx to 02-xx-xx) (Correct answer)
- The second segment (e.g., changing from xx-01-xx to xx-02-xx)
- The third segment (e.g., changing from xx-xx-01 to xx-xx-02)
- All three segments equally represent the same level of change
Correct answer: The first segment (e.g., changing from 01-xx-xx to 02-xx-xx)
Incrementing the first (major) segment signals a significant functional change or a new major application version.
Question 4: What must you do when you need to modify a rule in a locked Pega ruleset?
- Create a new (higher) ruleset version and make changes in that new version (Correct answer)
- Temporarily unlock the ruleset, edit the rule, then re-lock it
- Copy the rule to a completely different ruleset and edit it there
- Request an administrator to override the lock for a single rule
Correct answer: Create a new (higher) ruleset version and make changes in that new version
When a ruleset is locked, you must increment to a new ruleset version to make any modifications.
Question 5: What does the patch (third) segment of a Pega ruleset version typically represent?
- Bug fixes and minor corrections within an existing major.minor release (Correct answer)
- New feature additions that extend application functionality
- Compatibility updates for new Pega Platform versions
- Security patches applied automatically by the Pega system
Correct answer: Bug fixes and minor corrections within an existing major.minor release
The patch segment represents minor fixes or corrections within a given major.minor version.
Question 6: Which of the following best describes a 'private edition' ruleset in Pega?
- A ruleset containing application-specific rules that overlay or extend a base/built-on application
- A ruleset with access restricted to a single named operator (Correct answer)
- A ruleset used only in sandboxed development environments and never promoted
- A ruleset that is hidden from the ruleset stack and used only for unit testing
Correct answer: A ruleset with access restricted to a single named operator
A private edition ruleset holds implementation-specific overrides that specialize a shared framework or base application.
Question 7: What is the effect of selecting the 'Locked' checkbox on a Pega ruleset record?
- It freezes the ruleset version as read-only, preventing new rules from being added or existing rules from being edited (Correct answer)
- It restricts the ruleset from being exported to other Pega environments
- It removes the ruleset from the application's ruleset stack during deployment
- It requires a four-eyes approval before any rule in the ruleset can be executed
Correct answer: It freezes the ruleset version as read-only, preventing new rules from being added or existing rules from being edited
The Locked checkbox makes the ruleset version immutable, ensuring no rule modifications can occur in that version.
CPSA Application Rules and Rulesets 2
What is the correct format for a Pega ruleset version number?