PEGACPSA23V1 Exam Dumps : Certified Pega System Architect

Certain updates require the capabilities of Dev Studio because of their complexity and the need for custom configuration:

D. A new confirmation view displays a read-only text property. Creating and configuring new UI components, particularly those that involve specific behavior such as displaying read-only properties, typically necessitates using Dev Studio. This environment provides the necessary tools and features to design and implement detailed user interface requirements.

• 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.

An authority matrix in Pega is used to manage complex decision-making processes that depend on various levels of organizational authority:

C. Any overtime -> Manager of Supervisor. This condition involves hierarchical decision-making where approval authority escalates beyond the immediate supervisor, making it appropriate for an authority matrix to define and automate the approval paths based on the organizational structure.

D. Regular 40 hours -> Supervisor of Employee. Although this appears straightforward, using an authority matrix helps in organizations where different supervisors might have varying levels of authority based on departmental rules or other factors, thus standardizing the approval process across diverse units.