MyCo uses PRPC application to process claims. One of the user groups involved in the process should be able to perform assignments on any piece of "urgent" work no matter who it is assigned to using the "get most urgent" functionality.
Which of the following approaches would you most likely take to ensure that workers from that user group would perform any "urgent" work no matter who it is assigned to? (Choose One)

• A.Create a special privilege rule to the workers in that user group. Make sure only workers from that group have been attributed the privilege
• B.Create a special Role for the workers in that user group. Update the standard activity supporting the "Get most urgent" functionality to bypass any security measure if the user has that special role
• C.Circumstance the standard List view rule used by "Get Most Urgent" to pull work from workers' worklist based on user's workgroup. Update the circumstanced version to not check the assigned operator
• D.Attribute the highest skills level to the workers in that user group

Comment: *

Name: *

Email: *

Verification: *

Users have reported slowness on the production environment.
To find the cause, which of the following steps is NOT required? (Choose One)

• A.Use SMA to view the Log-Usage report to identify the performance issues that happened on that node over the past day
• B.Request for a developer access so you can run PAL in production
• C.Download the log files and import them in PLA to check for any CRITICAL warnings and EXCEPTIONS in the system log file
• D.Start Global DB Tracing in SMA to check for any DB issues on a specific node

Comment: *

Name: *

Email: *

Verification: *

A work type MyCo-FW-PurchaseApp-Work-Request has a PageList property .LineItems of class MyCo-FW-PurchaseApp-Data-Item.
Another work type, MyCo-FW-PurchaseApp-Work-Order has a PageList property .ItemsForVendor of class MyCo-FW-PurchaseApp-Data-Item.
An item has a calculation .TotalPrice = .Quantity * .UnitPrice.
The application is experiencing behavior where the TotalPrice is calculating correctly for Requests but not for Orders.
Which of the following is the most likely explanation for this issue? (Choose One)

• A.The expression is likely defined as backward chaining
• B.The expression is likely defined as a context-free expression ("regardless of any page it is contained in")
• C.The expression is likely defined as forward chaining
• D.The expression is likely defined as a context-sensitive expression ("only when the top level page is of the applies to class")

Comment: *

Name: *

Email: *

Verification: *

An application, created by MyCo, has a number of rules implemented as decision tables that use "Title" as an input as seen in the sample rule below:
MyCo is finding a number of application defects caused by incorrect spellings in the title field. The valid titles are stored as field values. MyCo is requesting options to help prevent these types of errors.
Which of the following approaches is most applicable? (Choose One)

• A.Create a custom rule form that uses harnesses and sections and can be configured however MyCo desires
• B.Recreate the logic in decision trees and use function aliases to limit the options via a drop down box
• C.Create a custom validation rule in the Rule-Declare-DecisionTable class to validate that the .Title property always has a valid value
• D.Use the table edit of the .Title property to reference the field values, the decision table will then automatically validate that the value is valid

Comment: *

Name: *

Email: *

Verification: *

Which of the following statements is most accurate about the Split-For-Each and Split-Join shapes? (Choose One)

• A.Split-For-Each can only be used when iterating over a list of work objects
• B.Split-Join allows you to execute different sub-flows whereas Split-For-Each calls the same process on different pages
• C.Both shapes create separate Threads for sub-processes they create
• D.Split-For-Each allows you to execute different sub-flows whereas Split-Join calls the same process on different pages

Comment: *

Name: *

Email: *

Verification: *