PEGACPSA23V1 Exam Dumps : Certified Pega System Architect

• Major version: In Pega, a major version update is typically used when there are significant changes to the application, such as the introduction of new functionalities, case types, or major changes to existing functionalities. Adding a new "Order return" case type to the Shopping application constitutes a significant enhancement, thus it would usually require incrementing the major version of the ruleset.
• Minor version: Minor version updates are used for less significant changes that don't alter the application's primary functionality but still add enhancements or optional components to the existing structures. Adding a stage-specific optional action to an "Order placement" case lifecycle would be a good candidate for a minor version update because it extends the functionality without fundamental changes.
• Patch version: Patch versions are often used for bug fixes or minor improvements that do not add new functionalities but rather correct issues with existing ones. Fixing a bug that lists product options by product ID instead of by name is a classic example of a patch fix, as it corrects a specific issue without materially expanding or altering the functionality of the application.

References:

• Pega official documentation would typically include a section on ruleset versioning that describes the scenarios for using major, minor, and patch versions.
• Best practices as described in Pega Community articles and the Pega Academy training materials also discuss how to manage ruleset versions effectively in various development scenarios.

In a claims application where customers file home insurance claims and some claims may be investigated for fraud, it is efficient to create two separate case types: one for "Claim" and another for "Fraud Investigation." The Claim case type handles the standard process of filing and processing insurance claims, including the assessment of damages and coordination of payouts. The Fraud Investigation case type is used specifically to handle instances where claims might require additional scrutiny for potential fraudulent activity. This separation allows each case type to be optimized for its specific processes and requirements, enabling parallel processing and specialized handling where necessary.

Delegation is used in Pega to enable business users to manage specific business rules or parameters directly. It addresses:

B. A risk officer wants to adjust the income threshold for automobile loans. This requirement is ideal for delegation as it involves a business parameter (income threshold) that may need frequent adjustments based on market conditions or internal policies. Delegating this allows the risk officer to make adjustments independently without requiring changes through IT or development teams.