Pega CSSA mock test 2 is a quiz on the Pega certification of the senior system architect. Are you a techie and working towards this certification? If so, take up the quiz below and sharpen you knowledge.
PRLOGGING .XML
Rule-Admin-System Settings
PRCONFIG.XML
You cannot customize the thresholds, the defaults are fine and do not need to customize
You can set a breakpoint for a specific step within an activity
Open an named clipboard page to display current data
Select which requestor session you wish to trace
Re-run a specific set of steps with updated data
They are essentally the same thing .ts personal preference as to which to use
You can see activity rule executions only in the application profiler
To see where database actions are taking place, the Application profiler provides more details
The Application profiler is the better tool to see the step-by-step where the elapsed and CPU time
Effective clipboard management is one of the best ways for an architect to reduce an applications memory footprint performing garbage collection
When available additional JVM heap space will always improve the time in garbage collection
As PRPC architects it is important to set properties to null so that they can be discarded as part of garbage collection
As long as reporting is done by a third party tool garbage collection will have a minimal impact on the performance of a PRPC
The overall time elapsed from when a user triggers Client Side Java Script
The time spent executing Declarative expressions
The time for a response from a web service called using the Connect-SOAP method
The time for a database query to execute and return results to PRPC
The size of the HTML stream returned to the user/browser
Use the restriction tab on the class definition form
Create an access rule
Lock the JumboLoanRS ruleset
Create a series of activities and declarative xpressions
Work-
MyCo-
MyCo-Work-
Myco-Div1-Work-
In both development and run-time
In run time only
In development only
None of the above
Rule Set only
Class and Ruleset
Circumstancing
A or B depending on additional details
B or C depending on additional details
EAA can generate a FrameWork and corresponding Implementation Layer in one go
You need to generate Framework and Implementation layer in two separate EAA runs
The EAA can create the Enterprise Organizational and Divisional Reuse layers
When generating a New Implementation, I can pick the work classess in the FrameWork to go
For generated connector class and rules that are shared by all application within a division
For classes and rules internal to a given division
For generated connector class and rules that are shared across all divisions
To internationalize an application
Except when the base rule flag is checked on the circumstanced rule
Even when the unqualified rule is in a higher rules set version
Except when the base rule flag is checked on the unqualified rule
Only when the unqualified rule is in the same same ruleset version as the circumstanced rule
The situation will never occur as PRPC will never allow you to check out the activity in version 01-01-03, if it has been checked out in version 01-01-02
PRPC will flag the activity in version 01-01-03 with a merge flag which user B will have to manually resolve by reponding to changes that user A introduced similar to how other SCMS/RCS systems such as ClearCase work
PRPC will not warn User B if user A modifies the activity in a lower version of the same Ruleset
PRPC will warn User B if User A modifes the activity in a lower version of the same Ruleset by diplaying a yellow warning at the bottom of the rule.
The Enterprise class structure allows building enterprise grade application that are scalable and extensible
Pega best practices call for all applications on PRPC v 5 platform be built using the Enterprise Class Structure pattern
The Enterprise Class Structure provides the foundation for superior application performance
To put most rules in the Enterprise shared layer
To create new classes for each type of implementation
To consider the most appropriate class and ruleset for each rule
To use it as is and do not try to alter it
As-Of date using a property on the work object and date qualified circumstancing uses the current system time
As-of date processing uses the rule whose date circumstance matches a work object property
As-of date processing requires a RuleSet effective date
Data qualified circumstancing allows selecting rules based on a work object property.
Withdrawn rules make refactoring the class a rule "applies to" easier
Seting a rule's availabiltiy to "Withdrawn" is the same as setting it to "NO"
Withdrawn rules remove all instances of the rule from the database
Withdrawn rules are the same as blocked rules
Thoroughly document all rules
Paramterize rules
Use a Dynamic class referencing design pattern
Limit ur design to utilize not more than 8 different rule types
Use naming conventions when naming rules
It is the primary way to notify other developers that the rule should not be refused
It is the primary way to notify other developers that the rule can be reused but should not be overridden
It allows a developer to move the rule to a more generic class in the class structure
It allows a developer to use an older version of the same rule (and the same applies to class)
True
False
Stored in a page group with the subscript representing the role of the party
Stored in a page list with the subscript representing the priority of the party
Only used if the application is sending email correspondence
Data instances that are linked to work objects as attachments
Rule-HTML-Property instances cannot be circumstanced
Rule-HTML-Property instances belong to a ruleset version
Rule-HTML-Property instances can accept parameters as input
Rule-HTML-Property instances have an applies to class
Folders can contain 2 covers
A folder can contain another folder
A folder contains an embedded page of all the work objects that it contains
A folder cannot have a process run on it
A folder does not have a status
History is automatically added during key events, such as SLA deadlines as well as by application specific rules
History is automatically deleted from the PRPC database when the associated work object is resolve
History is only added by application specific rules
History is stored as a page list inside a work object so it can be easily displayed in the harness
Both page name parameters and prompt pages provide a way to pass a page reference to an activity so page names don’t need to be hardcoded
Page name parameters can only be used to pass top-level pages
Page names parameters create aliases for pages that can be used by any rule that is executed after an activity
Passing pages by reference requires java Code
Wait!
Here's an interesting quiz for you.