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

A rule defined in myco-data-shape-rectangle can modify the .Color property because .Color is defined in the parent class (myco-data-shape) and is inherited by its subclasses.

A rule existing in myco-data-shape can be overridden in myco-data-shape-circle, allowing for specific behavior in the subclass while maintaining the inheritance structure.

Enable CAPTCHA Security Policy:

Navigate to the security settings in Pega.

Enable CAPTCHA to prevent automated login attempts.

Authentication Lockout Policy:

Configure the authentication lockout policy to lock accounts after a certain number of failed attempts within a specified timeframe.

To define Authentication Service data instances in Pega, the following rule types are used:

Data pages: Used to retrieve and store authentication-related data.

Activities: Perform operations such as authentication logic and integration with external systems.

Data transforms: Used to map and transform authentication data.

References:

Defining Authentication Services in Pega

To ensure the host system origin is trusted in a Pega web mashup implementation:

In the authentication service JNDI binding parameters, specify the protocol, host, and port (Answer A):

Explanation: Specifying these parameters ensures that the Pega system recognizes and trusts the origin of the mashup requests.

Defining a case type within a case type-specific ruleset provides several advantages:

Branch Ruleset Association: By associating each branch ruleset with case-specific user stories, you can better manage development and testing. This allows for more targeted reviews and testing, ensuring that changes are isolated and easily traceable.

Component Application Conversion: If there is a possibility that the case type might be converted to a component application in the future, having a case-specific ruleset simplifies the process. It allows the case type to be more easily packaged and reused across different applications.

References: Pega Platform best practices for ruleset management and case type design.

 Separate Mobile Portal: Creating a separate portal for mobile users ensures that the specific needs of mobile interfaces can be addressed without affecting the desktop version. This separation allows for dedicated customization.

 Adjust Responsive Behavior: Fine-tuning the responsive behavior within the application skin ensures optimal viewing on mobile devices. Adjustments can include changing breakpoints, font sizes, and element visibility to enhance user experience on smaller screens.

 Non-impactful Changes: Both options focus on optimizing the mobile experience while keeping the desktop experience intact, adhering to Pega's principle of responsive and adaptive design.

 Reference: Pega recommends using responsive design techniques and, when necessary, separate portals for different device types to ensure a consistent user experience (Pega Platform 8.7 Documentation, User Interface - Skins).

 Queue Status "Available": When the queue status for an item is "Available," it indicates that the item is ready for processing but has not yet been picked up by the agent.

 Failed Processing: If the agent attempted to process an item but failed, it can be reflected in the status. The item remains in the queue, and the system logs may indicate the failure reason.

 Scheduled Processing: The status "Available" can also mean that the item is scheduled for future processing based on the agent's schedule.

References:

Pega Academy: System Queue Management

Pega Documentation: Understanding Agent Status and Queue Management

Several factors can contribute to delays in sending correspondence in a Pega application:

Queued SLA Objects: The number of Service Level Agreement (SLA) objects queued can affect the timing of correspondence. If there are many SLA objects queued, the system may take longer to process them, leading to delays.

Error Handling for Locked Items: If there are errors in handling locked items, this can also cause delays. When an item is locked and an error occurs, the system needs to manage these exceptions, which can impact the overall processing time.

References: Pega Platform documentation on SLA and error handling mechanisms.

Data Transform Configuration:

Create a data transform that copies the selected items to the page list property.

Post-Processing Action:

In the flow action, add the data transform as a post-processing action to ensure it executes after the form submission.

Testing:

Test the form submission to verify that the selected items are correctly copied to the page list property.

References:

Pega Academy: Data Transform and Flow Actions.

Pega Documentation: Configuring Post-Processing Actions.

Configure Activity for Background Execution:

Set the activity to execute in the background to prevent user interface delays.

Activity Setup:

Configure an activity that handles the connector call.

Declare Trigger:

Set up a declare trigger that activates when the case status changes to ensure the connector runs at the appropriate time.