PDF PEGACPLSA88V1 Study Guide

PegaUnit testing best practices include:

A test ruleset is placed at the top of an application's ruleset stack:

Ensuring the test ruleset is at the top makes sure that the latest test rules are executed first, which helps in isolating and testing changes effectively.

A test case groups relevant assertions together:

Grouping relevant assertions in a test case ensures that related conditions are checked together, providing a more comprehensive and organized test output.

A test case focuses on a single area of functionality:

Focusing on a single area of functionality per test case simplifies testing and debugging. It ensures that each test case is specific and clear in its purpose.

References:

Pega Documentation on PegaUnit Testing: PegaUnit Testing

Pega Documentation on Best Practices for Testing: Testing Best Practices

This comprehensive approach ensures that all the answers are verified and supported by references to Pega Lead System Architect documentation.

To troubleshoot a chronic performance issue in a cloud-based production application:

Review Performance Alerts and Exceptions in PDC (A): Pega Predictive Diagnostic Cloud (PDC) monitors and reports on the health and performance of Pega applications in real-time. Reviewing alerts and exceptions here can provide insights into the root causes of performance issues.

Review Performance Alerts and Exceptions in AES (D): Pega Autonomic Event Services (AES) also monitors system health and performance. It can help identify patterns and issues that occur during specific time frames.

References:

Pega PDC: Understanding Pega Predictive Diagnostic Cloud

Pega AES: Pega Autonomic Event Services Overview

To avoid creating unnecessary case-related properties and views:

Work Pool Level Definitions: Define most properties and sections at the work pool level to ensure they are reusable across multiple case types. This approach reduces redundancy and simplifies maintenance.

Data Types: Create data types that correspond to the case type when necessary. This helps in organizing related data and promotes reuse.

Data Reference Field Type: Use the data reference field type in the case type's data model tab. This allows you to link to existing data types without duplicating properties, maintaining data integrity and reducing redundancy.

References: Pega Platform documentation on data modeling, work pools, and data reference field types.

 Setting pxThread.isWebMashup:

In the pyDefault Data Transform for a case, setting pxThread.isWebMashup to True ensures that App Studio users see the same views displayed by a Mashup interface.

 Associated Privilege Visibility Conditions:

Using associated privilege visibility conditions allows App Studio users to view and configure sections only shown to external personas at design time.

 References:

Pega documentation on Mashup interface development in App Studio outlines these practices to ensure seamless integration and development.

 Therefore, the correct answers are:

B. In the pyDefault Data Transform for a case, set pxThread.isWebMashup to True by using an Application Setting. App Studio users then see the same views that are displayed by a Mashup interface when it is configured to use the Create a case option.

C. Use associated privilege visibility conditions. At design time, an App Studio user is able to view and configure sections that are only shown to external personas.