PEGACPSA23V1 Exam Dumps and Practice Questions

Service Level Agreements (SLAs) in Pega are used to define and enforce time limits for completing work and other time-based conditions:

B . A transaction review is completed within 24 hours. This is a direct application of SLAs, where a specific time frame (24 hours) is set as a target for completing a process step, such as a transaction review. SLAs ensure that such time-bound requirements are met, facilitating prompt and efficient service delivery.

To increase the font size on all field placeholder value components specifically to aid visually impaired users, applying global styling changes is the most effective approach. Among the options provided, adding a new theme text entry to the application theme allows for targeted styling adjustments to be applied broadly across the application.

C . Add a new theme text entry to the application theme: This approach allows for the customization of specific UI elements, such as field placeholder values, at the application level. By adding a new text entry with increased font size to the application theme, all instances of field placeholder values throughout the application will inherit this styling, ensuring a consistent and accessible user experience for visually impaired users.

Updating the existing Default theme text entry (A) could affect more elements than intended. Running a case type and changing the font on the view (B) only applies changes locally and lacks scalability. Uploading a new application theme (D) could be an option but is less direct and more complex than simply adding a new text entry specifically for placeholder values.

When configuring the 'Search duplicate cases' step in a Pega application, especially for IT ticketing systems, the primary aim is to identify multiple tickets raised for the same underlying issue. The most straightforward and effective criterion for identifying duplicates in this context is the issue type, such as 'the office Wi-Fi is down.'

B . Issue type is same: This option targets the core reason behind the creation of a ticket. Since multiple individuals can report the same issue from various departments or locations, filtering by the issue type ensures that all reports concerning a single problem (e.g., Wi-Fi outage) are identified as duplicates. This approach helps in consolidating the efforts to address and resolve the issue efficiently, avoiding redundant work.

Filtering by the name of the submitter, department, or office location (Options A, C, and D) might miss duplicates reported by different users or from different areas, making 'Issue type is same' the most logical and effective criterion for identifying duplicates in IT ticketing scenarios.

To enforce restrictions that an applicant must be older than 21 and have a monthly income of at least USD 2000 for an instant loan qualification, using a single Validate rule that includes both conditions is efficient. This method consolidates the validation logic into one rule, making the process streamlined and easier to manage and update, should the criteria change in the future.

The appropriate scope for a data page that lists products purchased by a customer viewed in an online portal is 'Requestor'. This scope ensures that the data page is unique to each user session and is accessible across multiple requests within that session. The 'Requestor' scope is suitable because it persists for the duration of the user's interaction with the application, across multiple threads or cases, making it ideal for situations where a user might be working on multiple support requests during a single login session.