Certified Lead System Architect (CLSA) PEGACPLSA88V1 Reddit Questions

Configure Authentication Activity:

Go to Records Explorer > Security > Activities.

Create or configure the authentication activity to map the authenticated user to the operator ID in Pega.

LDAP Attributes Mapping:

Go to Designer Studio > Security > Authentication Service.

Configure the LDAP attributes to map to Pega operator properties, ensuring that attributes like cn, sn, mail, etc., are correctly mapped.

Validation:

Test the Single Sign-On (SSO) setup to ensure the authentication and attribute mappings work correctly.

Verify that users can log in using SSO and their LDAP attributes are correctly reflected in Pega.

References:

Pega Academy: Single Sign-On Configuration.

Pega Documentation: LDAP and SSO Configuration.

 Column Importance: The importance setting helps define which columns are displayed on smaller screens. "Primary" ensures the column is always visible, "Secondary" is shown if there is enough space, and "Other" is hidden on smaller screens.

 Restaurant Name as Primary: Setting the restaurant name to primary ensures it is always visible, as it is crucial information for making a reservation.

 Image Column as Other: Setting the image column to "Other" hides it on small screens, which is acceptable as images are non-essential compared to textual information.

 Location and Reservation as Secondary: These columns are set to secondary, ensuring they are visible on medium to large screens but can be hidden on smaller screens if space is limited.

 Reference: Pega guidelines recommend using the importance settings to manage the visibility of columns in responsive layouts, ensuring critical information is prioritized (Pega Platform 8.7 Documentation, User Interface - Column Settings).

Ensuring that new team members adhere to best practices can be achieved through the following methods:

Branch Review: Utilize the branch review feature in Pega, where senior team members can review the contents of the branch. This allows experienced developers to provide feedback and ensure that the new rules meet the required standards.

Branch Quality Review: Regularly review the quality of the branch to identify any rules that have guardrail warnings. Guardrails are best practice guidelines in Pega, and addressing these warnings helps maintain high-quality, robust rules.

References: Pega Platform documentation on branch development and guardrail compliance.

To address performance issues and ensure optimal application performance, the following actions are recommended:

Dedicated a node to background processing (Answer A):

Explanation: By dedicating a node specifically for background processing tasks (such as agents and batch processes), you can reduce the load on nodes handling user interactions, thereby improving overall performance.