A Pega certification is not an easy achievement. Most people take up exams severally before getting it right. This Pega CSSA Mock Test will help you prepare well to get through at the first shot. All the best.
Since it is a column in a table in a database you can extract the BLOB and use it in another system
The BLOB contains the same clear text xml which you see when clicking the rule data or the View XML option on the clipboard
The "pzPVStream" can be eliminated by use of simple tables (those without embedded pages and page lists)
The BLOB enables a single table to store complex data structure that would normally require multiple tables in a non blob database.
The Data-Admin-DB-Table record for the class group the work object belongs to and the Access Group
The Rule-Set the class belongs and Data-Admin-DB-Table definitions
Data-Admin-DB-Table record associated to the class group the work object belongs to
The Rule-Set the class belongs to
Rule Instance Cache
Static Contect Cache
Look up list cache
Conclusion cache
Dictionary cache
There is a way to select the agent and force its execution
You can delay the agent processing from SMA and then trace the given requestor
We can set a breakpoint in the activity that the agent runs to have tracer pick it up
We can set a log message step in the activity the agent runs to have tracer find the activity
) Declare expression or Declare Trigger rules can be used to copy a single embedded property to a top level page property and can be exposed
Declare Index rules can be used to expose many or all of the items in an embedded list or group
Ask your DBA to create a database level index.This is a good mechanism to expose embedded properties
) Exposing a new property with the Modify Databse schema Wizard will automatically populate all rws of the new column - both for new rows and existing rows
The default table does not contain adequate indexes and columns for performance
Data is purged by the system cleaner
The default table names are too generic
The default table is too small to hold of ur data
Because the Preflight tool will flag it as bad practice
JMS message services support need to be provided
Support for two-phase commits is required
Support for EJB services need to be provided
J2EE security is required
JSR-94 support is required
) Ruleset prerequisites as specified in the "Requires Ruleset and Versions" fields of the Ruleset form are enforced at runtime
Pre-requisites Rulesets govern the creation of new rules during development
RuleSet prerequisites are validated during export of application archives
When saving Application rules, Ruleset prerequisites are validated
) Data-Agnet-Queue instances are not locked so they allow you to control the behavior of Agents in a locke RuleSet at run time
Data-Agent-Queue instances are created by PRPC to support the new Queue for Agent functionality which was provided in PRPC 5.4
) Data-Adgent-Queue instances are created automatically by PRPC whenevr Queue-For-Agent method is used in an activity step to queue work for agent
Data-Agent-Queue instances are data instances which are used by the Queue manager functionality to allow for concurrent access to a queued piece of work by agents running on multiple nodes
) Data-Agent-Queue instances represent the master definition of PRPC agents and have been deprecated in PRPC 5.4 in favor of using Rule-Agent-Queue
It is used by PRPC to synchronize changes to the Data-Agent-Schedule instances whenever a Rule-Agen-Queue is modified
It invalidates rule caches on a per node basis using entries in the pr_sys_updatescache table
It processes changes to the Lucene indexes that support full text searches
It synchronizes the lookup list cache deletions and any rule-file-deletes
It is used by PRPC to send information to PAL on a weekly basis so that the performance analysis can be performed over a period of time
It supports incremental rollbacks
Rollback is not supported by PRPC.The only way to do a rollback is by using the compensation action method
Rollback is a way to rollback an object to a previous state using the History instance for a work object
Rolls back the entire deferred stack of operation
The Rule assembly cache is a memory based cache that stores the generated XML and resulting class files, post compilation since what finally gets executed is XML , not Java code
The Rule Assembly cache is a memory cache which is used to determine the right instance or existence of the generated Java code on disk used by the classloader
The Rule Assembly Cache is a memory cache of the rule data accessed when using the Obj-Open, Obj-Open-By-Handle.The cache is checked when rule data is needed
The Rule Assembly cache is used by PRPC to feed the instance cache as the instance cache is the instance of a given rule for which code has been generated
The overall size of a PRPC work object impacts the time it takes to compress and store the onject in the database
During ListView execution, PRPC will only retrieve/expand the BLOB if the properties retrieved are not exposed
During ListView execution, PRPC will only retrieve/expand the BLOB if the properties used in the generated where clause are not exposed
PRPC only retrieves/expands the BLOB via the use of the Obj-Open and obj-Open-B-Handle methods
By default the PRPC BLOB is stored in an encrypted format in the database
Use the PLA-PegaRULES Log Analyzer to analyze the ALERTS, System Logs and GC
Run PAL on every screen in the application
Run Pre-Flight
Ask the DBA to monitor the database
The Alert log contains garbage collection details to help support performance monitoring
The Pega Log details the internal runtime exceptions thrown by the Application Server
The Pega Log contains messages created by the Application Server
The Log Usage log contains details on how the system is being used
The alert log contains only alerts and supports performance monitoring.
Partition the database
Avoid arithmetic operations or functions in the where clause
Write queries that operate on large results sets but only display small amounts of data
Create and use indexes effectively
Avoid using Where clauses
You can configure within an activity rule which log file you want to write errors to
You are able to configure within SMA which rules write to which log files
You can update prlogging.xml file to change the efault PegaRules log file name
You can update the prlogging.xml file to change the log file names, roll over settings and even add new log files for specific rule type and class within PRPC
Renaming a class and propagating the name change through the heirarchy and rule references
Converting a Map-Value into a decision table
Search and replace of a string in all rules
Merging one ruleset into another
PAL
Profiler
SMA
DBTrace
PLA_ PegaRules Log Analyzer
AES
SMA
Excel
The Preflight checks rules when run to validate if they follow best practices
) The Preflight tool checks the Index Warnings table to find which rules have warnings on them- (pr_index_warning table)
The Preflight tool is flexible and allows for you to create your own custom warnings on rules, possibly to implement additional best practises for client
The Pre-flight tool will check for specialization and re-use and determine if your application is following the best practices of an enterprise class structure.
It is a non-critical alert that says you have too much data on the clipboard
It is triggered when the total number of bytes sent to the browser in an interaction exceeds a byte count threshold
It is triggered when the total number of bytes read to the browser in an interaction exceeds a byte count threshold
It is triggered when the total number of bytes saved to the database in an interaction exceeds a byte count threshold
Using the SMA you can view the contents of the instance cache which are displayed in the form of an excel file
Using the Developer Portal you can viewe the contents of the instance cache which are displayed
By viewing the XML files from the TEMPDIR\PRGenJava\XML directory
By Viewing the XML files from the pzInsKey column by usng JDBC code
Node-Pulse
Rule Cache
System-Update
System-Pulse
It writes a message to log4j
only ignores the rule and continues to search for the next rule via rule resolution
It throws an exception
It either ignores the rule or throws an exception depending on the prcofig.xml setting
Wait!
Here's an interesting quiz for you.