Pegasystems PEGAPCDC87V1 Exam Dumps

Understanding Refreshable Segment Option:

This option ensures that the segment is updated automatically whenever it is referenced.

Functionality:

When enabled, all segments that reference the refreshable segment are automatically updated, ensuring that the latest data is used.

Purpose:

This helps maintain data accuracy and relevance across all segments and ensures that the decisioning process is based on current data.

Verification from Pega Documentation:

Pega documentation on using and configuring refreshable segments in outbound schedules.

Context: The bank wants to suppress mortgage offers if a customer ignores three offers within a group for one month.

Suppression Rule: In Pega, suppression rules are defined to manage overexposure to customers.

Implementation: The suppression rule should be set at the group level to ensure the entire group of mortgage actions is suppressed for 30 days after three rejections.

Pega Configuration: The configuration for suppression rules supports this requirement by allowing the setting of a threshold for rejections across any channel, thus making option A the correct choice.

Referencing Customer Properties: In Pega decision strategies, customer properties are accessed by prefixing the property name with 'Customer.' This convention helps in clearly identifying the context of the properties being used.

Scorecard Component - This component in Pega CDH is designed to evaluate attributes and produce a score based on those attributes. It is commonly used for calculating credit scores, risk scores, etc.

Steps to Use Scorecard:

In the decision strategy, add a Scorecard component.

Configure the scorecard to include relevant customer attributes (e.g., payment history, credit utilization).

Set the rules and weights for each attribute to calculate the final credit score.

Use the score in further decision logic (e.g., filtering out customers with a score below 500).

Pega Customer Decision Hub User Guide 8.5, Section 'Using Scorecards in Decision Strategies' explains how to configure and use scorecards to calculate scores.

Requirement Analysis: U+ Bank wants to display a specific credit card offer (Standard Card) to every customer who logs in to the bank website using Pega Customer Decision Hub.

Identify Mandatory Artifacts: To implement this requirement in Pega Customer Decision Hub, certain artifacts are necessary:

Business Structure: This defines the business hierarchy in Pega CDH, such as issues and groups. For this scenario, a relevant business issue and group must be defined (e.g., Credit Cards -> Standard Card).

Action and Associated Web Treatment: The specific credit card offer (Standard Card) must be created as an action, and it must have an associated web treatment to display on the bank's website.

Real-time Containers: These containers facilitate real-time interactions by displaying the appropriate offers to customers when they log in to the website.

Not Mandatory Artifacts:

Customer Contact Policies: These policies are used to limit the number of interactions with customers over a period. However, they are not mandatory for simply displaying an offer upon login.

Customer Engagement Policies: While important for determining eligibility, applicability, and suitability of offers, they are not specifically mandatory for the basic requirement of displaying an offer upon login.

Conclusion: The three mandatory artifacts to implement the requirement are a business structure, an action and the associated web treatment, and real-time containers.