• A: Configuring a data transform to apply the Open-Review status on the appropriate assignments can be used to change the status of a case when it is assigned to a user for review.
• D: Apply the Open-Review status to the appropriate assignments directly within the flow where the assignment is configured. References: Pega official documentation on case statuses and data transforms.

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.

To start operations at a specific GMT time regardless of where the server is located, you would use the Queue-For-Processing method in an activity. This method adds a task to a queue to be processed either by a standard or a dedicated queue processor. A dedicated queue processor can be configured to operate on a schedule, so it can start processing at midnight GMT. References: Pega SSA course materials on queue processors and timed events.

Graphical user interface, application Description automatically generated

Keyed data pages can return multiple embedded pages if the data structure includes lists or other page structures. They can also have multiple keys, which allows them to return data based on a combination of key values. References: Pega Platform Help - Data Pages.

No

YES

YES

NO

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.

Graphical user interface, application Description automatically generated

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.

• A: Configuring a process with a decision shape that continues if the TestThreshold Configuration setting is less than the applicant's test score supports the requirement for automatic case advancement based on standardized test scores.
• B: Configuring a TestThreshold Configuration setting with the national average for the test score threshold allows for the necessary comparison to determine if a case should advance automatically. References: Pega official documentation on decision shapes and configuration settings.

In Access Control Policies, attributes like Appointment date (A) and Number of dependents (B) can be used to define conditions for data access. These attributes can be part of case data or user profiles and serve as criteria for determining access levels. For example, an access control policy can restrict access to certain case information based on the appointment date or allow access to specific functionalities based on the number of dependents associated with a user profile.References: Pega Community documentation on Access Control Policies.

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. References: Pega SSA course materials on activity best practices.

An association rule differs from a class join in that it is a reusable rule that can be used by anyone with appropriate permissions when creating reports. This makes it available across multiple reports. Class joins, on the other hand, are specific to each report definition and are not reusable in the same way. References: Pega Reporting Guide - Associations vs. Joins.

• Inbound request received
• Map inbound data
• Request processing
• Map outbound data
• System returns a response

This sequence represents the typical flow of processing an inbound service request, from the initial receipt of the request to the final response after the necessary processing and mapping have been completed.

Graphical user interface Description automatically generated

To match the security solutions to their appropriate use cases:

• "Access of Role to Object" is typically used to specify what actions a particular role can perform on instances of a class. It would be appropriate for a use case where "Dealers can modify evaluations" since this is an action that a specific role (dealers) would be allowed to perform.
• "Access Control Policy" allows defining rules that enforce property and case access restrictions based on the user role and other conditions. It would be appropriate for a use case where "Customers can only view their own credit report" since this would be a restriction based on user-specific data.
• "Access Deny" is used to explicitly deny access to a rule or data instance. It fits the use case where "Dealers cannot run reports" because it is a restriction that prevents a specific action (running reports) for a specific role (dealers).
• "Access when" is a rule that defines conditions for whether certain access is allowed. It would be used in the scenario where "Dealers cannot modify orders in the Fulfillment stage" since this is a conditional restriction based on the stage of the process.

Based on these explanations, here is the matched list:

• Access when -> Dealers cannot modify orders in the Fulfillment stage.
• Access Control Policy -> Customers can only view their own credit report.
• Access Deny -> Dealers cannot run reports.
• Access of Role to Object -> Dealers can modify evaluations.

• B: When adding a Split For Each shape to your case life cycle, you need to define when the parent process resumes processing. This can be after each iteration or after all iterations complete.
• C: You also need to specify the Page List or Page Group property that the split will iterate over. This determines the scope of the subprocesses that are to be created. References: Pega official documentation on case life cycle design.

Pega Mobile Client supports leveraging various mobile device features to enhance app functionality and user experience. Barcode scanning (A) is commonly used in logistics and retail applications for quick identification and tracking of items. Biometric identification (C), such as fingerprint or facial recognition, adds an extra layer of security for user authentication. Push notifications (D) are crucial for real-time communication, alerting users to updates or required actions within the app, even when the app is not actively in use.References: Pega Community documentation on Pega Mobile Client capabilities.

To satisfy the report requirements, you can configure a class join on the Fulfillment report definition to join the operator information to each case. Alternatively, you can use an association rule to achieve the same effect. Both these options allow for the relevant operator information to be displayed alongside the shipping information in the report. References: Pega Reporting Guide - Joining Data.

• 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 prevent horizontal scrolling on mobile devices, setting the importance of columns allows for the most critical information to be shown first, potentially hiding less important columns on smaller screens. Using percentage widths for layouts ensures that the layout adapts to the screen width, which can also help prevent horizontal scrolling. References: Pega UI design best practices for mobile devices.