Agile success depends heavily on collaboration, shared understanding, and constructive stakeholder participation. When a stakeholder disrupts progress due to unfamiliarity with agile, the project manager (or agile leader) should first address the behavior directly and provide feedback (D). This enables quick course correction through coaching: clarifying agile roles, explaining how iterations deliver value, setting expectations for participation, and establishing respectful working agreements. Early direct engagement often resolves misunderstandings and reduces future disruptions without escalation. Reporting the stakeholder for replacement (A) is premature and damages relationships; it also may be unrealistic if the stakeholder has legitimate authority. Logging the attitude as a risk and continuing (B) avoids the underlying people issue and can compound delays and conflict. Switching to predictive (C) contradicts the sponsor’s direction and does not solve the root cause—lack of agile understanding. Addressing the stakeholder early supports change management, strengthens trust, and improves team flow, while maintaining alignment with the organization’s agile transition objectives.

==========

Large equipment purchases must follow the organization’s procurement and authorization controls. The project manager should align the purchasing approach to governance by agreeing on an approval and escalation method (A) that defines who can authorize what amounts, how exceptions are handled, and how long approvals typically take. This ensures compliance, avoids delays, and supports predictable planning for procurement lead times. Replacing equipment to bypass approvals (B) is poor governance and may compromise requirements, quality, or lifecycle cost—procurement decisions must be driven by business need and specifications, not approval avoidance. Requesting blanket approval authority for the PM (C) often conflicts with segregation-of-duties controls and is unlikely to be granted. Having the sponsor approve everything (D) can create bottlenecks and also may not match governance rules (finance/procurement committees may still be required). Establishing a clear approval/escalation path integrates procurement management with schedule and cost control, reduces risk of noncompliance, and supports effective stakeholder and vendor management.

==========

In agile, the team should focus on completing the sprint goal and finishing the committed work before pulling in future sprint items. If a team member has capacity and can help with work already selected for the sprint, the best action is to reassign them to other tasks in the current sprint (C). This supports flow and increases the likelihood that all committed backlog items meet the Definition of Done, reducing spillover and improving predictability. Validating completeness (A) is important, but it is not the best use of a skilled person’s capacity if there is still unfinished sprint work elsewhere; quality validation should be integrated into DoD and team practices. Increasing velocity (B) is not something a PM “does” directly; velocity is an empirical measure, and artificially pushing it can harm quality. Starting next sprint tasks early (D) risks undermining sprint planning, creating partial work, and distracting from the sprint goal. Helping finish current sprint items maximizes value delivery and maintains agile discipline.

==========

When a previously unidentified stakeholder appears late, the first priority is to assess who they are and how they can affect (or be affected by) the project. Stakeholder analysis determines their interest, influence, expectations, urgency, and potential impact on acceptance, deployment, or benefits realization—especially critical close to completion when changes are expensive. By analyzing the stakeholder’s interest and impact first, the project manager can choose the right engagement approach: what information to provide, how to involve them (if at all), and whether their needs require action through change control. Immediately providing “full details” and soliciting input can trigger last-minute scope changes without understanding authority or relevance. Escalating to the sponsor might be necessary later, but doing so before analysis risks unnecessary conflict or misalignment. Simply sharing a summary and closing the project could jeopardize acceptance or operational readiness if the stakeholder influences sign-off, compliance, or adoption. Proper stakeholder analysis supports a focused engagement plan, minimizes disruption, and protects the project’s closure and transition outcomes.

==========

When a project faces an unplanned cost need (hiring additional resources) and there is no approved additional budget, the project manager should first evaluate available reserves that are already authorized within the project’s overall funding structure. Management reserves (C) are typically controlled by management and may be used for unforeseen work that is within project scope but not covered by contingency reserves. The PM should initiate the process to access those reserves according to governance, enabling timely action to protect a mandatory deadline. Asking the sponsor for more funds (A) may ultimately be required, but it is not the first step if reserves exist and can be used within established authority paths. Introducing a change request (B) can be appropriate if the action changes baselines or exceeds thresholds; however, the immediate “first” funding source check is reserves. Updating baselines to accommodate delay (D) does not address the mandatory deadline and is not funding. Properly applying reserves supports schedule recovery while remaining aligned with formal cost control and escalation procedures.

==========

This question fits the Business Environment domain because it is about aligning delivery with business value and market needs. PMI’s agile and value-delivery guidance emphasizes delivering the highest business value quickly and using incremental delivery so usable value can reach stakeholders early and be adapted based on feedback. In this scenario, the client wants to jump-start the market with the informal sector traders, so the best approach is to structure delivery in phases and begin with the segment that creates immediate business impact.

Option B may increase activity, but parallel execution does not automatically maximize early value. Option C follows the schedule mechanically without responding to the stated business priority. Option D uses agile language, but backlog conversion alone does not answer the strategic need to sequence delivery for fastest market benefit. PMP-style thinking favors tailoring the delivery approach to realize value as early as practical. Therefore, a phased approach starting with the informal sector is the strongest answer.

This question belongs to the Process domain because it focuses on managing project issues, procurement performance, and recovery actions. PMI’s PMP Examination Content Outline includes tasks such as assessing and managing risks, engaging stakeholders, and taking action to keep the project aligned with delivery objectives. In this case, the core problem is an active supplier delay that is already affecting schedule performance. The best immediate action is to engage the vendor directly and establish a recovery plan to bring delivery back on track. That response is proactive, solution-oriented, and consistent with contract and supplier management practices.

Option B may provide useful background, but it does not directly resolve the live issue. Option C jumps too quickly to a punitive approach; penalties may exist, but PMP-style thinking generally favors first working collaboratively to correct performance before escalating contract remedies. Option D is the weakest choice because waiting worsens the schedule risk. The strongest answer is to work with the vendor now, clarify commitments, and define concrete corrective actions to protect the project deadline.