Pegasystems PEGAPCLSA86V2 Lead System Architect (LSA) Pega Architecture Exam 86V2 Exam Practice Test

create an encrypted keyring password and replace the unencypted password in prconfig.xml

enter a password in an application ID instance and reference the external system

create an encrypted password with PR cipherGenerator and reference the external system

create an encrypted password with passGen and replace the unencrypted password in pconfig.xml

Require Access of Role to Object rules be specified for each layer in the class hierarchy and not inherited from parent classes.

Deny access to a rule if the privilege of the user is not defined in an Access of Role to Object.

Disable standard privileges providing administrator access to the application (for example AllFlows and AllFllowActions).

Ensure that all rules with the option of specifying a privilege have a privilege. Only users with the privilege can execute the rules.

Network security configuration

Database access configuration

System management application configuration

Log file access configuration

Resolution of the Event Booking case requires the Parking case to be resolved.

Parking, Weather, and Hotel cases must be instantiated for the Event case to process correctly.

The Weather case can be instantiated without a parent Event Booking case.

The Parking class must inherit from the Event Booking class.

limit the number of rows fetched from this table,

add one or more column indexes to this table.

Expose one or more columns within this table.

alter one or more column types in the table.

Prior to the first assignment in the ApproveRuleCheckin flow, add a decision shape where one output connector is equivalent to the submitting the SendBack flow action.

Implement a CheckForCustomWarnings activity for each rule included in the requirement. The activity issues a warning whenever the requirement's history tab criteria are not met.

Override the FindReviewers decision tree to invoke a when rule that evaluates the criteria, if the when rule returns true, the decision tree returns SendBack.

Override the SendBack Flow Action adding a pre-ctivity that transfers the assignment to the create operator if the rule's criteria are not met.

Use an advanced agent on a dedicated node to increment the pyUrgencyAssignAdjust value by 1 for every assignment that matches the selection criteria.

Use the assignment SLA to increment the pyUnjerncyAssiqnAdjust value by 1 every day the claim is in an open status.

Use a declare expression to increment the pytJrgcncyAsp/gnAdjur.t value to 1. When a claim processor opens the assignment, the urgency is increased by 1.

Use the overall SLA to increment the pyUrgencyAssignAdjust value by 1. Reset the goal date to the following day

Force a full syn for members of the access group

Enable caching for the access group

Create a model operator for the access group to authienticate users.

configure an offline-capable portal as the default portal for the access group

Each access group can use separate portals, harnesses, and sections. Use Specialty Components and use XML to pass data.

Level age the Case Manager and Case Worker as reference points to create new portals, if required. Use Special Components and use JSON to pass data.

Create different harnesses for each user's workspace. New portal rules are not needed. Define Specialty Components and use JSON to pass data.

Identify the functionality required for each portal. Customize the portal either by modifying the section or harness. Use Specialty Components and use XML to pass data.

create a separate service package for each WSDL.

create a service listener for each WSDL.

Run the service wizard for each WSDL.

place the service rules in separate classes, one class per WSDL

Specialize the pega customer service data pages that use account data.

Integrate with the system of record in the pega customer service account class

Rename the pega customer service data pages to match the system of record.

Integrate with the system of record to populate an Account data class.

Create a data transform to map the Account data class to the pega customer service Account class

Automated testing reduces costs by reducing the need to hire and I rain testing resources.

Automated testing accelerates the deployment of rules from the development environment to target environments.

Automated testing programmatically ensures quality of rules to maintain the integrity of the pipeline.

Automated testing allows for orchestration between automation server and the Execute Test REST service.

Create a decision table that evaluate role and application properties that return access group

Configure the authentication mapping to evaluate the decision table

Create a decision table that evaluate role and application attribute value that return access group

Add a method to the authentication activity to evaluate the decision table

cricumstance the section that describes the form for each language.

add the section to the translation package using the localization wizard.

create a filed value rule for the instruction text.

create a paragraph rule for the instruction text.

Ability to be circumstanced

Ability to be parameterized

Ability to be called directly from a decision table

Ability to be versioned

Have each subcase load a portion of the customer data prior to updating the parent case.

Use the Snapshot data access pattern to capture the customer data prior to subcase spin off.

Load the customer data in parallel using the Load -Data Page and Connect-Wair methods.

Use the System of Record (SOR) data access pattern when capturing the customer data.

Use the Queue-for-processing method

Use Utility smart shape

Use Run in Background smart shape

Use the Queue for -agent method

Add indexes to all columns.

Purge workparty UUI index tables periodically.

Schedule scripts to maintain frequently fragmented tables.

Purge and/or archive records based on the company's record retention policy.

Define most of the properties and sections at the work pool level.

Create a data type (if required) that corresponds to the case type.

Use the data reference field type in a case type's data model tab.

Drag and-drop a field group when defining a case view.

Define case type views using ".page.property" syntax.

Data transforms invoked by custom javascript

Data paga used to source a drop-down list

Validate rules on an email address field

Filed values used to populate a drop-down