Pega Agent Interview Questions :Part 2

1. Why standard agent do not require an access group ?

Ans : For standard agents, each queue item is processed in the authorization context of the user whose actions or processing (work item, assignment, and so on) generated the queue item.


2. What is the significance of Auto Queue Management ?

Ans : When AQM is enabled, the system locks items that are retrieved from the queue by the agent until the agent is finished with the item (commit or rollback). If a transient condition means that the item cannot be processed (such as if the work item is locked), the system queues the item again and the agent can try processing it the next time it wakes up.


3. What are the various mode of agent ?

Ans : There are 3 types of modes :

Legacy — For old agents. This option is not available for agents created in PRPC 5.4 or later.
Standard — Indicates that this agent processes items from an agent queue and that it relies on the system to provide object locking and other transactional support.
Advanced — Indicates that this agent uses custom queuing. This is the option is recommended when the Pattern field is set to Startup.


4. Business wants to configure the interval period of 10 second, how will you do that ?

Ans : To configure an interval less than 30 seconds and at least five seconds, create the agent/minimumwakeup environment variable in the prconfig.xml file.


5. What are the patterns of agent ?

Ans : Generally 3 types.
Periodic — The agent runs the activity and then sleeps for the number of seconds entered in the Interval column.
Recurring — The agent runs the activity based on a specified calendar schedule (for example, every Monday at 5:00 P.M.).
Startup — The agent runs the activity once at startup based on a specified parameter.


6. What is the general wake time and how to change it ?

Ans : By default, this operation occurs every 10 minutes. This value can be updated in the prconfig.xml file setting:


7. We often talk about automatic timeout. Who handles this ?

Ans : Generally master agent monitors idle requestor sessions to enforce automatic timeouts.


8. What is master agent ?

Ans : Master agents are background processes operating on each Pega Platform node that are not defined by agents rules

Suggest an Edit

Suggested Posts

Provide Delivery Details
* indicates required field