PEGACPDC24V1 practice question 21 of 35

What are the main types of change requests in customer engagement projects?

Full set: 350 questions
Answer options
A: Proactive, reactive, and adaptive
B: Emergency, standard, and urgent Correct answer
C: Predictive, adaptive, and automated
D: Manual and automated
Correct Answer:
B. Emergency, standard, and urgent
Explanation

In the context of managing enterprise-level customer engagement projects, change requests are typically categorized based on their urgency and impact, aligning with established IT Service Management (ITSM) frameworks like ITIL. Standard Changes: These are low-risk, pre-authorized changes that are common and follow a defined, approved process (e.g., updating proposition content). Emergency Changes: These are required to fix a critical incident or restore service immediately (e.g., a hotfix for a production outage). Urgent/Normal Changes: These are non-emergency changes that must be reviewed, approved, and scheduled through a formal change control process. This classification ensures proper governance, risk management, and stability for the live application.

Why Incorrect

A. Proactive, reactive, and adaptive: These terms describe strategic approaches or project management styles, not the formal classification of individual change requests.
C. Predictive, adaptive, and automated: This option incorrectly mixes project management methodologies (predictive, adaptive) with an implementation method (automated).
D. Manual and automated: This describes the method of implementing a change, not the type of request or its associated governance process.

References

1. Pega Academy, "Business Agility in 1:1 Customer Engagement" Mission: The "The change request process" module details how business users initiate changes to Next-Best-Action strategies. The process implicitly categorizes requests based on complexity and urgency, which aligns with the Standard, Urgent, and Emergency framework for governance and deployment.

2. Pega Documentation, "Pega Express delivery approach," Section: The change control process: "Any change to the scope defined in the project backlog must go through a formal change control process... The change control process provides a mechanism for capturing, evaluating, approving or rejecting, and tracking all changes." This formal evaluation process is the foundation for categorizing changes by risk and urgency (Standard, Urgent, Emergency).

3. Pega Documentation, "Managing your release process with Deployment Manager": The documentation describes different types of application pipelines, such as a 'Hotfix' pipeline for immediate production fixes. This directly corresponds to the handling of an 'Emergency' change request, separate from standard development release cycles.

Scroll to Top