PEGACLSA_62V2 試験問題を無料オンラインアクセス

A PRPC application is built for handling a Customer Support Call Center. Authentication is handled outside PRPC. When operators are added to the external system, they must be able to access the PRPC application and perform work.
Which approach is best suited for this requirement? (Choose One)

• A.Create operators manually
• B.Use an authentication activity that creates operators dynamically
• C.Configure a shared or guest operator with the appropriate privileges to perform the work
• D.Create a background process that polls the external system on a regular basis and creates the corresponding operators

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

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.Both shapes create separate Threads for sub-processes they create
• C.Split-Join allows you to execute different sub-flows whereas Split-For-Each calls the same process on different pages
• D.Split-For-Each allows you to execute different sub-flows whereas Split-Join calls the same process on different pages

In a PRPC application the ViewPortfolioInformation section has three accordion layouts: Stock Details, Stock graphs and Trade/Payment history.
What is the preferred design you will do to make the screen display latest details when they are accessed? (Choose One)

• A.Enable the Refresh When active feature on accordion layouts to get the recent transaction
• B.Add Refresh When condition on each Accordion layouts that refreshes on a When rule which uses a timer to fire the event
• C.Defer load on all accordion layouts, selecting them will render data everytime
• D.Write a timer script that periodically does a section refresh

In a PRPC application the Collect Information section has three tabs: Personal Details, Transaction History and Comments. When the user is working on the case they will open the transaction history only when it's required. What is the preferred design you will do to make the screen render faster? (Choose One)

• A.Enable Defer Load, so the page loads only with the contents in the active tab
• B.Enable Refresh When active flag so it refreshes the list when accessed
• C.Modify the layout to use accordion because transaction history need not be displayed unless its required
• D.Disable the transaction history tab and use a visible when condition that uses run on client to enable the transaction tab when required