PEGACPSA88V1-QUESTION practice question 12 of 15

Several Development teams work on different enhancements. The release date for each enhancement is uncertain. Which two options allow each team to keep its work separate? (Choose Two)

Full set: 82 questions
Answer options
A: Create a new ruleset version for each team. Correct answer
B: Set up a branch ruleset for each team Correct answer
C: Create a new application for each team
D: Create a production ruleset for each team.
Correct Answer:
A. Create a new ruleset version for each team.; B. Set up a branch ruleset for each team
Explanation

Pega Platform provides two primary mechanisms to manage parallel development and keep the work of different teams separate, especially when release timelines are uncertain.
1. Branch Rulesets (B): This is the recommended, modern approach for parallel development. Each team works in a dedicated "branch," which is an isolated copy of a ruleset. This allows teams to develop and test features independently without impacting the main application or other teams. When a feature is complete, the branch is merged back into the main rulesets.
2. Ruleset Versioning (A): Teams can also work on different minor or major versions of a ruleset. For example, one team could work on features for a future release in version 01-02-01, while another team works on a different set of features in version 01-03-01. This segregates the rule changes into different versioned containers, effectively keeping the work separate.

Why Incorrect

C. Create a new application for each team: This is an excessive and impractical approach for managing enhancements to a single application. It creates significant overhead and is intended for building entirely separate business solutions.
D. Create a production ruleset for each team: Production rulesets are specifically designed for rules delegated to business users for modification in a production environment, not for core application development by technical teams. ---

References

1. Pega Platform™ 8.8 Documentation, "Branching rulesets to support parallel development": This official document explicitly states, "To support parallel development among teams, you can use branched rulesets. A branch is a container for rulesets with rules that are undergoing rapid change and development." This directly supports option B as the primary method for parallel, isolated development.

2. Pega Platform™ 8.8 Documentation, "Copying a ruleset version": This document describes the process of creating new ruleset versions. It notes, "Create a new version of a ruleset to update your application as part of your development life cycle." While not its primary purpose, using different version streams (e.g., one team on 01-02-xx, another on 01-03-xx) is a valid strategy to segregate development efforts for different planned releases, thus supporting option A.

3. Pega Platform™ 8.8 Documentation, "Application development in branches": This guide details the branching workflow: "Branching helps you manage parallel development in a rule-based application. For example, a development team can create a branch to develop a new feature in an isolated environment without affecting the source application." This reinforces the correctness of option B.

Scroll to Top