Free AWS Solutions Architect Associate Practice Exam 2026 | 900+ Exam-Style Questions

Meet the affected assignees privately to reassure them the change is milestone-driven, then tell the wider team the work has been reassigned.

Ask the most experienced team member to absorb the task, and let the others know the allocation has changed to protect the milestone.

Reassign the tasks yourself based on skills and explain the rationale afterward, so the milestone is protected without debate.

Bring the team together, explain the milestone driver behind the reallocation, and work with them to redistribute the tasks in a way the affected members can support.

Promote engineer B instead, since the project manager is accountable for delivery and should have the final say on the team lead role.

Support engineer A in growing into the new role while keeping engineer B engaged and motivated on the team.

Coach engineer B to be ready to step in the moment engineer A struggles, so the transition is seamless when it fails.

Log the concern about engineer A as a project risk, then quietly prepare engineer B as the designated backup.

Ask the construction manager to meet the two team members directly and work it out among themselves.

Ask the two team members to be patient with the cultural differences, since everyone brings a different background.

Give the construction manager specific instructions on how to handle the two team members going forward.

Discuss the team members' concerns with the construction manager and work together on solutions to improve the working relationship.

Clear project work breakdown structure (WBS) and timeline

Resource management and conflict resolution plan

Risk management and issues resolution plan

Clear responsible, accountable, consult, and inform (RACI) matrix

Meet the sponsor to clarify the expectation, document the gap against the approved scope, and initiate a formal change request if the expansion is confirmed.

Assess the deliverable against the approved scope and, if it is a genuine gap, raise a change request while continuing the current work unchanged.

Acknowledge the sponsor's expectation and update the scope informally, noting the change in the next status report for visibility.

Begin planning the expansion now, since the sponsor's authority to approve the project also covers adjusting its scope.

Address the shutdown suggestion first, since it is the most extreme concern and the most likely to sway the other stakeholders.

Present the variances with context and commit to bringing a detailed corrective action plan to the next status meeting, with daily updates in between.

Acknowledge the variances, walk the group through the root cause analysis, and present the corrective action plan already in progress.

Ask each stakeholder to submit their concerns in writing so the project manager can prepare a thorough written response for the next meeting.

Keep it in the risk register and continue monitoring it as an active risk.

Close it in the risk register, since the identified risk response is now complete.

Escalate it straight to the change control board before recording it anywhere.

Move it to the issue log, because the uncertain event has now occurred and is a present problem to be managed.

Ensured that all defects identified during testing were resolved before implementation.

Ensured that all of the required tasks identified in the scope were completed successfully.

Ensured that all documentation was completed post implementation before closing the project.

Ensured that all the required approvals were received per the organizational procedures.

The overall project management plan, since every subsidiary plan ultimately rolls up into it.

The scope baseline, since the three new features expand the product scope.

The quality management plan, to incorporate the new specialized testing process the change introduces.

The requirements traceability matrix, to map the three new features back to their requirements.

Ask the product designer why the deviation was not caught during the design phase.

Log the deviations as low-priority items and monitor them, revisiting only if they escalate, to protect the strained budget.

Evaluate the recommended corrective actions and initiate the change request process with the stakeholders.

Ask the quality team to discard the current sample and retest with a fresh one.

Apply earned value techniques that compare planned to actual value delivered at key checkpoints.

Develop a work breakdown structure and perform activity-based cost estimating for the solution.

Consult colleagues at other companies and use their historical information to predict the final cost.

Perform scenario planning across the candidate solution designs and feed the estimates into the next budgeting cycle.

Risk log

Backlog

Change log

Issue log

A Gantt chart, which lays out tasks as horizontal bars along a timeline and shows their durations and dependencies.

A risk register, which lists identified risks along with their owners and planned responses.

A responsibility assignment matrix (RACI), which maps who is responsible and accountable for each activity.

A stakeholder register, which records the people affected by the project and their interests.

Raise a change request and get formal approval from the project owner before revising the design.

Inform the client of the problem and follow the change request process to revise the approved design.

Amend the design specifications and pass them to the development team to reprogram.

Run a proof of concept first to confirm the revised design has no problems before doing anything else.

Prepared and negotiated a follow-on contract with the consultancy for the remaining 14 months at the time of the first signature.

Included the client in every negotiation phase to secure their advance approval before signing the contract.

Agreed with the client up front on how often the status of procurement activities would be reported.

Developed a detailed, phased procurement management plan covering all activities through project end and had the client approve it.

Remove the deliverables from the iteration backlog.

Update the issue log and escalate it to the project sponsor.

Meet with the stakeholders and request a solution.

Ask the team to work on the unblocked deliverables.

Use the lower-cost supplier as directed to maximize the internal profit margin.

Analyze the impact of the supplier change on the client's expectations and facilitate an alignment discussion before proceeding.

Submit a change request to increase the budget so the original high-end fixtures can still be purchased.

Inform the external client that internal procurement policy requires the change in fixture materials.

Crash the project schedule to release the product before the competitor captures more of the market.

Shield the team from the market news so they stay focused on delivering the current baseline.

Facilitate a review of the project vision with stakeholders to confirm it still fits the new market reality.

Terminate the project immediately to prevent the organization from wasting further resources.

Ask the vendor to provide their own relationship-history summary as an independent reference for the incoming project manager.

Write a comprehensive vendor relationship summary and hand it to the incoming project manager during the final week of overlap.

Let the incoming project manager build the vendor relationship from scratch to avoid anchoring them to the outgoing approach.

Establish a structured knowledge transfer plan — relationship history, shadowing, formal introductions, and a transition meeting — before the rotation.