Pega CPBA: Application Development

What the exam tests

Application Development questions test the rule-based architecture: class structure, rulesets, application stack, rule resolution, and the DevOps and testing practices that keep an application maintainable.

Core rules

• Applications are built from rules that apply to classes; the class hierarchy typically separates Work-, Data-, and Integration- classes.
• A ruleset is a versioned container for rules; ruleset versions move through DevOps stages.
• The application stack lists built-on applications; a specialization layer can override foundation rules without copying them.
• Rule resolution chooses the most specific applies-to class, ruleset, circumstance, and effective date.
• The situational layer cake organizes reuse across organization, division, unit, and work group.
• Guardrails, unit testing (PegaUnit), and scenario testing catch design and regression issues early.

Worked example

A foundation application defines a Customer data type and a case type. A regional application built on it needs a different approval threshold. Create a circumstanced rule in the regional ruleset rather than editing the foundation. The reasoning: rule resolution selects the more specific circumstance at run time, the foundation stays upgradeable, and the regional difference is visible in one place.

Traps

Editing rules in a built-on application; copying rules instead of building on or circumstancing; ignoring ruleset versions during deployment; skipping unit tests because the UI "looks right"; letting class structure mirror the org chart rather than reuse.