Practice Test Geeks(CPSA) Certified Pega System Architect Practice Test
← All CPSA Flashcard Decks

Application Design & Case Management Flashcards

7 cards from real CPSA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Application Design & Case Management flashcards as text

  1. In Pega application design, what is the purpose of a 'Built-On' application layer?

    Answer: It provides a base layer of rules that a child application extends and overrides

    A Built-On layer is a parent application whose rules are inherited by the child application, enabling reuse and customization through rule overrides.

  2. What is the role of a RuleSet in a Pega application?

    Answer: A RuleSet is a container that groups related rules and controls their versioning and availability

    RuleSets package related rules together, and their version stacks determine which rule version is found during rule resolution.

  3. When should a Pega architect create a new Case Type versus using a child case (subcase)?

    Answer: Create a new case type when the process is independent; use a subcase when the process is part of a parent case's lifecycle

    Independent, standalone processes warrant their own case type, while subcases model work that is logically part of and dependent on a parent case.

  4. In Pega, what does 'case type inheritance' allow a child case type to do?

    Answer: Reuse and override stages, steps, and rules defined in a parent case type

    Case type inheritance lets a child case type inherit its parent's lifecycle, rules, and UI, and override specific elements without duplicating configuration.

  5. Which Pega design principle recommends building applications in layers to separate core, product, and implementation concerns?

    Answer: Situational Layer Cake (SLC)

    The Situational Layer Cake organizes application rules across enterprise, division, product, and implementation layers for maximum reuse and governance.

  6. What is the key difference between a 'Data Type' and a 'Case Type' in Pega application design?

    Answer: Data Types store field values only; Case Types also define a process lifecycle and assignments

    A Data Type models a business entity with properties, while a Case Type adds a full process lifecycle, stages, assignments, and SLAs to that entity.

  7. In App Studio, which section allows an architect to configure the channels through which a case type can be initiated?

    Answer: Channel interfaces under application settings

    Channel interfaces in application settings let architects specify whether a case can be created via web, mobile, email, chatbot, or other channels.