PEGA CSSA Mock Test3

The correct answer is "Report, Receive, Resolve, Respond, Route, Research". These six R's represent a process or sequence of actions that need to be followed. First, a report is made to bring attention to an issue or problem. Then, the report is received by the appropriate person or department. Next, the issue is resolved or addressed. A response is then provided to the person who made the report. If necessary, the report is routed or directed to the relevant individuals or departments. Finally, research may be conducted to gather additional information or investigate the issue further.

In PRPC, push routing refers to the process of assigning work to a specific worklist or operator, pushing the work to them. Assigning work to a worklist is an example of push routing because the work is being assigned to a specific location. On the other hand, pull routing involves using a "get next work" function to grab work items from a workbasket, allowing operators to pull the work towards themselves. Using "get next work" to grab work items from a workbasket is an example of pull routing as the operator is pulling the work towards themselves.

The correct answer includes "Rule-Declare-Expression" and "Rule-Declare-Onchange" as the declarative rules. These rules are used to define expressions and handle changes in the system respectively. The other options, "Rule-Declare-DecisionTree" and "Rule-Declare-Decisiontable," are not declarative rules but are used for decision-making processes. "Rule-Obj-MapValue" is used to map values between properties, and it is not a declarative rule either.

In a screen flow, each step allows the user to determine if they can jump to that step or if they can only jump back to it after it has been completed. This means that the user has control over the navigation within the flow and can decide whether to skip a step or go back to a previous step. This statement best explains how navigation is controlled within a screen flow.

Decision tables can associate a privilege with the ability to edit each individual cell. This means that in a decision table, specific privileges can be assigned to users or roles, allowing them to have the capability to edit or modify the content of each cell within the table. This level of granularity in access control allows for more precise control over who can make changes to specific parts of the decision table, ensuring data integrity and security.

Rule-Declare-Expression can use backward chaining as a method of propagation because it allows the system to infer the value of a property based on the values of other properties. Backward chaining starts with the goal, which is the property that needs to be determined, and then works backwards to find the values of the dependent properties that are needed to calculate the goal. This method is useful when there are complex relationships between properties and it allows for efficient calculation of values in a rule-based system.

Work can only be routed to a worklist if a data-admin-operator-id exists for the specified worklist. This means that in order for work to be assigned to a worklist, there must be an operator ID associated with that worklist. Without an operator ID, the work cannot be routed to the worklist for processing.

The recommended way to implement client-side calculations, according to Pegas best practice, is to build a declarative expression to calculate the grand total and use the calculated value HTML property on the GrandTotal screen to display it. This approach allows for efficient and dynamic updating of the grand total as the inputs change, without the need for additional client events or activities.

OnChange rules are different from Rule-Declare-Expression because OnChange rules have the capability to directly execute an activity, while Rule-Declare-Expression is used to set a single property. OnChange rules require a front-end user to make the change, and they can only track changes in top-level properties. Additionally, OnChange rules only use backward chaining to track changes, whereas expressions can use either backward or forward chaining.

The correct answer is to create a single assignment shape, set it to worklist, and set the switchtoWorkBasket if the .RecommendedOperator property is not set. This approach ensures that the work is routed to the operator specified in the .RecommendedOperator property if it is present. If the property is not present, the work will be routed to the GeneralWorkBasket. This approach allows for flexibility in routing the work based on the presence or absence of the .RecommendedOperator property.

Using the RDB-Save method to save/update instances to the PegaRules database may not be appropriate because not all properties are distinct database columns and some data may be lost. This means that certain properties may not be properly saved or updated in the database, leading to potential data loss or inconsistencies. It is more efficient and reliable to use the Obj-Save method for saving/updating instances in the PegaRules database.

not-available-via-ai

Spin-off flows are executed in the current requestor in a serial manner, however they do provide business parallelism for users to have assignments on the same work object. This means that while the spin-off flows are processed one after the other, multiple users can still work on different assignments related to the same work object simultaneously, allowing for parallelism and increased efficiency.

The calculation types available in a rule declare expression depend on the type of target property. Different target properties may require different types of calculations, such as summing up values or finding the maximum value. The calculation type needs to be compatible with the target property in order to perform the desired calculation accurately.

A Thread Level Declarative Page is a type of memory storage that holds data specific to a user's session. When the user logs out or their session expires, the Thread Level Declarative Page is removed from memory to clear up resources for other users. Additionally, when the application server is brought down, all active sessions and their associated Thread Level Declarative Pages are terminated. These three scenarios result in the removal of the Thread Level Declarative Page from memory.

During the execution of a Rule-Declare-Onchange, declarative expressions will not execute. This is because Rule-Declare-Onchange rules are triggered when the value of a property changes and are used to perform actions or validations based on that change. Declarative expressions, on the other hand, are evaluated during rule resolution and are not specific to property changes. Therefore, they do not execute during the execution of a Rule-Declare-Onchange.

The primary page in an activity serves as the context page, providing data and variables for the activity to work with. A step in an activity with a blank Step page column indicates that the step page is the primary page. When iterating through embedded pages, each instance of the embedded page becomes a step page, allowing the activity to access and manipulate the data within each instance.

Thread level pages can use a when to determine when the page needs to be refreshed, node level pages cannot. This means that thread level pages have the ability to dynamically refresh based on a condition, while node level pages do not have this capability.

In PRPC, a List View can be used to dynamically execute rules based on certain conditions. By defining the conditions in the List View and associating it with a Rule-Declare-Collection, the system can execute all Decision rules when the State is "Ohio" and also keep an audit of which rules were executed. This approach does not require any custom development and can be achieved using the out-of-the-box functionality provided by PRPC.

The rules that fit the "Build for Change" paradigm and are best candidates for being delegated are Rule-Declare-Casematch, Rule-Declare-Constraint, Rule-Declare-Decision Tree, and Rule-Obj-When. These rules allow for flexibility and adaptability in the system, as they can be easily modified or updated without impacting the overall structure. Delegating these rules to specific individuals or teams ensures that they can be efficiently managed and updated as needed, allowing for continuous improvement and adaptation to changing requirements.