Quick Answer
The answer is stakeholder feedback, along with regulatory changes and scope errors, as three of the most common causes of project change requests. Stakeholder feedback drives changes because evolving needs, new insights, or overlooked requirements from clients or sponsors often surface after the project baseline is set, forcing adjustments to deliverables or priorities. Regulatory changes, such as new GDPR or HIPAA compliance mandates, are equally common because external laws can require immediate scope modifications to avoid legal penalties. On the PMP exam, this concept tests your understanding of the integrated change control process and how change requests originate from both internal and external sources. A common trap is assuming only technical issues trigger changes, but the exam emphasizes that stakeholder input and legal shifts are frequent, legitimate triggers. Memory tip: think “SRS” for Stakeholder feedback, Regulatory shifts, and Scope creep—the three silent disruptors that always demand a formal change request.
This PMP practice question tests your understanding of process — managing technical aspects. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which THREE of the following are common causes of project change requests?
Regulatory changes
New regulations may require changes to project deliverables.
Team member vacation
Why wrong: Vacations are planned and do not typically result in change requests.
Budget surplus
Why wrong: A surplus may allow changes but is not a direct cause.
Scope creep
Uncontrolled additions to scope often trigger change requests.
Stakeholder feedback
Stakeholder input often leads to change requests.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Regulatory changes
Regulatory changes are a common cause of project change requests because new laws or compliance requirements (e.g., GDPR, HIPAA, or PCI DSS) can mandate modifications to project scope, deliverables, or processes. These external mandates often require immediate adjustments to avoid legal penalties, making them a frequent trigger for formal change requests in technology projects.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Regulatory changes
Why this is correct
New regulations may require changes to project deliverables.
Related concept
Read the scenario before looking for a memorised answer.
Team member vacation
Why it's wrong here
Vacations are planned and do not typically result in change requests.
Budget surplus
Why it's wrong here
A surplus may allow changes but is not a direct cause.
Scope creep
Why this is correct
Uncontrolled additions to scope often trigger change requests.
Related concept
Read the scenario before looking for a memorised answer.
Stakeholder feedback
Why this is correct
Stakeholder input often leads to change requests.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates may confuse operational issues like team member vacation or budget surplus with legitimate triggers for formal change requests, but the PMP exam emphasizes that change requests must stem from external or internal factors that alter the project baseline, not routine resource or financial adjustments.
Detailed technical explanation
In project management, change requests are formal proposals to modify baselines (scope, schedule, cost). Regulatory changes often require updates to system architecture or data handling procedures, such as implementing encryption standards (e.g., AES-256) or access controls (e.g., RBAC) to meet new compliance rules. Scope creep, another common cause, occurs when uncontrolled additions to requirements are made without formal change control, often due to vague initial specifications or evolving stakeholder needs.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the PMP exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Process — Managing Technical Aspects — study guide chapter
Learn the concepts, then practise the questions
Process — Managing Technical Aspects practice questions
Targeted practice on this topic area only
All PMP questions
892 questions across all exam domains
Project Management Professional PMP study guide
Full concept coverage aligned to exam objectives
PMP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PMP questions linked to People — Leading Projects.
Practise PMP questions linked to Process — Managing Technical Aspects.
Practise PMP questions linked to Business Environment — Strategy and Value.
Practise PMP questions linked to Business Environment: strategy and project benefits.
Practise PMP questions linked to PMP fundamentals.
Practise PMP questions linked to PMP scenario.
Practise PMP questions linked to PMP troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Process — Managing Technical Aspects — This question tests Process — Managing Technical Aspects — Read the scenario before looking for a memorised answer..
The correct answer is: Regulatory changes — Regulatory changes are a common cause of project change requests because new laws or compliance requirements (e.g., GDPR, HIPAA, or PCI DSS) can mandate modifications to project scope, deliverables, or processes. These external mandates often require immediate adjustments to avoid legal penalties, making them a frequent trigger for formal change requests in technology projects.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 11, 2026
This PMP practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.