Free PEGACPSSA25V1 practice test: 30 questions with answers

A circumstance-qualified rule takes precedence over the unqualified rule with the same name when its circumstance matches, and the base rule is used only when no circumstance applies. Option A is wrong because circumstances apply to many rule types, not only data pages, C is wrong because rules are not chained by default, and D is wrong because the circumstance is part of how Pega selects the rule.

A queue processor consumes items placed on a queue asynchronously, so the user does not wait for the work. A nightly job scheduler runs at set times rather than reacting to each item, a keyed data page loads and caches data rather than processing queued work, and a declare expression recalculates values without sending messages.

Data classes hold reference and business data that is not a work item, and their names carry a Data- prefix. A work class holds case instances, so option B is wrong, and reference records are not stored as flows or as rule instances, so C and D are also wrong.

Built-on applications let several applications share a common ruleset stack, so the rules are maintained once and inherited by each application. Copying the rules creates duplicates that drift apart, rewriting them in each application repeats effort, and a spreadsheet is not a way to share live rules.

A locked ruleset version is protected against changes, so the correct path is a new ruleset version that carries the updated rule. Treating a lock as only a warning, deleting the version, or editing the database directly would all bypass Pega's rule management.

Routing to a work group lets any member of the team pick up the assignment, which avoids stalling the case when one person is unavailable. Routing to a single named operator, including the lead or the case creator, leaves the work stuck if that person is away.

A split starts parallel branches and a join holds the flow until every branch has completed, which matches the dependency. Sequential checks take longer than needed, continuing at once ignores the requirement, and a data page caches data rather than running verification steps.

Optimistic locking lets both users work and checks at save time whether the record changed since it was read, so the conflicting save is rejected. Pessimistic locking blocks access up front, no locking lets the last save overwrite earlier changes, and a shared read lock does not allow safe concurrent saves.

Pre-processing runs before the flow action's own processing, so it can set values the action depends on, and post-processing runs after the action completes, which suits follow-up work such as notifications. Validation rules check input, a report definition reads data, and a data page loads or caches data rather than sending messages.

In a Pega SLA the goal is the target completion time and the deadline is the later point at which the SLA is breached and escalation applies. On day two the goal has passed but the deadline has not, so the case is not yet in breach, and the other options misstate what the goal and deadline do.

An edit validate rule can test input against a regular-expression pattern so that values not matching the format are rejected before the save. A keyed data page loads reference data, a report definition finds problems only after saving, and a formatting utility changes display without enforcing the format.

A keyed data page is identified by a key such as a customer ID, so each customer's data can be loaded once and reused. A non-keyed page cannot separate customers, a report definition returns more than the screen needs, and a field value rule stores fixed values rather than retrieved records.

Node scope loads the data once per node and shares it across the requestors on that node, which suits common lookup lists. Thread and requestor scopes keep narrower copies, and case is not a data page scope option.

A Service REST rule defines an inbound REST endpoint that external callers can invoke, whereas a Connect REST rule handles outbound calls from Pega. A Service SOAP rule exposes SOAP messages rather than REST, and a data transform maps values without providing an endpoint.

HTTP 401 means the request was not authenticated, so missing or invalid credentials or authentication settings are the most likely cause. Overload typically appears as 503, a missing path as 404, and an oversized request as 413, so those do not explain a 401.

Tracer records the sequence of rules and activities executed in a session with their timings, which suits pinpointing slow steps in one transaction. The Clipboard shows property values, the alert log lists alerts and exceptions rather than a step-by-step run, and the Application Explorer only browses rules.

Pega Predictive Diagnostic Cloud collects alerts and exceptions from the system over time and highlights recurring problems, which supports prioritising tuning. Tracer suits a single session, the Clipboard shows property values for one requestor, and data page scope controls caching rather than measuring performance.

Reproducing the scenario in a test system and measuring it identifies the rules or data loads responsible before any change is made. Nightly restarts and higher timeouts can hide symptoms without finding the cause, and turning off logging removes evidence while adding little capacity.

The PegaRULES log records exceptions and stack traces that a generic on-screen message hides, so it is the first place to find the root cause. A report definition shows case data, a screenshot shows only what the user saw, and an access group controls permissions rather than recording errors.

Application Settings rules hold environment-specific values such as endpoint addresses, so the value can differ between systems without editing the rules that read it. A hard-coded URL forces rule changes in each environment, access groups control permissions, and a data page refresh copies values rather than configuring a per-environment address.

Attribute-based access control grants or denies access by comparing attributes such as Region on the user and on the case. Role-based control decides by role alone, encryption protects stored values rather than controlling visibility, and single sign-on governs authentication rather than record-level access.

Limiting who can view attachments through access control and encrypting stored content both reduce exposure of sensitive documents. Open links and passwords stored in free-text fields weaken protection, so they are not valid measures.

Assigning the role the team already uses gives the adjuster the same access through role-based control, with no excess rights. Copying or sharing logins breaks accountability, and the administrator role grants far more than the job needs.

Encryption at rest protects stored data, including backups, so the contents cannot be read without the decryption key. Encryption in transit protects data only while it moves, a session timeout does nothing for a copied backup, and masking in a report does not secure the stored values.

Audit tracking records changes to tracked values along with who made them and when, which answers the compliance question. A data page refresh only reloads data, a validation checks input without keeping history, and an access group controls visibility rather than recording changes.

Pega Web Embed is designed to place Pega content inside external web pages without rebuilding them. A standalone portal replaces the page rather than embedding into it, a data page only caches data, and a DX component is built for Pega's own user interfaces rather than an existing intranet menu.

A dedicated portal tied to an access group, with its own access restrictions, limits external users to their own cases. Administrator access exposes far more than needed, hiding menu items with styling does not restrict data, and a separate case type per customer does not solve visibility.

Custom DX components built with the Constellation SDK can be reused across Constellation pages, which matches the requirement. A data page stores data rather than UI, a report definition shows data without providing a reusable widget, and an access group controls visibility rather than building components.

The DX API exposes Pega operations over REST, so an authenticated external app can create cases and read assignments without the Pega user interface. Embedding the UI, reading database tables directly, or using nightly exports does not give the app safe, current access through a supported interface.

Using the standard components and design system tokens keeps screens consistent and upgrade-safe, with customisation only where it is truly needed. Heavy stylesheet overrides break consistency and upgrades, building from scratch loses standard behaviour, and copying components creates copies that must be maintained separately.