Free Practice Questions for Pegasystems PEGACPSSA23V1 Exam

The compliance score of an application is generated based on several factors, including the number of rules with warnings, the number of rules with unjustified warnings, and the percentage of compliant rules in the application. This score helps to identify potential issues with rule compliance and areas that may need attention. References: Pega Platform Help - Compliance score.

Rule resolution will choose the rule that is most specific to the circumstances of the case. Since the country is set to Japan, the rule resolution algorithm will choose the rule version that is circumstanced for Japan. Among the options, 01-01-02 is the circumstanced rule that matches the country condition of Japan and would be selected over the base rule and any other versions. References: Pega Platform Help - Rule Resolution.

At 4.5 hours after the case reaches the assignment, the SLA would have passed the goal and deadline, and entered the passed deadline period. The initial urgency is 15, the goal adds 10 (total 25), and the deadline adds 15 (total 40). After the passed deadline, the urgency increases by 10 every hour up to a limit of 10 events. By 4.5 hours, there would have been two passed deadline events, adding 20 to the urgency, leading to a total urgency of 60. References: Pega Platform Help - Service Level Agreements.

The major skim operation copies rules from the highest minor version of the current major version of a ruleset to create a new major version. In this scenario, the ruleset being skimmed is ABC:02-02-01, indicating that the current major version is 02.

Given this, the ruleset versions that would be used by the skim operation to copy rules into ABC:03-01-01 would be the highest minor versions within the major version 02.

02-01-01: This is not the highest minor version (since we have 02-02-01), so it would not be used. The answer should be "No."

01-02-01: This is from a different major version (01), so it would not be used. The answer should be "No."

02-01-05: Despite having a higher patch version, it belongs to the minor version 01 within the major version 02. Since we have a higher minor version 02, this would not be used. The answer should be "No."

Only the highest minor version from the current major version (in this case, 02-02-01) is used for the skim operation to create the new major version ABC:03-01-01. If the ruleset version 02-02-01 were listed, the correct answer would be "Yes" for that version, but as it is not listed, none of the provided ruleset versions would be used in this skim operation.

B: Mashup requests are checked for the corresponding mashup channel ID parameter to ensure that the request is coming from a trusted source and is intended for the Pega application.

D: A user can view their worklist in an external portal and select items on which to take action, which is one of the key features of the Pega Web Mashup as it extends Pega's capabilities to external web pages. References: Pega official documentation on Pega Web Mashup capabilities.

In attribute-based access control (ABAC), an attribute can be a property (such as an age or status), a Boolean value (indicating true or false conditions), or a single string (such as a name or identifier). These attributes are evaluated to determine access rights within the application. References: Pega Platform Help - ABAC.

To ensure that patients can read but not edit cases in the hospital's ER case management system, two steps need to be taken. First, configure an Access Role to Object rule with the open case action set to 1 (B), which grants read-only access. This ensures that patients can view their cases without the ability to make any modifications. Secondly, create an access group unique to patients (D). This access group would include the Access Role to Object rule configured in the previous step. By associating patients with this access group, it ensures that they are granted the appropriate level of access to their cases, fulfilling the security requirements specified by the stakeholders.References: Pega Community documentation on Access of Role to Object and access groups.

The correct configuration for two parallel cases that run independently is the Subprocess shape with the Spinoff flow option enabled (Option C). This allows the Retirement planning case to proceed in parallel without waiting for, or reporting to, the Account review case. References: Pega official documentation on case design and flow shapes.

Creating a new ruleset version for each team ensures that each team's work is isolated within a specific version, preventing overlap and conflict. Setting up a branch ruleset for each team further isolates development work, allowing parallel development streams that can later be merged back into the main application ruleset. These two options, when used together, provide the most flexibility for teams working on separate enhancements with uncertain release dates. References: Pega Platform Help - Branch Rulesets.

To ensure that multiple teams can update the same application version without affecting each other's work, the following actions are recommended:

B: Create branches for each team's application. This allows teams to work on isolated versions of the application and merge their changes when ready.

D: Create a new application for each team built on the base application. This creates separate instances of the application for each team to work on, which they can then synchronize with the base application as needed. References: Pega official documentation on branch rulesets and application development.