Most Recent Pegasystems PEGACPSSA23V1 Exam Questions & Answers

In a Pega Web Mashup, valid ways to exchange data include using an action object configured as a script to perform additional actions on a web mashup gadget (A), utilizing the Javascript function doAction() to set or read data values through the hosting web page (B), and using the data-pega-event-onpagedata attribute to configure default values for the gadget (E). These methods facilitate dynamic interaction between the mashup and the hosting web page, allowing for seamless data exchange and integration of Pega functionalities into external web applications. Reference: Pega Community documentation on Pega Web Mashup and integration techniques.

To resolve performance issues caused by resource-intensive queue processors, it's essential to ensure that these processors are associated with appropriate node types (A) and that application nodes are configured with node types (D). Associating queue processors with specific node types allows for the distribution of workload across the application infrastructure, optimizing resource utilization and improving performance. Configuring application nodes with node types ensures that tasks are executed on the most suitable nodes, further enhancing system efficiency and scalability. Reference: Pega Community documentation on queue processors and node types.

The two most common ways to expose your application to an external system are to leverage the Pega API (B) and to create a web service with the Service wizard (D). The Pega API provides a set of out-of-the-box RESTful endpoints for performing operations within the Pega Platform. The Service wizard simplifies the creation of SOAP or REST services, enabling external systems to interact with Pega applications. Reference: Pega Community documentation on Pega API and Service wizard.

The difference between using the Call and Branch methods in an activity step to invoke other activities is that Call will return to the originating activity once the called activity completes, while Branch will not return to the originating activity and will skip the remainder of it after the called activity completes. Reference: Pega official documentation on activity methods.

Pega best practices recommend keeping activities short to enhance maintainability and readability. Custom Java steps should be limited to reduce complexity and potential errors. Activities should also be limited in general, with preference given to other rule types that are more declarative and less procedural, like data transforms, to improve application performance and maintainability. Reference: Pega SSA course materials on activity best practices.