Quiz
Background Processing
This quiz has question types that open in the usual player.
Questions in this quiz (15)
1What are two reasons to configure background processing rules for tasks? (Choose Two)
- ATo automate tasks that otherwise rely on human interaction.
- BTo defer tasks to a specific time, such as off-peak hours.
- CTo process case updates more efficiently.
- DTo allocate a task to a specific node or nodes in a cluster.
2A Standard queue processor: (Choose 4)
- AUsed for simple queue management to process real-time messages
- BSpecify the activity to run on the queued item
- CChoose a locking option
- DSpecify an optional access group to establish context (optional)
- ESupports higher throughput scaling
- FUsed for customized or delayed queue management.
- GSpecify the queue processor
- HConfigure and enable the queue processor rule
3A Dedicated queue processor: (Choose 4)
- AUsed for simple queue management to process real-time messages
- BSpecify the activity to run on the queued item
- CChoose a locking option
- DSpecify an optional access group to establish context (optional)
- ESupports higher throughput scaling
- FUsed for customized or delayed queue management.
- GSpecify the queue processor
- HConfigure and enable the queue processor rule
4Upload an insurance claim to an external database after normal business hours: [blank_start]Dedicated queue processor[blank_end]
Submit each status change to an external system. Processing does not require high-throughput: [blank_start]Standard queue processor[blank_end]
Delete older records from log tables: [blank_start]Job Scheduler[blank_end]- AJob Scheduler
- BStandard queue processor
- CDedicated queue processor
5Background processing is useful when a [blank_start]process-intensive task[blank_end] [blank_start]or automation[blank_end] is required. Executing tasks [blank_start]in the background[blank_end] allows users to continue the case or other work and [blank_start]improves system scalability[blank_end] and [blank_start]performance[blank_end]. By moving tasks to [blank_start]dedicated nodes or off-peak hours[blank_end], users can continue to process cases without any impact caused by the uploading operations.
A Pega Platform installation often spans a set of servers called a [blank_start]cluster[blank_end]. Within this cluster, each [blank_start]server, or node[blank_end], can be designated a [blank_start]node type[blank_end] for specific processing tasks. The system can then allocate [blank_start]background tasks[blank_end] to one node while [blank_start]processing user interactions[blank_end] on a different node. As a result, the system can optimize performance on each node for the types of [blank_start]interactions that the node supports[blank_end].
To enable background processing for an application, select the [blank_start]Include in background processing[blank_end] option on the application rule. Enabling this option for an application updates the [blank_start]System Runtime Context[blank_end] record to include the application when performing background processing tasks. The System Runtime Context [blank_start]automatically manages[blank_end] the resolution of background processes.
For Pega Platform updates, your existing context is migrated from the current [blank_start]ASYNCPROCESSOR[blank_end] requestor type to the System Runtime Context record. When creating a new application with the New Application wizard, the Include in background processing option is [blank_start]enabled by default[blank_end].
[blank_start]All queue processor and job scheduler[blank_end] rules resolve against the context specified in the System Runtime Context. The System Runtime Context [blank_start]must include[blank_end] the application rulesets to resolve and run Queue Processors and Job Schedulers. Configure the application record to include the application in background processing.- Aprocess-intensive task
- Bor automation
- Cin the background
- Dimproves system scalability
- Eperformance
- Fdedicated nodes or off-peak hours
- Gcluster
- Hserver, or node
- Inode type
- Jbackground tasks
- Kprocessing user interactions
- Linteractions that the node supports
- MInclude in background processing
- NSystem Runtime Context
- Oautomatically manages
- PASYNCPROCESSOR
- Qenabled by default
- RAll queue processor and job scheduler
- Smust include
6Pega Platform has two options for performing system tasks on objects in the background: [blank_start]queue processors and job schedulers[blank_end]. A job scheduler schedules a [blank_start]recurring task[blank_end] that runs at a [blank_start]specified interval[blank_end] and identifies the [blank_start]tasks to process at that time[blank_end]. Job schedulers are most suitable for tasks that [blank_start]recur on a regular basis[blank_end], such as overnight batch jobs.
A [blank_start]queue processor[blank_end] queues tasks for background processing, identifying [blank_start]which tasks to queue[blank_end].
Tasks can be queued using either a [blank_start]Run in Background automation[blank_end] or the [blank_start]Queue-For-Processing method[blank_end] in an activity. The parameters for each option [blank_start]differ depending on whether you use[blank_end] the standard queue processor or a dedicated queue processor.
Tasks can be queued [blank_start]immediately[blank_end] or the queue [blank_start]can be delayed[blank_end].
Tasks are defined with an [blank_start]activity that runs on[blank_end] the queued item.
Specify the number of [blank_start]processing threads[blank_end] to allocate to the task and the [blank_start]number of nodes[blank_end] that can run background tasks. The options affect the [blank_start]throughput or scalability[blank_end] of the queue processor.
[blank_start]Vertical scaling[blank_end] — The number of threads
[blank_start]Horizontal scaling[blank_end] — The number of nodes
Each thread is assigned on each node of the specified node type
For example, the three threads on background processing nodes and three background processing nodes in the cluster allow you to run nine available threads for processing.
On the Queue processor rule form, you may also need to configure the [blank_start]Processing retries[blank_end] section.
[blank_start]Max Attempts[blank_end] – The number of attempts to retry a queued process.
[blank_start]Initial Delay[blank_end] – The number of minutes before the second attempt of a queued process.
[blank_start]Delay Factor[blank_end] – The multiplier for the delay between attempts. For example, if the initial delay is 1 minute and the delay factor is 2, the retries would be 1, 2, 4, 8, and so on, minutes apart.- Aqueue processors and job schedulers
- Brecurring task
- Cspecified interval
- Dtasks to process at that time
- Erecur on a regular basis
- Fqueue processor
- Gwhich tasks to queue
- HRun in Background automation
- IQueue-For-Processing method
- Jdiffer depending on whether you use
- Kimmediately
- Lcan be delayed
- Mactivity that runs on
- Nprocessing threads
- Onumber of nodes
- Pthroughput or scalability
- QVertical scaling
- RHorizontal scaling
- SProcessing retries
- TMax Attempts
- UInitial Delay
- VDelay Factor
7Queue processors and job schedulers handle read/write transactions on database objects differently.
A [blank_start]job scheduler[blank_end] includes steps in the activity to identify the items expiring in seven days, apply the discount, and then [blank_start]save and commit[blank_end] the change. They [blank_start]use the activity to manage[blank_end] any [blank_start]read/write operations[blank_end] they perform on database objects.
[blank_start]Queue processors[blank_end] [blank_start]automatically manage the read/write[blank_end] transactions on database objects. If they needs to update an object, the activity [blank_start]should not[blank_end] contain any steps to perform the read/write objects to the database as part of the process.- Ajob scheduler
- Bsave and commit
- Cuse the activity to manage
- Dread/write operations
- EQueue processors
- Fautomatically manage the read/write
- Gshould not
8Which two statements are true about the job scheduler? (Choose Two)
- AWhen creating job scheduler activities, separate business logic from transaction logic.
- BThe job scheduler can only be run once per day.
- CThe job scheduler and queue processor handle database transactions the same way.
- DThe job scheduler runs an activity.
9What task can you perform in Admin Studio?
- ACreate a new user.
- BMigrate an application.
- CView broken processors.
- DCreate a case type view.
10Where can you view detailed information about processor functions?
- AOverview landing page in Admin Studio
- BJob scheduler rule form
- CData flow for the processor
- DCase life cycle in App Studio
11Queue processors and job schedulers are [blank_start]background jobs[blank_end] that use [blank_start]an activity[blank_end] to implement [blank_start]processing logic[blank_end]. These [blank_start]activities[blank_end] expect to finish processing in less than a few seconds. If an activity takes longer to complete, use the following best practices to ensure that work items are not affected during the shutdown process.
[blank_start]Break down large work items[blank_end] into [blank_start]smaller work items[blank_end]. Queue them to a queue processor, and process them [blank_start]individually[blank_end]. If you have background tasks that break into multiple tasks with different performance capabilities, consider [blank_start]dividing[blank_end] them and [blank_start]scaling each independently[blank_end].
To ensure that activity logic can gracefully [blank_start]handle restarts without corrupting data[blank_end] or introducing inconsistencies into your application, use [blank_start]checkpoints[blank_end] by saving the [blank_start]state of jobs[blank_end] in [blank_start]persistent storage[blank_end] or [blank_start]as messages in a queue[blank_end] that is [blank_start]appropriate to the use case[blank_end]. Consider a scenario where a work object can have the following statuses: New, In-Progress, and Processed. You can read [blank_start]all of the work object records[blank_end] to be processed, loop through them one by one, [blank_start]mark the status[blank_end] of the current work object as In-Progress, continue with the business logic, and when processing is complete, [blank_start]change the status[blank_end] to Processed.
When configuring job scheduler activities, [blank_start]separate business logic[blank_end] from [blank_start]transaction logic[blank_end]. For example, a company sends congratulatory letters to employees celebrating work anniversaries. The business logic identifies employees with work anniversaries. The transaction logic executes the process to send the letter. [blank_start]Logic separation[blank_end] enables you to adjust processing if the activity [blank_start]cannot obtain a lock[blank_end]. To separate the logic, you can [blank_start]create one activity[blank_end] for the business logic and a [blank_start]second activity[blank_end] for the transaction logic.- Abackground jobs
- Ban activity
- Cprocessing logic
- Dactivities
- EBreak down large work items
- Fsmaller work items
- Gindividually
- Hscaling each independently
- Idividing
- Jcheckpoints
- Khandle restarts without corrupting data
- Lstate of jobs
- Mpersistent storage
- Nas messages in a queue
- Oappropriate to the use case
- Pall of the work object records
- Qmark the status
- Rchange the status
- Sseparate business logic
- Ttransaction logic
- ULogic separation
- Vcannot obtain a lock
- Wcreate one activity
- Xsecond activity
12To ensure that the system processes your activities successfully, check the [blank_start]statuses of the activities[blank_end] that queue processors resolve. In Admin Studio, click Resources > Queue processors. For example, you can [blank_start]identify and fix issues[blank_end] that affect [blank_start]indexing information about assignments[blank_end] to ensure that your [blank_start]data is available in the system[blank_end].
Two options are available:
Click [blank_start]Trace any node[blank_end] to automatically choose the node (the node is randomly assigned).
Click [blank_start]Trace specific node[blank_end] to select the node.
Queue processors and job schedulers can [blank_start]fail to process items[blank_end] correctly for several reasons. For example, the processes [blank_start]cannot obtain a lock[blank_end] on an entry because the processes [blank_start]lack security access[blank_end] or another user or process [blank_start]already has a lock on the object[blank_end].
Queue processors queue objects and then process them. AIf the [blank_start]process fails[blank_end] and the system cannot [blank_start]commit a queue entry[blank_end], the system puts the entry into [blank_start]failure status[blank_end] and indicates the process is broken. The system also [blank_start]reverses any changes[blank_end] the process initiated.
In Admin Studio, you use the [blank_start]Queue processor landing page[blank_end] to [blank_start]trace and monitor[blank_end] Queue Processor rules in your application. On this landing page, you view [blank_start]advanced statistics[blank_end] on each queue processor by viewing the data flow. If there is an error, users with the [blank_start]SysAdmin4[blank_end] role can troubleshoot issues with the queue processor by [blank_start]tracing the running processes[blank_end] and examining the items in the [blank_start]Broken queue[blank_end].
The job scheduler [blank_start]triggers items[blank_end] to process at [blank_start]preconfigured times[blank_end]. The job scheduler [blank_start]does not queue items[blank_end]. To troubleshoot issues with job scheduler processes, you can run a [blank_start]trace on the failing[blank_end] processes. You can also configure the [blank_start]Performance tool[blank_end] to manage statistic aggregation for job scheduler rules.- Astatuses of the activities
- Bidentify and fix issues
- Cindexing information about assignments
- Ddata is available in the system
- ETrace any node
- FTrace specific node
- Gfail to process items
- Hcannot obtain a lock
- Ilack security access
- Jalready has a lock on the object
- Kprocess fails
- Lcommit a queue entry
- Mfailure status
- Nreverses any changes
- OQueue processor landing page
- Ptrace and monitor
- Qadvanced statistics
- RSysAdmin4
- Stracing the running processes
- TBroken queue
- Utriggers items
- Vpreconfigured times
- Wdoes not queue items
- Xtrace on the failing
- YPerformance tool
13Refund requests are queued for overnight processing. What two pieces of information are required to queue the refund request? (Choose Two)
- AThe ID of the queue processor.
- BThe date and time at which the queued item can be processed.
- CThe case ID of the refund request case.
- DThe ID of the customer requesting the refund.
14How does a developer review information about queue processors running in their system?
- AIn Dev Studio, from the Records Explorer, select Queue Processor.
- BIn Admin Studio, navigate to the Jobs landing page.
- CIn Admin Studio, navigate to the Queue processors landing page.
- DIn Dev Studio, from the case life cycle, select the Run in background automation.
15Type "Queue" or "Job":
Directly handles read/write transactions on database objects: [blank_start]Queue[blank_end]
Best for periodic or recurring tasks: [blank_start]Job[blank_end]
Standard or dedicated processing available: [blank_start]Queue[blank_end]
Save and commit steps included in the activity: [blank_start]Job[blank_end]
Runs at a specific time: [blank_start]Job[blank_end]- AQueue
- BJob
- CQueue
- DJob
- EJob
Information
- Description
- User has deleted their subject information Quiz on Background Processing, created by Deleted user on 14/09/2022.
- Author
- Deleted user
- Language
- English
- Views
- 13
- History
- Created on 14 Sep 2022 · updated on 15 Sep 2022
- Tags