Free Pegasystems PEGACPSA23V1 Practice Exam with Questions & Answers | Set: 8

Delegation is used in Pega to enable business users to manage specific business rules or parameters directly. It addresses:

B. A risk officer wants to adjust the income threshold for automobile loans. This requirement is ideal for delegation as it involves a business parameter (income threshold) that may need frequent adjustments based on market conditions or internal policies. Delegating this allows the risk officer to make adjustments independently without requiring changes through IT or development teams.

For a case type that facilitates booking the dining room for events, with additional steps required if the customer opts for catering, structuring the case flow to adapt to customer choices is essential.

• A. Create a check box for customers to indicate catering preference. Add a decision shape: This setup allows the case flow to branch based on whether catering is required. If the check box is selected, the flow can proceed to steps for selecting menu preferences and scheduling a menu tasting appointment; if not, it can move directly to providing a rental rate quote.
• B. Configure menu preferences and appointment date fields with a visibility condition: This ensures that these fields are only displayed when catering is chosen, maintaining a streamlined and relevant user experience. Visibility conditions based on the catering check box selection dynamically adjust the form to match customer requirements.

Creating parallel processes for menu selection and rental rate quoting (C) might imply simultaneous progression, which does not align with the conditional nature of these steps. Making the menu selection and tasting appointment process a case-wide optional action (D) could allow it to be bypassed, potentially conflicting with the specified requirement for catering requests.

In Pega Express, when creating a new child case, the "Create Case" shape in the case designer is used to configure the propagation of data from a parent case to a child case. This shape can be configured to copy specified properties to the new child case, ensuring that necessary data is automatically carried forward. This configuration is essential for maintaining data consistency and relevance across related cases, facilitating seamless case management and data integrity.

Decision tables in Pega are best used for scenarios where multiple conditions determine the outcome:

A. A dance studio recommends a membership type based on the number and type of dance classes the customer wants to attend every month. This situation is suitable for a decision table because it involves evaluating various combinations of conditions (number and type of classes) to determine a specific outcome (membership type).

C. If customers decide to add insurance, checked bags, or early boarding to their airline tickets, extra fees are added to their order total. This is another appropriate use for a decision table as it requires a straightforward assessment of conditions (additional services selected) to calculate added fees, making the process clear and manageable through a decision table

In Pega, when configuring data pages to source UI controls such as drop-down lists, it's crucial to select the configuration that optimally uses memory and efficiently serves the data to the users. For this scenario, the correct answer is Option F: List, ACME-Products-Data-Color, ReadOnly, Node.

• List vs. Page: Choosing 'List' is appropriate because the requirement is to populate a drop-down list with multiple entries (colors in this case). 'Page' would be used for single record data, which is not the case here.
• Object Type: 'ACME-Products-Data-Color' is chosen because the data represents a list of color options provided by the manufacturer, which is typically static reference data, fitting the 'Data' class layer rather than the 'Work' layer which is used for case management or the 'Work-ColorFeedback' which would be used for storing feedback or interactions specific to colors.
• Edit Mode: 'ReadOnly' is the correct mode since users are selecting a color from a pre-defined list and are not expected to edit these values directly.
• Scope: 'Node' is selected to minimize memory usage. By setting the scope to 'Node', the data page is loaded once per node (server instance) and shared across all requestors (users) on that node, which is memory efficient for data that doesn't change often and is applicable across all users, such as a list of colors.

This configuration ensures that the data page is loaded efficiently in a read-only list format at the node level, reducing the overall memory footprint while making the color selections available across the application.

For a data page set with a "Reload if Older Than" threshold of 15 minutes, it is essential to understand how this setting dictates the data page's reload timing in response to user requests for product information.

• D. 06:42: The data page is reloaded at 06:42 because this is the point at which the next user request for product information occurs outside the 15-minute validity window from the data page's last load at 06:12. The 06:20 request does not trigger a reload since it falls within the 15-minute window. By 06:42, the data page has surpassed the "Reload if Older Than" threshold relative to its initial load time, necessitating a reload to ensure the currency and accuracy of the product