PEGAPCSSA85V1 Practice Exam Questions with Answers Pega Certified Senior System Architect (PCSSA) 86V1 Certification

Add a Persist Case shape after the first step.

Apply a when condition to the first step to persist only cases requiring updates.

Configure the starting flow to instantiate the case type as a temporary case.

Configure the first step to instantiate the case type as a temporary case.

During User Acceptance Testing

Throughout the application development life cycle

Before migrating an application to a testing system

After the application is deployed to a production system

Use the attribute data-pega-event-onpagedata.

Use REST methods to call Pega microservices.

Call a Pega API function from the host server.

Call the function pega.web.api.doAction().

Update the portal format in the skin applied to the portal.

Update the portal type on the portal record.

Change the section layout on the harness referenced on the portal record.

Configure a navigation record to describe the new portal format.

Hide noncritical columns.

Use grid layouts rather than repeating dynamic layouts to display tabular data.

Configure UI controls to use native controls on mobile devices.

Set the width for layouts in percentages.

Columns to display are: Operator Name, Last updated Case ID, Last updated Case Status, Update Date.

Columns to display are: Operator Name, Operator Division, Count of Purchase Requests created.

Columns to display are: Manager, Name, Count of operators that report to each manager.

Columns to display are: Operator Name, Operator Division, Count of Purchase Requests created by the operator. Filter the results by unresolved status.

set default values for a property

test the validity of an input value

customize a list of allowed values for a property based on the context of the property

define the values used in a circumstance template

define the properties used in a circumstance

define the values available to an end user in the application

define the values used in a circumstance

define the list of all circumstance values for a rule

Organization

Framework

Implementation

Division

copy data from a data page option on a property

separate the functional behavior of a rule from specific business contexts

define the values used in a circumstance

help improve business users' ability to adapt to changing business conditions

Create a new case

Add a property to a data class.

Access data from a data page

Update a decision table.

An Access Group that has access to the production ruleset

An Access Role that has access to the production ruleset

An unlocked ruleset added to the Application rule as a production ruleset

A separate Operator ID that has access to the delegated rules

Pega log

Service-PAL log

Alert log

BIX log

This option limits the workbasket search to only those workbaskets defined in the user's work group.

This option organizes all assignments in all of the workbaskets the user is associated with into a single list before the list is filtered and sorted.

The workbaskets associated with the user are checked first. If no assignments are found in the user's workbaskets, the user's worklist is checked.

When a user clicks the Next Assignment link, the system checks the user's worklist. If assignments are available in the user's worklist, the assignments are filtered and sorted.

Set default locking on purchase requests and set the do not lock the parent option on purchase orders.

Set default locking and the do not lock the parent option on purchase orders.

Set optimistic locking on purchase requests and the do not lock the parent option on purchase orders.

Set default locking and the do not lock the parent option on purchase requests.

Create a data page

Create a property for each environment

Create a data transform

Create a report definition

The copy data from a data page option on a property

No specific feature — just use a data page directly in the application

The Property-Ref activity method

The refer to a data page option on a property

Identify the user role of the type of user who would access the portal.

Determine which skin to use to apply branding to the portal.

Change the application(s) available to users.

Configure the positioning of the navigation pane within the portal.

Use an SQL call to exchange data between the mashup and hosting web page.

Use the data-pega-event-onpagedata attribute to configure the default value for the gadget.

Use a queue processor to pass updated attributes to the gadget on the hosting web page.

Use an action object configured as a script to perform additional actions on a web mashup gadget.

Use the Javascript function doAction() to set or read data values through the hosting web page.

Select Refer to a data page on .Product.

Select Copy data from a data page on .Product.

Configure .Product to refer to a keyed data page.

Define a reference property that refers to the data page.

Set up branch ruleset for each team.

Create a new application for each team.

Create a new ruleset version for each team.

Create a production ruleset for each team.

Decrease the weights of the weighted conditions.

Increase the weights of the weighted conditions.

Increase the weighted condition sum threshold.

Decrease the weighted condition sum threshold.

Configure a text box to allow date entry.

Use a calendar control that displays an entire year.

Use a calendar control that displays an entire month.

Provide separate controls for month, day, and year.

Use the Ruleset Maintenance wizard to merge the existing rules in the relevant ruleset versions to the new version.

Use the Ruleset Maintenance wizard to skim the relevant ruleset versions to copy the highest version of existing rules to the new ruleset version.

Create a new application ruleset using the appropriate version number, then copy the highest version of existing rules into the new ruleset version.

Use the Application Structure landing page to lock and roll the existing ruleset versions to the new version.

identify a layer of the Enterprise Class Structure

combine related properties by usage

assign work to a specific group of users

store data from different child classes in a single table