What is the difference between using the Call and Branch methods in an activity step to invoke other activities?
Answer(s): D
Option D is correct because in Pega activity steps, Call transfers control back to the originating activity after the called sub-activity completes, preserving the call-return flow, whereas Branch is a direct jump that can bypass subsequent steps in the calling activity. A) Incorrect: Call and Branch do not differ primarily in debugging capability or run-time performance as stated. B) Incorrect: Branch does not override security to allow testing in production; security is governed by access roles and rules, not the Branch mechanism. C) Incorrect: Branch does not create a new thread for asynchronous processing; it is a control-flow construct like Call but with different continuation semantics.
An application contains a flow action with an Apply to: class of TRB-HRApps-Work-Feedback in a locked ruleset. When updating the application, you save the existing flow action into a new minor version of the ruleset this time applied to TRB'HRApps-Work so it can be used by more than one case type.How do you prevent the application from using the rule in TRB-HRApps-Work-Feedback?
Answer(s): A
Option A is correct because locking the original ruleset TRB-HRApps-Work-Feedback and creating a new minor version applied to TRB-HRApps-Work, with the rule’s availability set to Blocked, prevents the application from resolving/using the TRB-HRApps-Work-Feedback rule while still keeping the original rule intact for other contexts. Incorrect — B: Withdrawn hides the rule but can still be resolved in some contexts; not a controlled resolution approach. Incorrect — C: Not available is not a valid availability state in Pega and does not guarantee prevention. Incorrect — D: Final applies to a different rule scope (TRB-HRApps-Work) and does not affect the TRB-HRApps-Work-Feedback applicability.
A medium-size toymaker wants to fulfill orders received during the peak season in December and process the orders in batches multiple times a day.How do you implement this use case?
Option D is correct because a queue processor is designed to handle high-volume, asynchronous processing of items as they arrive, suitable for peak-season ordering and batch-like processing when integrated with queues. A) A single scheduled job cannot natively handle dynamic batching or streaming arrival rates. B) Multiple scheduled jobs are inefficient and harder to coordinate for accumulated orders. C) Pre-forming batches and waiting for fullness introduces delays and lacks real-time responsiveness. Therefore, a queue processor provides scalable, continuous processing aligned with Pega's queue-based processing capabilities.
DRAG DROP (Drag & Drop is not supported)In the Answer Area, drag each log name on the left to its intended purpose on the right.
A travel reservation servicing case includes a service level for responding to requests. The service level intervals vary according to passenger status, class of service, and fare type.Which implementation satisfies this requirement?
Answer(s): B
Option B is correct because: A multivariate circumstanced rule, with a circumstance definition and template, allows varying the service level according to multiple factors (passenger status, class, fare type) by applying different circumstanced rules at runtime, enabling granular, data-driven intervals.A) Incorrect — A multivariate circumstanced rule alone lacks the formal structure of a circumstance definition/template needed to model multiple conditional axes consistently. C) Incorrect — A single property circumstanced rule cannot capture multiple condition dimensions with distinct templates; it limits to property-driven scoping. D) Incorrect — A single property circumstanced rule omits the necessary circumstance definition/template and cannot express multivariate conditions.
In your purchasing application, you use a decision table with vendor discount codes. You want to delegate the decision table.In which ruleset do you save the decision table to allow delegation?
Answer(s): C
Option C is correct because delegation requires the rule to be in the Production ruleset to be delegated to end users; production is the deployment target for runnable rules. A) Organization is not a runnable ruleset for delegation. B) Integration is used for external integrations, not for delegating business rules. D) Application is the instance-level application container, not the destination for delegating individual decision tables. INSUFFICIENT_KNOWLEDGE
You are preparing to create a new major version of an application ruleset in which there are multiple minor and patch versions. How do you create the new ruleset version?
Answer(s): B,D
Option B is correct because the Ruleset Maintenance wizard provides the merge operation to consolidate multiple minor/patch versions into a new major version, preserving rules with proper versioning. Option D is also correct because creating a new major ruleset version and then copying the highest existing version into it is a valid approach to establish the new major version baseline. Incorrect — A misstates skim as a merge; it would not consolidate rules properly. Incorrect — C’s “lock and roll” does not describe the merge/copy process used to create a new major version.
HOTSPOT (Drag & Drop is not supported)The current version of an application lists ABC:02-02 as an application ruleset. The ruleset versions listed in the Answer Area are also present on the system.In the Answer Area, identify the ruleset versions that the skim operation considers when you perform a major version ruleset skim on ruleset ABC.
Post your Comments and Discuss Pegasystems PEGAPCSSA87V1 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PEGAPCSSA87V1 content, but please register or login to continue.