Pass the Pegasystems Certified Pega Lead System Architect (CPLSA) Exam 8.8 PEGACPLSA88V1 Questions and answers with ValidTests

 Standard Agent Behavior: A standard agent in Pega with auto queue management enabled will manage its own queue and handle retries automatically.

 Retry Mechanism: If a task fails, the agent sets the task status to "broken-process" and retries the task according to the specified retry settings.

 One Retry: Since the agent is set to retry once, it will automatically attempt to reprocess the task one more time before taking further action.

References:

Pega Academy: Managing Agents and Queues

Pega Documentation: Standard Agents and Queue Management

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

Wait Shape with Case Dependency:

The best practice in Pega for handling dependencies between cases is to use a Wait shape configured with case dependencies. This ensures that the mortgage case waits for the completion of the credit report case before proceeding.

By configuring the Wait shape to monitor the status of the credit report case, it ensures that the mortgage case automatically resumes once the credit report case is resolved.

Process Configuration:

In the mortgage case process, insert a Wait shape where the process needs to pause for the credit report.

Configure the Wait shape to depend on the resolution of the credit report case. This can be done by specifying the case ID of the credit report as a dependency.

Automation and Efficiency:

This method is efficient as it automates the waiting process without manual intervention. The mortgage case resumes automatically once the credit report case completes, ensuring smooth workflow automation.

It avoids the need for complex SLAs or additional activities to check the status of the credit report case, simplifying the process design.

Routing to Specialist:

Once the Wait shape condition is satisfied, the process flow continues to the step that routes the mortgage case to a specialist.

This ensures that the mortgage case is routed at the appropriate time, maintaining process integrity and efficiency.

To expose a set of services for your application, with each service exposed as a separate WSDL:

Create a separate service package for each WSDL (Answer A):

Explanation: Service packages in Pega allow you to group related services and generate WSDL files for them. By creating a separate service package for each WSDL, you can manage and expose each service independently.

 Responsive Layouts:

Using responsive layouts helps ensure that the application aligns well with different device screen sizes, enhancing accessibility for all users.

 Link Controls:

Using link controls instead of buttons can improve readability and accessibility, making it easier for screen readers and other assistive technologies to interpret the interface.

 References:

Pega best practices for designing accessible applications emphasize the use of responsive designs and appropriate controls to ensure accessibility.

 Therefore, the correct answers are:

B. Use responsive layouts to help align with device screen size.

C. Use link controls instead of buttons, for readability.

Create Decision Table:

Go to Records Explorer > Decision > Decision Table.

Create a new decision table that evaluates LDAP attributes (role and application properties) and maps them to access groups.

Authentication Mapping Configuration:

Go to Designer Studio > Security > Authentication Service.

In the mapping tab, configure the authentication service to evaluate the decision table created.

Testing:

Test the configuration by logging in with different users and verifying that the correct access group is assigned based on the LDAP attributes.

References:

Pega Academy: Authentication and Access Control.

Pega Documentation: Decision Table and LDAP Integration.

Scenario testing in Pega is used to create UI-based, end-to-end tests for applications. The following statements are true about scenario testing:

Scenario Tests Can Include Another Scenario Test (A):

Scenario tests can be nested, allowing one scenario test to include another. This enables the reuse of common test steps and enhances the modularity of test cases.

Scenario Tests Do Not Support File Uploads or Downloads (C):

Scenario tests are designed to simulate user interactions but do not support file uploads or downloads as part of the test execution. This limitation ensures tests focus on UI interactions and business logic.

Scenario Tests Support the Setup or Cleanup of Test Data (E):

Scenario tests allow for the setup or cleanup of test data before or after the test execution. This capability ensures that the test environment is correctly prepared and that any test data is appropriately managed.

References:

Pega Scenario Testing Guide

Pega Platform Test Automation Documentation

Pega Customer Service functions as the customer interaction system of record within the enterprise architecture. It manages customer interactions and provides a comprehensive view of customer information and history, facilitating efficient and effective customer service.

References:

Pega Customer Service: Customer Interaction Management

Pega System of Record: Defining System of Record

For processing weekly CSV files of customer insurance quotes and creating policy cases:

File Listener and Job Scheduler (D):

Use a file listener to read the incoming CSV file and feed the data into a data type.

Configure a job scheduler to read the records from the data type and create cases. This approach decouples the file reading and case creation processes, allowing for better control and error handling.

References:

Pega File Listener Configuration Guide

Pega Job Scheduler Documentation