To ensure that only HR Managers have read access to a candidate's reference letter attachment, the

tasks involved include restricting read access according to a When condition (B) and configuring

attribute-based access control on the Attachment Category (C). The When condition can specify

criteria that must be met for the attachment to be accessible, such as the user's role being an HR

Manager. Attribute-based access control allows for the definition of access rules based on attributes

of the data or user, providing a flexible and granular approach to securing sensitive attachments like

reference letters.

Reference: Pega Community documentation on attachment security and attribute-based access

control.

The two most common ways to expose your application to an external system are to leverage the

Pega API (B) and to create a web service with the Service wizard (D). The Pega API provides a set of

out-of-the-box RESTful endpoints for performing operations within the Pega Platform. The Service

wizard simplifies the creation of SOAP or REST services, enabling external systems to interact with

Pega applications.

Reference: Pega Community documentation on Pega API and Service wizard.

The correct configuration for two parallel cases that run independently is the Subprocess shape with

the Spinoff flow option enabled (Option C). This allows the Retirement planning case to proceed in

parallel without waiting for, or reporting to, the Account review case. Reference: Pega official

documentation on case design and flow shapes.

A Declare OnChange rule is designed to perform an action when a specified property changes. The

action that a Declare OnChange rule can perform includes executing a data transform, which allows

for the automated update of properties when a change is detected in the specified property.

Reference: Pega official documentation on Declare OnChange rules.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/PEGA_PEGACPSSA23V1/page_52_img_2.jpg

Reference: https://academy.pega.com/topic/log-files/v1

To satisfy the requirement where service level intervals vary according to multiple criteria (passenger

status, class of service, and fare type), you would create a multivariate circumstanced rule, a

circumstance definition, and a circumstance template. This allows you to create SLAs that vary based

on the combination of these criteria. Reference: Pega official documentation on circumstancing rules.

In Pega's ruleset hierarchy, a ruleset can reference rules in its own ruleset as well as in any

prerequisites (and their prerequisites, recursively). Since MyCo lists MyCoInt and Customer as its

prerequisites and MyCoInt, in turn, lists Pega-ProcessCommander (which is not relevant here), MyCo

can reference rules in both Homelns and HomelnsInt. However, since only Homelns is explicitly

mentioned in the options, the correct answer is that MyCo can reference rules in Homelns.

Reference: Pega SSA course materials on ruleset hierarchy and ruleset validation.

Pega best practices recommend keeping activities short to enhance maintainability and readability.

Custom Java steps should be limited to reduce complexity and potential errors. Activities should also

be limited in general, with preference given to other rule types that are more declarative and less

procedural, like data transforms, to improve application performance and maintainability. Reference:

Pega SSA course materials on activity best practices.

In Pega's Enterprise Class Structure (ECS), standard functionalities that are shared across multiple

applications within an organization, such as sending a confirmation email, should be placed at the

Organization layer. This allows for reusability and standardization across various implementations

within the organization. Reference: Pega best practices for class design and ECS.

To create a class join in a report definition, you must select the type of match for key values (A) and

create a prefix for the joined class (C). Selecting the type of match, such as Inner Join or Left Outer

Join, determines how records from the primary class and the joined class are combined based on

matching key values. Creating a prefix for the joined class helps in distinguishing properties from the

joined class from those of the primary class, preventing naming conflicts and clarifying the report

definition. These actions are fundamental steps in setting up class joins in report definitions to

retrieve and display data from multiple related classes.

Reference: Pega Community documentation on report definition and class joins.