To avoid recalculating declarative properties when extracting data with BIX:

BIX Command Line Options :

The BIX extraction process can be configured to disable recalculating declarative properties by using specific command line options.

The options disableBackwardChaining and disableForwardChaining prevent the recalculation of declarative properties during the extraction.

Configuration :

Include these options in the BIX command line execution to ensure that declarative properties are not recalculated from their source properties during the extraction process.

References:

Pega Business Intelligence Exchange (BIX) User Guide

Pega Documentation on Declarative Rules

Robotic Desktop Automation (RDA) is recommended in this scenario because it enables Customer Service Representatives (CSRs) to launch and interact with multiple applications from a single interface. RDA automates repetitive tasks and integrates different systems without requiring backend changes, making it an ideal solution for environments where applications are built on diverse technologies. This approach improves efficiency by reducing the manual effort needed to synchronize data across systems, ensuring real-time updates and data consistency.

References:

Pega Robotics: Pega Robotics Overview

Pega Customer Service: Pega Customer Service Capabilities

To address complaints about irrelevant offers and products:

Pega Marketing (A) : This solution helps create targeted marketing campaigns and personalized offers, ensuring that customers receive relevant and timely promotions.

Customer Decision Hub (D) : This solution uses real-time analytics and decisioning to determine the best action or offer for each customer, ensuring relevance and improving customer satisfaction.

References:

Pega Marketing: Pega Marketing Overview

Customer Decision Hub: Pega Customer Decision Hub

To address the requirement where users working in one application need to create cases in another application, the recommended approach is to implement Federated Case Management (FCM).

Federated Case Management : FCM allows different Pega applications to share and manage cases across multiple systems. This approach enables seamless case creation and man agement, ensuring that users can interact with cases regardless of the application they are working in.

Synchronization and Communication : FCM facilitates synchronization and communication between different Pega instances, ensuring that case data is consistent and accessible across the applications.

References: Pega Platform documentation on Federated Case Management.

When deciding between a wait shape and an assignment with an SLA, consider the following requirements where a wait shape is simpler:

Adjust the Case Urgency: The wait shape allows you to adjust the urgency of a case when the wait condition is defined, which is simpler than configuring an SLA.

Manual Override: The wait shape provides an option to manually step past the waiting point if necessary, making it more flexible for certain scenarios.

References:

Wait Shape

Service Level Agreements

Advanced Mode Configuration:

Configure the agent to run in Advanced mode to gain more control over its execution.

Periodic Pattern:

Set the agent to run with a Periodic pattern, scheduling it to execute daily at midnight.

Ensure the agent checks for customer birthdays and sends out emails accordingly.

For Pega Web Mashup to follow the same-origin policy, both the web application page URL and the Pega gadget URL must have the same origin, which includes the same scheme (HTTP/HTTPS), host, and port.

Configuration A and Configuration B :

Web application page URL: https://www.pega.com/MyWebApp/home.html

PEGA Gadget URL: https://www.pega.com/MyWebApp/gadgetA.html

In both configurations A and B, the scheme (https), host (www.pega.com), and port (default HTTPS port 443) are the same, which adheres to the same-origin policy.

References:

Pega Web Mashup and Same-Origin Policy

To isolate database-related performance issues:

Investigate when the database is used most heavily (B) : Understanding peak usage times can help pinpoint when the database is under the most strain. This information is crucial for identifying potential bottlenecks and optimizing performance.

Lower query-time-related alert thresholds (C) : By lowering the alert thresholds for query times, you can capture more detailed information about slow-running queries, helping to identify and address inefficient database operations.

References:

Pega Performance: Database Performance and Tuning

Pega Alerts: Configuring Alerts and Thresholds

 Responsive Layouts :

Using responsive layouts helps ensure that the application aligns well with different device screen sizes, enhancing accessibility for all users.

 Link Controls :

Using link controls instead of buttons can improve readability and accessibility, making it easier for screen readers and other assistive technologies to interpret the interface.

 References :

Pega best practices for designing accessible applications emphasize the use of responsive designs and appropriate controls to ensure accessibility.

 Therefore, the correct answers are:

B. Use responsive layouts to help align with device screen size.

C. Use link controls instead of buttons, for readability.

Increase Weights of Conditions:

Adjust the weights of the conditions to make them more significant in the duplicate detection process. This can help in reducing false positives.

Adjust Threshold:

Increase the threshold for the weighted condition sum to ensure that only cases with a higher likelihood of being duplicates are flagged.

References:

Pega Academy: Duplicate Case Management.

Pega Documentation: Configuring Duplicate Detection Rules.