Separate Application for Reusable Component:

Placing the component in a separate application ensures modularity and reusability.

Departments can integrate with this application as needed, ensuring consistency and reducing redundancy.

Benefits:

Centralized maintenance and updates.

Easier to manage and deploy across various departments.

Avoids embedding the component directly in multiple applications, which could lead to version control issues.

References:

Pega Best Practices Guide

Pega Academy Course on Reusable Components and Modular Design

These answers and explanations have been verified according to the Pega Lead System Architect guidelines and best practices.

Class Structure Flexibility: The class hierarchy allows for instances of Parking and Auto to be stored either together or separately, depending on the implementation requirements and table mapping configurations.

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.

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.

Use the Optimistic Locking Option : Optimistic locking ensures that updates are handled efficiently in a multimode system without causing contention.

Override DetermineLockString : Override the DetermineLockString to use .AccountID instead of .pyID as the lock string to ensure that the correct customer account is locked during updates. References:

Pega Locking Mechanisms: Locking Mechanisms

Pega Advanced Agent Configuration: Advanced Agent Configuration

 Senior Manager Role with Dependent Roles :

Creating a new Senior Manager role with Manager and Vice President as dependent roles ensures that the Senior Manager inherits access from both roles. Overriding the Access of Role to Object rules from the Vice President role as required provides the necessary fine-tuning.

 References :

Pega documentation on role-based access control recommends defining new roles with dependencies to inherit access rights and customize as needed.

 Therefore, the correct answer is:

D. Create a new Senior Manager role with Manager and Vice President as dependent roles, and override the Access of Role to Object rules from the Vice President role as required.

Graphical user interface, application Description automatically generated

There are two primary methods to queue an item for processing in Pega:

Queue-for-processing method: This method is used within an activity to queue items for background processing.

Run in Background smart shape: This smart shape is used in the process flow to queue items for background processing efficiently.

References:

Queue-for-processing method

Run in Background smart shape

Add Justification to ARO Instances:

When configuring ARO instances, ensure that you add justifications whenever a privilege is not visible from the ARO’s ruleset. This improves transparency and adherence to security guidelines.

Navigate to the security settings in Pega and update the ARO instances accordingly.

Change Security Type for Activities:

For activities used for simulations, change their security type from " Activity " to " Utility " . This aligns with best practices and reduces unnecessary warnings.

Update the security settings for these activities through the Pega Developer Studio.

Create a New Mapping Servlet:

Go to the servlet configuration section in Pega.

Define the New URL Pattern:

Create a unique URL pattern that will be mapped to the new LDAP authentication servlet.

Implement the Servlet Logic:

Ensure the new servlet contains the necessary logic for LDAP authentication.