Pass the Pegasystems Certified Lead System Architect (CLSA) PEGACPLSA88V1 Questions and answers with ExamsMirror

 Page List vs. Page Group: In Pega, a Page List is an ordered collection of pages indexed by position (e.g., 1, 2, 3). A Page Group, on the other hand, is an unordered collection of pages indexed by a string value (e.g., "CompanyA", "CompanyB").

 Sorting Requirement: Since the requirement specifies that the list must be sorted by company stock ticker, a Page List is more appropriate because it allows for sorting and ordered iteration.

 Implementation: Use a Data Transform or an activity to populate and sort the Page List. You can use Pega's built-in sorting functions to order the list by the stock ticker.

References:

Pega Academy: Data Management with Page Lists and Page Groups

Pega Documentation: Working with Collections

 Ensuring Quality with Automated Testing:

Automated testing programmatically ensures the quality of rules, maintaining the integrity of the CI/CD pipeline. This is crucial for consistent and reliable deployments.

 References:

Pega Lead System Architect documentation emphasizes the importance of automated testing in CI/CD models to ensure rule quality and pipeline integrity.

 Therefore, the correct answer is:

B. Automated testing programmatically ensures quality of rules to maintain the integrity of the pipeline.

When deciding between a wait shape and an assignment with an SLA, consider the following requirements where a wait shape is simpler:

Adjust the Case Urgency: The wait shape allows you to adjust the urgency of a case when the wait condition is defined, which is simpler than configuring an SLA.

Manual Override: The wait shape provides an option to manually step past the waiting point if necessary, making it more flexible for certain scenarios.

References:

Wait Shape

Service Level Agreements

For validating the BenefitType property value, the recommended approach is:

When Rule and Relevant Record (D):

A System Architect creates a When rule in Dev Studio, referencing the ClaimBenefit Clipboard page on the Pages & Classes tab.

The rule is marked as a relevant record, making it available for Citizen Developers to use. This approach ensures that the validation logic is centrally defined and easily accessible for reuse.

References:

Pega Dev Studio Documentation on Creating When Rules

Pega Documentation on Marking Rules as Relevant Records

Custom Split-for-Each Process Step:

In the case designer, add a new step in the Processing stage where you need to create child cases.

Select the "More" option and then "Split for Each".

Configure the split to create a separate child case for each item in the page list property.

Configure Data Propagation:

Ensure that data from the parent case is propagated to each child case.

In the case designer, go to the data propagation settings and map the relevant properties from the parent case to the child cases.

Use Page List Property:

Create a page list property in the parent case to store the list of suspected fraudulent charges.

Configure the case type to iterate over this page list property when creating child cases.

References:

Pega Academy: Implementing Case Management.

Pega Documentation: Split-For-Each and Data Propagation.

Important points to follow while designing enterprise applications include:

Modular Architecture (A):

Implementing a modular architecture allows different parts of the application to be developed, maintained, and scaled independently. This minimizes the impact of changes, making the system more resilient and easier to manage.

Communication Channels (B):

Focusing on required communication channels ensures that the application meets the needs of its users, enhancing user productivity and satisfaction. This involves integrating the necessary communication tools and channels directly into the application workflow.

References:

Pega Best Practices for Application Design

Enterprise Architecture Principles

 The Adaptive Model decision component automatically computes a property called Propensity.

 Propensity is the likelihood or probability that a particular action will result in the desired outcome.

 This property is used to rank and prioritize decisions based on predicted customer behavior.

To avoid creating unnecessary case-level properties and views in Pega Express:

Define case type views using "* page, property" syntax for the majority of the fields (Answer A):

Explanation: Using this syntax allows you to reference existing data types and properties, reducing redundancy and the need for additional case-level properties.

 Job Scheduler:

Configuring a job scheduler to record monthly case status in a separate table ensures that the data is consistently updated and available for reporting.

 References:

Pega best practices for reporting strategies recommend using job schedulers to handle periodic data collection and reporting tasks.

 Therefore, the correct answer is:

A. Configure a job scheduler to record monthly case status in a separate table and report on that table.

Configure Temporary Case:

Set the case type to be instantiated as a temporary case in the starting flow. This ensures that the case is not persisted unless necessary.

Conditional Persistence:

Apply a when condition to determine whether the case should be persisted based on the comparison results. Only cases that require updates are persisted.

References:

Pega Academy: Case Type Design and Management.

Pega Documentation: Temporary Case Configuration.