PEGACPSSA23V1 Exam Dumps : Certified Pega Senior System Architect 23 Exam

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.

When configuring Pega Web Mashup, it's essential to create one DIV element in the hosting web page for each Pega gadget (A), ensuring that each gadget is properly isolated and rendered within its designated area on the web page. Additionally, adding a list of trusted domains in your application settings (B) is crucial for security, as it specifies which domains are authorized to host the mashup, preventing unauthorized use or embedding of the Pega functionalities in untrusted environments.References: Pega Community documentation on Pega Web Mashup configuration and security best practices.

The assignment urgency 6.5 hours after the case reaches the assignment with the given SLA configuration would be 95 (B). Here's the calculation: The initial urgency is 20. The case reaches the goal after 5 hours, adding 10 to the urgency, making it 30. Since the deadline is at 2 hours and has been exceeded by 4.5 hours, the urgency increases by 25, making it 55. Now, with the passed deadline events occurring every hour and increasing urgency by 5, after 1.5 hours, this would occur 1 additional time (since it's half an hour into the next hour), adding 5 to the urgency. Therefore, the total urgency after 6.5 hours is 20 (initial) + 10 (goal) + 25 (deadline) + 5 (passed deadline event) = 60. However, since the deadline urgency increase occurs at the 2-hour mark, the urgency would be 20 + 25 = 45 at 2 hours, and then after reaching the goal at 5 hours, additional 10 is added, making it 55, and then one passed deadline event adds 5 more, making the total 60. Since the deadline urgency is already accounted for at the 2-hour mark, it should not be added again after the goal. Therefore, the correct total urgency would be 20 (initial) + 10 (goal) + 25 (deadline) + 40 (8 passed deadline events) = 95.References: Pega Community documentation on SLAs and urgency calculation.