Free Practice Questions for Pegasystems PEGACPDC25V1 Exam

Volume constraints allow you to limit the number of times an action is presented to customers across one or more channels. You can use volume constraints to implement a policy that restricts the number of emails sent per day. Outbound channel limits are used to limit the number of customers contacted per channel per run, not per day. Suppression rules are used to exclude customers from receiving an action based on certain conditions, such as opt-out preferences or recent purchases. Applicability rules are used to determine whether an action is relevant for a customer based on their profile or context, not based on the number of times the action is presented. Verified References: Certified Pega Decisioning Consultant | Pega Academy, Volume constraints

A screenshot of a computer AI-generated content may be incorrect.

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

The outbound run delivers 75 emails and 25 SMSes for the Standard card offer because the volume constraint is set to limit the number of actions per channel per day. The email channel has a limit of 75 actions per day, so all 75 email offers are delivered. The SMS channel has a limit of 25 actions per day, so only 25 SMS offers are delivered. The remaining 50 SMS offers are not delivered because they exceed the volume constraint.

To present offers from the two groups, you must map a real-time container to the Top-level or Issue-level. A real-time container is a configuration that defines how to deliver offers and treatments to a specific channel, such as a website or a mobile app. By mapping a real-time container to the Top-level or Issue-level, you can enable all the offers under that level to be available for delivery through that channel. Verified References: Pega Academy - Decisioning Consultant - Configuring real-time containers

Using the decision table, you can find the label for a customer with a credit score of 240 and an average balance of 35000 by following these steps:

Start from the top row and check if the customer’s credit score is less than 150. If yes, then the label is Very Poor. If no, then move to the next row.

Check if the customer’s credit score is less than 175 and their average balance is less than 25000. If yes, then the label is Poor. If no, then move to the next row.

Check if the customer’s credit score is less than 200 and their average balance is less than 50000. If yes, then the label is Fair. If no, then move to the next row.

Check if the customer’s credit score is less than 250 and their average balance is less than 75000. If yes, then the label is Good. If no, then move to the last row.

The last row applies to all other cases that do not match any of the previous conditions. The label for this row is Very Poor.

In this case, the customer’s credit score is not less than 150, so the first row does not apply. The customer’s credit score is less than 175, but their average balance is not less than 25000, so the second row does not apply either. The customer’s credit score is not less than 200, so the third row does not apply. The customer’s credit score is less than 250 and their average balance is less than 75000, so the fourth row applies. Therefore, the label for this customer is Poor.