Application Rules and Rulesets Flashcards

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

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.

When is a Pega ruleset considered 'locked'?

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.

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

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.

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

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.

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

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.

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

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.

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

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.