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 case management within Pega, when processing a parent case (P-l) with two child cases (C-l and C-2), the typical configuration requires that both child cases be resolved before the parent case can be resolved. This ensures that all related activities and requirements in the child cases are completed before the overall process (represented by the parent case) is considered complete. This approach is crucial for maintaining the integrity of the case processing lifecycle and ensuring that all necessary tasks are completed before concluding the parent case.

For accommodating passengers traveling with service animals, efficiently capturing necessary information (type of animal, size, and medical information) is critical. This requirement is conditional, triggered only when a passenger declares travel with a service animal.

• A. Add a process to the case life cycle for service animal accommodation and apply a condition: This option allows for the integration of a dedicated process within the overall case life cycle specifically for gathering service animal information. The process is conditionally executed, based on whether the passenger has declared the need for service animal accommodation. This ensures that the additional information is requested only when relevant, keeping the case life cycle streamlined and focused.

Applying an optional action (B) offers flexibility but might not guarantee the collection of this information as part of the standard workflow. Configuring a separate stage (C) could unnecessarily segment the case life cycle, especially if service animal accommodation is a conditional step rather than a distinct phase. Creating a child case (D) for service animal accommodation could complicate case management, especially for a requirement that is inherently part of the main travel arrangement process rather than a standalone case.