I85PREP
⌘ K
Pega LSA study materials
Pega LSA study resources

Pega LSA practice questions

One question at a time. Build your Pega LSA understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Architecture (written exam)

In Pega application architecture, which layer holds reusable rules that are shared across multiple applications and are intended to be managed as a separate product?

  1. The organization layer
  2. The application layer
  3. The framework layer Correct answer.
  4. The division layer

Explanation

The framework layer holds rules meant to be reused and extended by other applications, and it is typically built and versioned as a distinct product. The organization and division layers hold enterprise-wide and business-unit rules respectively, while the application layer holds rules specific to one application. This separation lets a framework evolve without forcing change on every consuming application.

Question 2Architecture (written exam)

A team needs a rule to be available to every application in the enterprise without being changed by any of them. Which built-on application should own that rule?

  1. The division layer application
  2. Each individual application
  3. The organization layer application Correct answer.
  4. The framework layer application

Explanation

Rules placed in the organization layer are inherited by all applications built on it and are not meant to be overridden per application. This is the correct home for universal standards such as enterprise data classes and shared utilities. Division and application layers are for narrower scope, and duplicating a rule in each application defeats reuse.

Question 3Architecture (written exam)

What is the primary architectural purpose of a ruleset in a Pega application?

  1. To define the security roles available to operators
  2. To group rules into a versioned, deployable unit Correct answer.
  3. To schedule background processing jobs
  4. To store the case data for a case type

Explanation

A ruleset is the unit of versioning and deployment for rules; rules are checked in and versioned together at the ruleset level. Security roles, case data, and job scheduling are handled by other rule types entirely. Understanding rulesets as deployment units is fundamental to managing application change.

Question 4Architecture (written exam)

Which component of the Pega layer cake concept determines the order in which rules are resolved when the same rule name exists at multiple layers?

  1. The operator's access group
  2. The ruleset list order on the application
  3. The application's built-on hierarchy Correct answer.
  4. The class hierarchy of the case type

Explanation

Rule resolution walks the application's built-on hierarchy, so the layered structure of applications determines which version of a rule wins. The ruleset list and class hierarchy participate in resolution, but the built-on chain is what defines the layer ordering. Architects use this to predict override behavior when designing reusable components.

Question 5Architecture (written exam)

An architect is designing a case type where multiple subcases must complete before the parent case can move forward. Which Pega construct is the standard way to model this?

  1. A spin-off case created by a data transform
  2. A child case added to a case-wide list Correct answer.
  3. A stage with a parallel process
  4. A subprocess within a flow

Explanation

Child cases added to a case-wide list let the parent track multiple subcases and proceed when the required ones reach a resolved status. This is the standard pattern for decomposing work across case types. Spin-off cases run independently and are not tracked as children, and subprocesses stay within the same case.

Question 6Architecture (written exam)

Which design choice best supports a case type that must handle a high volume of short-lived, stateless work with minimal persistence overhead?

  1. A data type instead of a case type Correct answer.
  2. A case type with many stages and approvals
  3. A case type backed by a single long-running parent case
  4. A case type with extensive case-wide attachments

Explanation

When work has no long-running lifecycle, approvals, or audit requirements, a data type is lighter than a case type and avoids case instance overhead. Case types add stages, SLA processing, and history that are unnecessary for simple reference data. Choosing the lighter construct is a core architecture decision.

Question 7Architecture (written exam)

What is the recommended approach for integrating with an external system whose interface is unstable and may change frequently?

  1. Hard-code the endpoint in each activity
  2. Replicate the external data nightly into a case type
  3. Encapsulate the integration in a connector and expose it through a data page Correct answer.
  4. Call the external system directly from every data page

Explanation

Encapsulating the integration behind a connector and data page isolates external volatility to one component, so changes do not ripple through the application. Direct calls scattered across the application multiply the impact of any interface change. This separation is a standard architecture principle for external dependencies.

Question 8Architecture (written exam)

Which Pega feature provides a declarative, cached way to retrieve reference data from an external system for use across the application?

  1. A data page Correct answer.
  2. A flow action
  3. An activity
  4. A section

Explanation

Data pages load and cache data according to a defined scope, making them the declarative choice for reference data used across cases. Activities are procedural and do not provide the same caching semantics. Flow actions and sections are UI constructs, not data retrieval mechanisms.

Question 9Architecture (written exam)

An architect must ensure that a data page used for a large reference list does not reload on every access within a case. Which data page scope achieves caching for the duration of a single case?

  1. Requestor
  2. Thread Correct answer.
  3. Node
  4. Application

Explanation

Thread scope caches the data page for the life of the current interaction thread, which aligns with a case's processing context. Requestor scope persists longer across interactions for the same user, and node and application scopes are broader still. Choosing the narrowest sufficient scope avoids stale data and memory pressure.

Question 10Architecture (written exam)

Which mechanism should an architect use to enforce that a property value is validated consistently regardless of which flow or UI invokes it?

  1. A validate rule on the property's class Correct answer.
  2. A flow action pre-processing activity
  3. A required field setting on the section
  4. A UI control with client-side validation

Explanation

A validate rule on the class applies wherever the property is edited, providing consistent server-side enforcement independent of the UI. Section-level and client-side settings only apply to the specific UI context. Centralizing validation in the class is the durable architectural choice.

Question 11Architecture (written exam)

What is the architectural benefit of using a case type inheritance hierarchy in Pega?

  1. It eliminates the need for access groups
  2. It allows shared case behavior to be defined once and reused by specialized case types Correct answer.
  3. It reduces the number of rulesets required for deployment
  4. It automatically generates the database schema

Explanation

Case type inheritance lets a parent case type define common stages, properties, and processes that child case types extend, reducing duplication. It does not change ruleset deployment, security, or schema generation. This is a key lever for managing large case inventories.

Question 12Architecture (written exam)

Which security model component in Pega determines the set of applications and rulesets an operator can access at runtime?

  1. The access group Correct answer.
  2. The access role
  3. The privilege
  4. The operator record

Explanation

An access group links an operator to an application and its rulesets, and it carries the access roles that grant permissions. The operator record references access groups but does not itself define application access. Access roles and privileges define what actions are permitted once access is established.

Question 13Architecture (written exam)

An architect needs to restrict a sensitive case type so that only users in a specific business unit can create cases of that type, while other users can still view them. Which design best achieves this?

  1. Removing the case type from the application
  2. A UI section that hides the create button
  3. Access roles combined with a case type level condition or privilege check Correct answer.
  4. A single access role granting full access to all users

Explanation

Combining access roles with a condition or privilege on the create action enforces the restriction at the platform level while allowing read access. Hiding a button is cosmetic and does not enforce security. Removing the case type entirely would block the view access that is required.

Question 14Architecture (written exam)

Which Pega construct is used to define the attributes and behavior of a business entity that is not a case, such as a customer or product?

  1. A data type Correct answer.
  2. A flow
  3. A case type
  4. A work queue

Explanation

Data types model non-case business entities, holding their properties and related data pages. Case types model work with a lifecycle, while work queues and flows are routing and process constructs. Separating data types from case types keeps the model clean.

Question 15Architecture (written exam)

An architect is choosing between a single large case type and several smaller case types linked by child cases. Which consideration most strongly favors the smaller case types?

  1. Avoiding the use of data pages
  2. Enabling independent lifecycles and SLAs for each unit of work Correct answer.
  3. Minimizing the number of access groups
  4. Reducing the number of rules in the application

Explanation

Smaller case types let each unit of work have its own stages, SLAs, and reporting, which is valuable when the pieces progress independently. Rule count, data pages, and access groups are not direct drivers of this decision. Decomposition should follow lifecycle and ownership boundaries.

Question 16Architecture (written exam)

What does the Pega guardrail warning about a flow containing too many shapes most likely indicate to an architect?

  1. The flow may be overly complex and should be refactored or decomposed Correct answer.
  2. The flow will fail at runtime
  3. The flow lacks an access role
  4. The flow cannot be versioned

Explanation

Guardrail warnings flag design complexity that hurts maintainability, suggesting the flow be simplified or split. They are advisory and do not cause runtime failure or block versioning. Architects use guardrails as a signal to improve design quality.

Question 17Architecture (written exam)

Which approach best supports performance when a data page is accessed frequently but the underlying data changes rarely?

  1. Configure an appropriate refresh strategy and a scope that balances freshness with reuse Correct answer.
  2. Use requestor scope with no refresh settings
  3. Set the data page to reload on every access
  4. Remove the data page and query directly each time

Explanation

Pairing a suitable scope with a refresh strategy lets frequently used, slowly changing data be reused without unnecessary reloads. Reloading on every access or querying directly defeats caching. A deliberate refresh strategy keeps data acceptably fresh.

Question 18Architecture (written exam)

Which Pega feature allows an architect to define a reusable sequence of steps that can be invoked from multiple flows without duplicating logic?

  1. A subprocess Correct answer.
  2. A data transform
  3. A flow action
  4. A section

Explanation

A subprocess encapsulates a reusable sequence of flow steps that can be called from multiple flows, reducing duplication. Sections are UI, flow actions are UI steps, and data transforms manipulate data rather than define process flow. Reuse through subprocesses improves maintainability.

Question 19Architecture (written exam)

An architect observes that a case type's SLA is being missed because assignments sit in a work queue with no eligible users. Which design change most directly addresses the root cause?

  1. Increase the SLA goal interval
  2. Remove the SLA from the case type
  3. Convert the case type to a data type
  4. Add a routing strategy that ensures eligible operators exist for the queue Correct answer.

Explanation

The root cause is that work is routed to a queue with no eligible operators, so a routing strategy that guarantees eligibility addresses it directly. Extending or removing the SLA masks the symptom, and converting to a data type abandons the case lifecycle. Fix routing before tuning SLAs.

Question 20Architecture (written exam)

Which consideration is most important when deciding whether to build a framework application versus a single application?

  1. The size of the database
  2. Whether multiple applications will share a common, extensible base Correct answer.
  3. The number of developers on the team
  4. The number of UI sections in the application

Explanation

A framework is justified when several applications will reuse and extend a common base, making the shared investment worthwhile. Team size, database size, and UI section count are not the deciding factors. The decision is about reuse and variation across applications.

Question 21Architecture (written exam)

An architect must ensure that changes to a shared utility rule do not break consuming applications. Which practice best supports this?

  1. Disabling the rule for all consumers
  2. Versioning the ruleset and testing consumers before promotion Correct answer.
  3. Editing the rule directly in production
  4. Copying the rule into each application

Explanation

Versioning the shared ruleset and validating consumers before promotion provides a controlled path for change. Direct production edits bypass testing, disabling breaks consumers, and copying creates divergence. Controlled versioning is the core safeguard for shared components.

Question 22Architecture (written exam)

Which Pega capability supports exposing application functionality to external systems through a defined service contract?

  1. A data page
  2. A service rule such as a REST service Correct answer.
  3. A work queue
  4. A section

Explanation

Service rules define the contract by which external systems invoke application functionality, such as a REST service. Data pages retrieve data, sections are UI, and work queues route assignments. Service definitions are the standard integration surface for inbound calls.

Question 23Architecture (written exam)

An architect is evaluating a design where a data transform is used to populate a case from an external payload. Which risk should be assessed first?

  1. Whether the transform is invoked from a flow action
  2. Whether the mapping handles missing or malformed fields without failing the case Correct answer.
  3. Whether the data transform is versioned
  4. Whether the transform uses a section

Explanation

The primary risk in mapping external payloads is that missing or malformed fields cause failures or corrupt data, so defensive mapping must be assessed first. Versioning, UI sections, and invocation points are secondary concerns. Robust input handling protects the case lifecycle.

Question 24Architecture (written exam)

Which architectural principle best explains why business logic should be placed in the class layer rather than in UI sections?

  1. UI sections are deprecated
  2. Sections cannot reference properties
  3. Class rules run faster than sections
  4. Class-level rules apply consistently across all channels and entry points Correct answer.

Explanation

Placing logic in the class layer ensures consistent behavior regardless of which UI or channel invokes it, supporting reuse and integrity. Sections can reference properties, are not deprecated, and performance is not the deciding factor. Separation of concerns is the governing principle.

Question 25Architecture (written exam)

An architect must design for a scenario where the same case type is used by two business units with different approval thresholds. Which design provides the cleanest separation?

  1. Hard-code the threshold in the approval flow
  2. Remove approvals from one business unit
  3. Use circumstancing or a configurable property to vary the threshold by business unit Correct answer.
  4. Create two entirely separate applications with duplicated logic

Explanation

Varying behavior through circumstancing or configuration keeps one maintainable case type while honoring unit-specific rules. Hard-coding or duplicating logic creates maintenance burden and divergence. Configuration-driven variation is the cleaner architecture.

Question 26Architecture (written exam)

In Pega, which layer of the application stack is intended to hold organization-specific rules that are shared across multiple applications built on the same foundation?

  1. The ruleset that holds only circumstanced UI sections
  2. The implementation layer of a single application
  3. The enterprise (organizational) layer Correct answer.
  4. The framework layer owned by a single application

Explanation

Pega's situational layer cake separates enterprise-wide rules, reusable framework rules, and application-specific implementation rules. The enterprise layer holds rules shared across the whole organization, such as common data classes and enterprise-wide integrations. Framework and implementation layers sit above it and specialize behavior.

Question 27Architecture (written exam)

An architect wants to reuse a common set of case type rules across several applications while allowing each application to override specific behavior. Which Pega mechanism supports this directly?

  1. Using a single ruleset for all applications
  2. Duplicating the case type in every application
  3. Copying the rules into each application's ruleset
  4. Class inheritance with ruleset stacking across the built-on applications Correct answer.

Explanation

Ruleset stacking and class inheritance let an application build on a base application and override rules at the higher layer without copying them. This is the core mechanism for framework-style reuse in Pega. Duplication loses the single point of maintenance.

Question 28Architecture (written exam)

Which Pega construct is the correct place to define a reusable integration connector so that multiple case types can call the same external service without duplicating configuration?

  1. A section rule in each case type
  2. A flow action in each case type
  3. A data transform in each case type
  4. A Connect REST rule in a shared ruleset Correct answer.

Explanation

Connectors such as Connect REST are integration rules that can be placed in a shared ruleset and invoked from multiple case types. Sections, flow actions, and data transforms are UI or data-mapping rules, not service connectors. Centralizing the connector avoids duplicated endpoint and authentication configuration.

Question 29Architecture (written exam)

Which Pega security component determines the set of applications and rulesets an operator can access at runtime?

  1. The access group Correct answer.
  2. The operator record alone
  3. The role in the organization structure
  4. The application definition alone

Explanation

An access group binds an operator to an application, a ruleset stack, and a default portal. It is the runtime unit that determines which application and rulesets are available. Operator records reference access groups, and the application definition does not by itself grant access.

Question 30Architecture (written exam)

Which Pega guardrail warning most likely indicates that an architect should reconsider splitting a flow into smaller sub-processes?

  1. A flow includes a sub-process shape
  2. A flow uses a decision shape
  3. A flow contains an excessive number of shapes Correct answer.
  4. A flow has a single assignment shape

Explanation

Pega guardrails flag flows with too many shapes because large monolithic flows are hard to read, test, and maintain. Breaking the logic into sub-processes improves clarity and reuse. Using decision, sub-process, or assignment shapes is normal and not itself a warning.

Question 31Architecture (written exam)

Which Pega capability allows an architect to expose application functionality to external systems through a defined service contract?

  1. A data page scoped to the node
  2. A service REST rule in a ruleset Correct answer.
  3. A Connect REST rule in a ruleset
  4. A section rule exposed as a harness

Explanation

Service rules define inbound contracts that external systems call, while connectors define outbound calls. Service REST is the standard way to publish functionality to external consumers. Connectors and data pages are for outbound or internal data retrieval.

Question 32Architecture (written exam)

An architect must ensure that a data page holding a large reference list does not reload on every access within a case. Which configuration most directly achieves this?

  1. Convert the data page into a when condition
  2. Set the data page to reload on every access
  3. Set the data page scope to thread or requestor so it is cached for the session
  4. Configure the data page with no refresh strategy Correct answer.

Explanation

Refresh strategy governs when an already loaded data page is refreshed. With no refresh strategy, repeated access reuses the loaded page while it remains available in its scope. Scope alone does not disable refresh triggers; explicit removal, cache eviction, or the end of scope can still require reloading.

Question 33Architecture (written exam)

An architect needs to restrict a sensitive case type so that only users in a specific business unit can create cases of that type. Which combination is most appropriate?

  1. A data transform that clears the case type for other users
  2. An access control policy on the case class combined with access group membership for the business unit Correct answer.
  3. A when condition on the case type's starting flow
  4. A UI section hidden for other users

Explanation

Access control policies and access groups enforce authorization at the engine level. Combining a policy on the case class with access group membership ensures only the intended business unit can create the case. UI hiding and flow conditions are not security controls.

Question 34Architecture (written exam)

An architect is choosing between a single large case type and several smaller case types linked by child cases. Which consideration most strongly favors the child-case design?

  1. The work has distinct lifecycles, teams, and service-level expectations that should evolve independently Correct answer.
  2. The work has no reporting requirements
  3. The work always completes in a single assignment
  4. The work requires only one operator to ever touch it

Explanation

Child cases are appropriate when sub-work has its own lifecycle, ownership, and SLAs that should be managed independently. A single case type suits tightly coupled work with one lifecycle. Reporting and operator count are secondary considerations.

Question 35Architecture (written exam)

Which consideration is most important when deciding whether to build a framework application versus a single implementation application?

  1. Whether multiple applications will share substantial common behavior that must be maintained in one place Correct answer.
  2. Whether the application uses case types at all
  3. Whether the application needs any integrations
  4. Whether the team prefers a single ruleset

Explanation

A framework application is justified when substantial behavior is shared across multiple applications and must be maintained centrally. If only one application exists, a single application is simpler. Integrations and case type usage do not by themselves require a framework.

Question 36Architecture (written exam)

An architect must ensure that a change to a shared utility rule does not break consuming applications. Which practice best supports this?

  1. Delete the utility and recreate it with the same name
  2. Copy the utility into each application before editing
  3. Edit the rule in place in the shared ruleset
  4. Version the ruleset containing the utility and require consuming applications to adopt the new version deliberately Correct answer.

Explanation

Ruleset versioning isolates changes so consuming applications adopt new behavior on their own schedule. Editing in place propagates changes immediately and risks breakage. Copying rules creates divergence, and deleting removes history and dependent references.

Question 37Architecture (written exam)

An architect is evaluating a design where a data transform populates a case from an external payload. Which risk should be assessed first?

  1. Whether the transform is defined in the correct ruleset
  2. Whether the transform validates and maps every required property and handles missing or unexpected fields Correct answer.
  3. Whether the transform runs faster than a when condition
  4. Whether the transform uses the correct naming convention

Explanation

When mapping external payloads, the primary risk is incomplete or unsafe mapping that leaves required properties unset or accepts unexpected data. Validation and defensive handling of missing fields must be assessed first. Naming, speed, and ruleset placement are secondary concerns.

Question 38Architecture (written exam)

An architect must design for the same case type used by two business units with different approval thresholds. Which approach best supports this without duplicating the case type?

  1. Circumstance the approval decision rule by business unit Correct answer.
  2. Ask each business unit to maintain its own ruleset copy
  3. Hard-code the threshold in the approval flow
  4. Create two separate case types for each business unit

Explanation

Circumstancing allows one rule to behave differently based on a property such as business unit, avoiding duplication. Separate case types or ruleset copies multiply maintenance. Hard-coding a single threshold cannot satisfy both units.

Question 39Architecture (written exam)

Which Pega construct is used to define the attributes and behavior of a business entity that is not a case, such as a customer?

  1. A data class Correct answer.
  2. A flow action
  3. A case type
  4. A work class

Explanation

Data classes model business entities that are not cases, such as customers or products, and are often used with data pages. Work classes model case processing. Case types and flow actions are case and UI constructs, not entity models.

Question 40Architecture (written exam)

An architect notices that a frequently accessed data page loads slowly because it aggregates several external services. Which design approach best improves response time while preserving accuracy?

  1. Call the services directly from each section
  2. Load the data page asynchronously and cache it with an appropriate refresh strategy Correct answer.
  3. Remove caching so every access is fresh
  4. Increase the number of services aggregated

Explanation

Asynchronous loading combined with a suitable refresh strategy reduces user-facing latency while keeping data reasonably current. Removing caching increases latency, and calling services from sections spreads the problem. Adding services worsens the bottleneck.

Question 41Architecture (written exam)

An architect must integrate with an external system whose interface is unstable and may change frequently. Which design choice best isolates the application from that volatility?

  1. Wrap the integration behind a connector and data page facade so consumers depend on a stable internal contract Correct answer.
  2. Embed the endpoint URL in each section
  3. Duplicate the connector in every case type
  4. Call the external endpoint directly from every flow

Explanation

A facade that exposes a stable internal contract isolates consumers from external interface changes. Direct calls and duplicated connectors spread the volatility across the application. Embedding URLs in sections couples UI to the external system.

Question 42Architecture (written exam)

Which mechanism should an architect use to enforce that a property value is validated consistently regardless of which flow or channel creates the case?

  1. A when condition in each flow
  2. A UI section edit validate on one harness
  3. A flow action pre-processing step in one flow
  4. A validate rule or declarative constraint on the class Correct answer.

Explanation

Validation placed on the class applies wherever the property is set, regardless of channel or flow. Flow-level when conditions and single-harness edit validates only cover their own path. Class-level validation is the consistent enforcement point.

Question 43Architecture (written exam)

An architect must decide how to model a reusable sequence of steps invoked from multiple flows. Which Pega construct is most appropriate?

  1. A duplicated set of shapes in each flow
  2. A sub-process shape referencing a shared flow Correct answer.
  3. A data page
  4. A section rule

Explanation

A shared flow invoked through a sub-process shape centralizes reusable steps and keeps each calling flow readable. Duplicating shapes creates maintenance drift. Sections and data pages address UI and data concerns, not process reuse.

Question 44Architecture (written exam)

An architect is reviewing a design where a single case type handles high-volume, short-lived, stateless work. Which design choice best supports scalability?

  1. Use a lightweight case type with minimal persistence and automated processing where possible Correct answer.
  2. Add more manual approval steps to the case type
  3. Store each case in a dedicated data class
  4. Attach a long-running SLA to every assignment

Explanation

High-volume, short-lived work benefits from lightweight case types that minimize persistence and manual steps. Added approvals and long SLAs increase latency and load. Dedicated data classes per case add overhead without benefit.

Question 45Architecture (written exam)

An architect must ensure that a shared utility rule change can be rolled back quickly if it causes defects in production. Which practice best supports this?

  1. Edit the rule directly in production
  2. Rely on operators to report defects after the change
  3. Deploy through ruleset versions with a documented rollback to the prior version Correct answer.
  4. Disable the guardrail that flags the change

Explanation

Versioned ruleset deployment enables a controlled rollback to the prior version if defects appear. Direct production edits leave no clean rollback path. Disabling guardrails removes safeguards, and relying on reports delays remediation.

Question 46Architecture (written exam)

An architect is evaluating whether to use a framework application when only one application currently exists but two more are planned within a year. Which reasoning is most sound?

  1. Never build a framework until all applications exist
  2. Build the framework now only if the shared behavior is well understood and the future applications will genuinely reuse it Correct answer.
  3. Always build a framework regardless of reuse
  4. Build the framework only if it reduces the number of rulesets

Explanation

A framework is justified when shared behavior is understood and real reuse is expected. Building one speculatively risks over-engineering, while waiting until all applications exist can cause costly rework. Ruleset count is not the criterion.

Question 47Architecture (written exam)

An architect must design a case type where different business units require different approval flows but share the same data model and case lifecycle. Which approach best balances reuse and variation?

  1. Create fully separate case types per business unit
  2. Keep one case type and circumstance the approval sub-process by business unit Correct answer.
  3. Duplicate the data model per business unit
  4. Put all approval logic in a single UI section

Explanation

Circumstancing the approval sub-process preserves the shared data model and lifecycle while allowing per-unit variation. Separate case types duplicate the model, and UI-embedded logic cannot enforce process variation reliably. This balances reuse with controlled variation.

Question 48Architecture (written exam)

An architect observes that a declarative expression recalculates on every property change and is degrading performance. Which analysis is most appropriate?

  1. Remove all declarative rules from the application
  2. Determine whether the expression is over-broad and should be scoped to the properties it actually depends on Correct answer.
  3. Increase the number of dependent properties
  4. Convert the expression to a UI section

Explanation

Declarative expressions recalculate when their dependencies change, so an over-broad dependency set causes excessive recalculation. Scoping dependencies to what the expression truly needs reduces churn. Removing declarative rules wholesale or moving logic to UI is not a sound fix.

Question 49Architecture (written exam)

An architect must choose a caching strategy for reference data that changes daily but is read thousands of times per hour. Which approach is most appropriate?

  1. Use a data page with a refresh strategy aligned to the daily change cadence Correct answer.
  2. Cache indefinitely with no refresh
  3. Reload the data on every access to guarantee freshness
  4. Load the data directly in each UI section

Explanation

A refresh strategy aligned to the data's actual change cadence balances freshness with the performance benefit of caching. Reloading on every access wastes the read volume, and caching indefinitely risks stale data. Loading in each section bypasses caching entirely.

Question 50Architecture (written exam)

An architect is organizing an application stack for a new Pega solution. Which rule resolution layer is intended to hold organization-wide assets such as enterprise data classes and shared integrations?

  1. The built-on application layer, which only contains Pega-provided rulesets
  2. The ruleset layer, which stores rules directly in the application record
  3. The organization layer, built as a component application on top of the platform Correct answer.
  4. The implementation layer, where case types for each business unit are defined

Explanation

In the Pega application stack, the organization layer sits above the platform and below division and implementation layers. It is the correct home for enterprise-wide reusable assets such as organizational data classes, shared integrations, and common utilities so that multiple applications can inherit them.