PEGACPSSA23V1 Exam Dumps : Certified Pega Senior System Architect 23 Exam

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.References: Pega Community documentation on Pega API and Service wizard.

• A: When using a Pega Web Mashup, leveraging the standard authentication service IACAuthentication and updating the authentication activities to match the external system's requirements is a common practice.
• D: Configuring application permissions by specifying a list of trusted domains in the application rule is important for security purposes and to control which external domains are allowed to embed the mashup. References: Pega official documentation on Pega Web Mashup configuration.

To create a class join in a report definition, you must select the type of match for key values (A) and create a prefix for the joined class (C). Selecting the type of match, such as Inner Join or Left Outer Join, determines how records from the primary class and the joined class are combined based on matching key values. Creating a prefix for the joined class helps in distinguishing properties from the joined class from those of the primary class, preventing naming conflicts and clarifying the report definition. These actions are fundamental steps in setting up class joins in report definitions to retrieve and display data from multiple related classes.References: Pega Community documentation on report definition and class joins.