POPM PI Planning Preparation Practice Question
Exhibit
{
"System_Architect_Feedback": {
"Enabler_Status": "Critical_Missing",
"Impact": "High_Risk_To_Delivery"
}
}Refer to the exhibit. What must the Product Manager do immediately following this feedback?
⚠ Common exam trap
Candidates often choose to 'continue with feature development' first. They undervalue the architectural runway, failing to realize that missing enablers will eventually block all business feature delivery.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Work with the Architect to prioritize the enabler in the backlog.
When the System Architect flags a critical missing enabler, the PM must treat it as a top-priority item. Ignoring technical enablers leads to failed features and late delivery. The PM must re-prioritize the backlog to include this enabler, ensuring the architectural runway is secured. This alignment between business features and technical enablers is vital for the ART to deliver stable, high-quality solutions throughout the upcoming PI without systemic blockers.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ask the teams to ignore the enabler until the next PI.
Why it's wrong here
Ignoring a critical enabler is a significant risk that could render current features unusable. The PM must address the enabler now, as it is a prerequisite for technical success. Pushing it to the next PI could lead to compounding technical debt and ultimately failure to deliver.
- ✓
Work with the Architect to prioritize the enabler in the backlog.
Why this is correct
Collaborating with the Architect to prioritize the enabler is the correct path. It demonstrates respect for the technical foundation of the system and ensures that the ART has the necessary infrastructure to deliver the planned features successfully, minimizing risks and preventing major technical bottlenecks.
- ✗
Tell the teams to find a workaround that avoids the enabler.
Why it's wrong here
Workarounds often result in temporary fixes that increase technical debt and reduce long-term agility. The PM should address the root cause, which is the missing enabler. Finding a workaround is a short-term, risky solution that undermines the quality and sustainability of the system over time.
- ✗
Submit a change request to the Portfolio management office.
Why it's wrong here
Internal ART technical enablers usually do not require Portfolio-level approval. This is an operational decision within the ART. Escalating to the PMO creates unnecessary bureaucracy and delays, whereas the PM and Architect have the authority to manage the Program Backlog to ensure successful delivery.
About these practice questions
This POPM question is part of Courseiva's 336-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This POPM practice question is part of Courseiva's free Scaled Agile 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 POPM exam.