487 questions total · 7pages · All types, answers revealed
Which THREE of the following are recognized process groups in the PMBOK Guide? (Choose three)
A standard process group.
Why this answer
Options C, D, and E are correct. The PMBOK Guide defines five process groups: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. Analyzing and Reviewing are not recognized process groups.
A project manager is assigned to a cross-functional initiative in a matrix organization. The team members report to both the project manager and their functional managers. What is the primary challenge the project manager would face?
Dual reporting creates resource contention.
Why this answer
In a matrix organization, team members have dual reporting lines, leading to competing priorities. Option A is wrong because budget authority varies. Option B is wrong because communication is not necessarily slower.
Option D is wrong because resource availability depends on functional managers.
Which THREE of the following are key components of a work breakdown structure (WBS) dictionary?
Milestones associated with the work package are included.
Why this answer
The WBS dictionary provides detailed information about each WBS component. Key components include a description of the work package (C), the responsible organization or person (E), and associated schedule milestones (A). Option B is incorrect because the project charter is a separate high-level document authorizing the project, not a component of the WBS dictionary.
Option D is incorrect because network diagrams are used for activity sequencing, not typically included in the WBS dictionary.
Refer to the exhibit. A business analyst is analyzing system failures during user acceptance testing. The error log indicates a database connection problem. Which root cause should the analyst investigate first?
Communications link failure is commonly caused by network problems.
Why this answer
The 'Communications link failure' error typically indicates a network issue between the application and database server, so network connectivity should be checked first.
Which THREE of the following are typically included in a business case?
Alternatives analysis compares options.
Why this answer
A business case includes the problem statement, cost-benefit analysis, and alternatives analysis to justify the project. Risk register and stakeholder list are separate documents that inform but are not core parts of the business case.
A project manager is developing the project schedule for a construction project. The team has identified that the foundation work must be completed before the framing can begin. Which type of dependency does this represent?
Mandatory dependencies are inherent in the nature of the work, such as physical or legal requirements.
Why this answer
The dependency between foundation work and framing is a mandatory dependency because it is physically required that the foundation be completed before framing can begin. In construction, this is a hard logic constraint inherent in the nature of the work, not a preference or external factor. Mandatory dependencies are often referred to as 'hard logic' and are typically based on contractual requirements or physical limitations.
Exam trap
The trap here is that candidates often confuse 'mandatory dependency' with 'discretionary dependency' because they think all logical sequences are discretionary, but mandatory dependencies are those dictated by the nature of the work itself, not by preference or best practice.
How to eliminate wrong answers
Option B (Lead) is wrong because a lead is a technique used to accelerate the successor activity by overlapping it with the predecessor, not a type of dependency. Option C (Discretionary dependency) is wrong because this dependency is not based on best practices or preferences; it is a physical necessity. Option D (External dependency) is wrong because the dependency is between two internal project activities (foundation and framing), not involving a factor outside the project.
A company is considering implementing a new customer relationship management (CRM) system. The business analyst conducts a needs assessment to identify business gaps and opportunities. What is the primary output of a needs assessment?
The business case is the primary output of needs assessment.
Why this answer
The primary output of a needs assessment is the business case, which justifies the investment based on identified gaps and opportunities. Requirements documentation, stakeholder register, and project charter are produced later in the project lifecycle.
A project manager is leading a software development project. During the planning phase, the team identifies a significant risk that a key third-party API may be deprecated before the project completes. The project sponsor asks for a risk response strategy. Which strategy should the project manager recommend to best address this risk?
Mitigation reduces the probability or impact; a workaround proactively addresses the potential issue.
Why this answer
Developing a workaround using an alternative API or building a fallback mechanism directly reduces the probability and/or impact of the API deprecation risk. This is a classic risk mitigation strategy that proactively ensures the project can continue even if the third-party API becomes unavailable, which is a common technical risk in software projects.
Exam trap
The trap here is that candidates may confuse 'acceptance' (Option A) with a valid passive strategy, but for a significant technical risk like API deprecation, proactive mitigation is the standard recommended approach in project management.
How to eliminate wrong answers
Option A is wrong because simply accepting the risk without a contingency plan is passive and does not address the significant impact of a key API being deprecated, which could halt development. Option B is wrong because purchasing insurance is not a viable or standard practice for technical API deprecation risks; insurance typically covers financial loss from physical assets or liability, not software dependency failures. Option D is wrong because enhancing the risk (increasing exposure to it) is the opposite of what is needed; it would amplify the negative impact if the API is deprecated, making the project more vulnerable.
Which THREE are techniques used for estimating activity durations?
Uses optimistic, pessimistic, and most likely estimates to determine duration.
Why this answer
The correct techniques for estimating activity durations are three-point estimating (A), parametric estimating (B), and analogous estimating (E). Three-point estimating uses optimistic, pessimistic, and most likely estimates. Parametric estimating uses a statistical relationship between historical data and other variables.
Analogous estimating uses values from previous similar projects. Reserve analysis (C) is used for contingency reserves, not for estimating durations. Monte Carlo simulation (D) is a risk analysis technique.
A Scrum team has five members. During a Sprint, two members are pulled to work on a critical production issue. The remaining three are unable to complete all committed stories. What should the Scrum Master do?
The Development Team self-organizes to handle changes and can renegotiate scope.
Why this answer
In Scrum, the Development Team is self-organizing and responsible for managing its own work within the Sprint. When two members are pulled to a critical production issue, the remaining three team members have the authority to decide how to adjust the Sprint Backlog to reflect their reduced capacity. The Scrum Master should facilitate this self-management rather than imposing a solution, as option C respects the team's autonomy and the Scrum principle of self-organization.
Exam trap
PMI often tests the misconception that the Scrum Master or Product Owner should directly manage the Sprint Backlog, when in fact the Development Team has exclusive authority over it during the Sprint.
How to eliminate wrong answers
Option A is wrong because extending the Sprint violates the time-boxed nature of Sprints in Scrum, which are fixed-duration events (typically 2-4 weeks) and should not be extended for scope changes. Option B is wrong because asking the Product Owner to remove work from the Sprint Backlog bypasses the Development Team's authority to manage the Sprint Backlog; the Product Owner can only reorder the Product Backlog, not directly modify the Sprint Backlog during the Sprint. Option D is wrong because removing the least valuable stories is a decision that should be made by the Development Team, not unilaterally by the Scrum Master, and it assumes a value judgment that may not align with the team's priorities.
Based on the exhibit, what is the critical path duration?
The critical path is A-B-D-E-G with 15 days.
Why this answer
The critical path is the longest path through the network. Path A-B-D-E-G = 3+4+5+2+1 = 15 days. Path A-C-D-F-G = 3+2+5+3+1 = 14 days.
Therefore, the critical path duration is 15 days. Options B, C, and D are incorrect because they do not represent the longest path duration.
A project manager is leading a software development project using a predictive plan-based methodology. The project is at 70% completion and the team has discovered a significant defect in a module that was completed two months ago. The defect was not identified during testing because the test cases were incomplete. The project schedule has a buffer of 5 days, and the defect is expected to take 10 days to fix. The project manager needs to determine the best course of action. Which of the following should the project manager do?
Following the change control process is the appropriate action to assess and manage the impact of the defect fix.
Why this answer
In a predictive project, changes should be managed through the formal change control process. This ensures that the impact on scope, schedule, and cost is evaluated before taking action. Simply assigning the fix without a change request bypasses controls, removing the module changes scope without analysis, and requesting additional resources without a plan is premature.
You are managing a software upgrade project for a financial institution. The project involves upgrading the core banking system to a new version. During user acceptance testing (UAT), the testers find that the new system does not handle certain legacy data formats correctly, causing errors. The project schedule has no buffer left, and the go-live date is fixed due to regulatory compliance. The team estimates it will take two weeks to fix the issue, but the go-live is in one week. The project manager has already used the contingency reserve for other issues. What should the project manager do next?
The project manager should explore alternatives and escalate to the sponsor for a decision if the schedule cannot be met.
Why this answer
The project manager must first evaluate feasible alternatives (like a partial fix or workaround) to meet the fixed go-live date, given that the contingency reserve is exhausted and the schedule has no buffer. Escalating to the sponsor is appropriate when the issue impacts regulatory compliance and requires a decision beyond the PM's authority. This aligns with the CAPM principle of managing stakeholder expectations and seeking sponsor guidance when constraints force trade-offs.
Exam trap
The trap here is that candidates assume the management reserve is always the next step for budget issues, but the PM must first exhaust internal options (like workarounds) and escalate to the sponsor before tapping into reserves, especially when the schedule is fixed and compliance is at stake.
How to eliminate wrong answers
Option A is wrong because ignoring the issue that causes errors in legacy data formats could lead to regulatory non-compliance and operational failures, violating the project's quality and compliance requirements. Option B is wrong because requesting additional budget from the management reserve is not the immediate next step; the PM should first explore internal workarounds or partial fixes before seeking external resources, and management reserve requires sponsor approval. Option D is wrong because unilaterally delaying the go-live without first evaluating alternatives or escalating to the sponsor disregards the fixed regulatory deadline and the PM's responsibility to seek approval for schedule changes.
A business analyst is prioritizing requirements using the Kano model. A feature that provides delight when present but causes dissatisfaction when absent is classified as:
One-dimensional: These cause satisfaction when present and dissatisfaction when absent, matching the description. Correct.
Why this answer
In the Kano model, a feature that causes dissatisfaction when absent cannot be attractive because attractive features do not cause dissatisfaction when absent. One-dimensional (performance) features cause satisfaction when present and dissatisfaction when absent, which matches the description ("delight" is often used loosely for satisfaction). Thus, the correct classification is One-dimensional.
Exam trap
Many candidates confuse one-dimensional features with attractive features. Attractive features delight but do not cause dissatisfaction when missing.
During project planning, the project manager wants to ensure that all work required to complete the project is identified. Which document is the primary output of the process that defines and controls what is included in the project?
The scope baseline is the approved version of the scope statement, WBS, and WBS dictionary.
Why this answer
The scope baseline is the primary output of the 'Define Scope' and 'Create WBS' processes, and it formally defines and controls what is included in the project. It consists of the project scope statement, the WBS, and the WBS dictionary, providing a comprehensive reference for scope management. By establishing the scope baseline, the project manager ensures that all required work is identified and any changes must go through formal change control.
Exam trap
The trap here is that candidates often confuse the project scope statement (a component) with the scope baseline (the complete set), or they mistakenly think the WBS alone is the primary output, when the CAPM exam expects the scope baseline as the integrated deliverable that defines and controls scope.
How to eliminate wrong answers
Option A is wrong because the scope management plan describes how scope will be defined, validated, and controlled, but it does not itself identify or define the specific work included in the project. Option B is wrong because the project scope statement is a component of the scope baseline, not the primary output that defines and controls what is included; the scope baseline as a whole is the authoritative document. Option D is wrong because the Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work, but it is only one part of the scope baseline; the baseline also includes the project scope statement and WBS dictionary, making the scope baseline the complete output.
Refer to the exhibit. An Agile team uses Git for source control. Based on the git log, which integration strategy is the team using to incorporate changes from feature branches?
The merge commit shows that changes from feature-x were merged into main.
Why this answer
The presence of a merge commit (a1b2c3d) with two parents indicates a merge strategy. Rebase would show a linear history, squash would show a single commit, and cherry-pick would not show a merge commit.
Which THREE of the following are components of the project charter?
The charter includes the business case and project purpose.
Why this answer
The project charter formally authorizes the project and the project manager. It includes the project purpose or justification (A) to establish the business need, a summary budget (B) to provide high-level financial constraints, and high-level risks (D) to identify potential uncertainties early. These are key components per the PMBOK Guide.
Exam trap
PMI often tests the distinction between high-level charter content and detailed planning outputs, so candidates mistakenly select detailed schedule or WBS because they confuse the Initiating and Planning process groups.
A project manager needs to decompose the project scope into smaller, more manageable components to provide a framework for detailed planning. Which technique should the project manager use?
The WBS breaks down the project scope into work packages for detailed planning.
Why this answer
The Work Breakdown Structure (WBS) is the tool used to decompose scope into work packages. Option A is wrong because the RACI matrix is for responsibility assignment, not decomposition. Option B is wrong because the Critical Path Method (CPM) is for schedule analysis, not decomposition.
Option D is wrong because the Gantt chart is for scheduling, not decomposition.
A project team is experiencing frequent changes in requirements. The project manager wants to minimize disruptions. Which approach is best to manage changes effectively?
A formal process ensures changes are reviewed and approved before implementation.
Why this answer
A formal change control board (CCB) and a documented change control process provide a structured, consistent method for evaluating, approving, and implementing changes. This minimizes disruptions by ensuring that only approved, impact-assessed changes are introduced, preventing ad-hoc modifications that can destabilize the project scope, schedule, and budget.
Exam trap
The trap here is that candidates often choose 'freeze requirements' (Option A) thinking it prevents disruption, but the CAPM exam tests the understanding that a formal change control process—not rigidity—is the correct way to manage changes in an adaptive environment.
How to eliminate wrong answers
Option A is wrong because freezing requirements after initial sign-off is unrealistic in dynamic environments; it ignores the need for adaptive change management and can lead to a product that no longer meets stakeholder needs. Option C is wrong because letting the team implement changes as they come introduces uncontrolled scope creep, bypasses impact analysis, and often leads to rework, budget overruns, and schedule delays. Option D is wrong because communicating changes to stakeholders only after implementation violates the principle of proactive stakeholder engagement and can result in misalignment, rework, and loss of trust; changes should be reviewed and approved before implementation.
A startup is developing a mobile application with rapidly changing requirements. The team needs to deliver value quickly and adapt to user feedback. Which business analysis approach is most appropriate?
Agile supports iterative delivery and quick adaptation.
Why this answer
Agile is designed for rapid iteration and adaptability to changing requirements.
A project manager is reviewing the project's cost performance. The actual cost (AC) is $50,000, the earned value (EV) is $45,000, and the planned value (PV) is $60,000. What is the cost variance (CV)?
CV = EV - AC = -$5,000.
Why this answer
Cost variance (CV) is calculated as EV minus AC. Here, EV = $45,000 and AC = $50,000, so CV = $45,000 - $50,000 = -$5,000. A negative CV indicates the project is over budget, which matches option C.
Exam trap
The trap here is confusing cost variance (CV = EV - AC) with schedule variance (SV = EV - PV) or incorrectly subtracting AC from EV, leading candidates to pick $5,000 or -$15,000.
How to eliminate wrong answers
Option A is wrong because $5,000 would be the result of subtracting EV from AC (AC - EV = $5,000), but the correct formula is EV - AC. Option B is wrong because -$15,000 results from subtracting PV from AC (AC - PV = -$10,000) or confusing CV with schedule variance (SV = EV - PV = -$15,000). Option D is wrong because $10,000 is the result of subtracting AC from PV (PV - AC = $10,000), which is not a standard earned value management metric.
During project execution, you notice that a key stakeholder, the head of the legal department, has been disengaged from project reviews and has not responded to your emails requesting input on a regulatory compliance issue. The project is at risk of missing a legal requirement that could result in fines. You have classified this stakeholder as having high power and high interest. According to stakeholder engagement best practices, what should you do first?
Direct communication is best to re-engage a powerful, interested stakeholder.
Why this answer
For a stakeholder with high power and high interest, proactive engagement is key. A face-to-face meeting (C) is the most effective first step to directly address disengagement, understand their concerns, and re-establish communication. Option A escalates prematurely without attempting direct engagement first, Option B ignores the risk and the stakeholder's input, and Option D is too indirect and may further alienate the stakeholder.
Which TWO statements accurately describe the role of a business analyst in requirements management?
Aligning requirements to business goals is a key BA responsibility.
Why this answer
The business analyst (BA) is responsible for ensuring that each requirement directly supports the stated business objectives and strategic goals. This alignment is a core function of requirements management within the BABOK framework, as it prevents scope creep and ensures that delivered features provide measurable business value.
Exam trap
PMI often tests the distinction between the BA's role in eliciting and managing requirements versus the authority to approve or design technical solutions, leading candidates to incorrectly select options that conflate these responsibilities.
Refer to the exhibit. Which critical element is missing from this business case?
Alternatives analysis is essential to demonstrate that other options were evaluated.
Why this answer
The business case is missing a comparison of alternatives considered. A business case must justify why the selected approach is the best option, which requires evaluating at least one alternative (e.g., build vs. buy, different technical solutions). Without this, stakeholders cannot assess whether the recommended solution is optimal or cost-effective.
Exam trap
PMI often tests the misconception that a business case is just a high-level summary, but PMI requires it to include alternatives considered to demonstrate objective decision-making.
How to eliminate wrong answers
Option A is wrong because the project sponsor is typically identified later in the project charter, not as a required element of the business case; the business case focuses on justification, not governance roles. Option B is wrong because a detailed schedule belongs to the project management plan, not the business case; the business case only needs high-level timeframes or milestones. Option D is wrong because a risk mitigation plan is part of risk management planning, not the business case; the business case may mention key risks but does not require a full mitigation plan.
You are a project manager in a projectized organization. The project is nearing completion, but a key stakeholder has introduced several new requirements that were not in the original scope. The stakeholder insists these are critical for user acceptance. The project is already behind schedule and over budget. The change control board (CCB) has denied all previous change requests due to time and cost constraints. What is the best course of action?
Following the established process ensures decisions are made with full impact analysis.
Why this answer
The project manager must follow the established change control process. Even though the CCB has denied previous requests, it is still the proper authority to evaluate and decide on new change requests. Submitting a formal change request ensures the stakeholder's requirements are documented and evaluated against project constraints, while also protecting the project from unauthorized scope creep.
Option A bypasses the CCB, option B is premature without a formal request, and option C may be seen as dismissive and does not utilize the formal process.
During the planning phase of a predictive project, the project manager wants to define the project scope more precisely. Which process should be used to develop a detailed description of the project and product?
Correct: This process produces the project scope statement.
Why this answer
Define Scope is the process of developing a detailed project scope statement that describes the project and product boundaries.
During project execution, a key stakeholder requests a change that will increase the project scope. The project manager evaluates the impact and determines it will require additional budget and time. What is the first step the project manager should take?
Formal change requests are submitted to the CCB for evaluation and decision.
Why this answer
In predictive (waterfall) project management, any change that impacts scope, budget, or schedule must follow the formal integrated change control process. The project manager's first step after evaluating the impact is to submit a change request to the change control board (CCB) for approval or rejection. This ensures that all changes are documented, assessed for risks, and aligned with the project baseline before implementation.
Exam trap
PMI often tests the misconception that a key stakeholder's request should be automatically approved or that the project manager can make unilateral decisions on scope changes, when in fact the formal change control process must always be followed regardless of stakeholder importance.
How to eliminate wrong answers
Option A is wrong because rejecting the change outright without following the formal change control process bypasses the CCB's authority and ignores the stakeholder's legitimate request, which may have business value. Option C is wrong because implementing the change before obtaining formal approval violates the change control process and can lead to uncontrolled scope creep, budget overruns, and schedule delays. Option D is wrong because even a key stakeholder's request must go through the CCB for objective evaluation; approving it unilaterally undermines governance and can set a dangerous precedent.
Refer to the exhibit. What problem does this Kanban board reveal?
The WIP limit is 3, but there are 5 items in progress, causing overloading and potential bottlenecks.
Why this answer
The In Progress column shows 5 items while its WIP limit is set to 3, meaning the WIP limit is exceeded. This is the problem revealed by the Kanban board. Option B is incorrect: a nearly empty To Do column is not necessarily a problem; it may indicate that work is being pulled efficiently.
Option C is incorrect: having many items in Done is a positive sign of completed work, not a problem. Option D is incorrect: there is no indication of blocked items in the exhibit.
Refer to the exhibit. The team has a policy of not committing code that fails tests. What does this indicate about their process?
A failed build in CI should be addressed immediately; the presence of failures indicates a breakdown in the CI process.
Why this answer
The team's policy of not committing code that fails tests indicates that they may delay integration until tests pass, which can lead to large, infrequent integrations. This violates continuous integration (CI) principles, which require frequent merging of code changes, even if tests fail temporarily, to quickly detect and fix issues. Option A is not necessarily true; TDD involves writing tests before code, but the policy alone doesn't confirm TDD.
Option C is incorrect because the policy actually undermines proper CI. Option D is tangential and not indicated by the policy.
Which TWO statements correctly describe characteristics of the Kanban method?
WIP limits are a core Kanban practice to prevent overloading the team.
Why this answer
Kanban focuses on visualizing workflow, limiting work in progress (WIP), and managing flow. It does not prescribe fixed-length iterations (that's Scrum) nor require a dedicated team (teams can be shared).
A project manager is leading a team that includes members from different cultures. Communication misunderstandings are causing delays. Which action best addresses the root cause?
This directly addresses the root cause by tailoring communication to the team's needs.
Why this answer
Updating the communications management plan to include cultural considerations directly addresses the root cause of misunderstandings due to cultural differences. This proactive approach ensures that communication methods and styles are tailored to the team's diversity, improving clarity and reducing delays. Option A is too drastic, option B may not solve the underlying issue, and option D is a superficial fix that does not adapt the plan to cultural needs.
During requirements elicitation, the team discovers conflicting needs from two key stakeholders. The project manager asks the business analyst to use a prioritization technique that allows stakeholders to vote anonymously to reach consensus. Which technique should be used?
Correct: Delphi uses anonymous rounds to build consensus.
Why this answer
The Delphi Technique involves anonymous voting rounds to achieve consensus. MoSCoW is a prioritization but not anonymous, Multi-criteria Decision Analysis does not involve voting, and Voting (Roman Vote) is open.
Which TWO are core activities in a predictive plan-based methodology?
CPM is used in predictive scheduling.
Why this answer
In predictive plan-based methodology, detailed planning is done upfront, and changes are controlled. Decomposition of work into WBS and using CPM for scheduling are key activities. Rolling wave planning is more iterative, and retrospective reviews are from agile.
Adaptive budgeting is not typical.
A project manager is defining success criteria for a new software development project. Which of the following is the most objective and measurable success criterion?
Budget and schedule are objective, measurable constraints.
Why this answer
'completion within budget and schedule' is objective and measurable. Option A is subjective and hard to measure. Option C is subjective.
Option D is not a typical success criterion but a metric.
Which of the following is a key output of the needs assessment process?
Correct: Business case is the main output of needs assessment.
Why this answer
The needs assessment process results in a business case that defines the business need and recommended solution. Project Charter authorizes the project, Requirements Documentation details requirements, and Stakeholder Register lists stakeholders.
Which TWO of the following are responsibilities of the Product Owner in Scrum?
The PO orders backlog items to maximize value.
Why this answer
The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. This includes clearly expressing Product Backlog items and ordering them to best achieve goals and missions, which is prioritizing the Product Backlog. Managing the Product Backlog, which encompasses ensuring its visibility, transparency, and understanding, is also a core responsibility of the Product Owner as defined in the Scrum Guide.
Exam trap
PMI often tests the distinction between the Scrum Master's role (process facilitation, impediment removal, timebox enforcement) and the Product Owner's role (value maximization, backlog management, stakeholder alignment), leading candidates to confuse servant-leader duties with product-value responsibilities.
A project has a fixed deadline but flexible scope. The project manager receives a change request that would significantly increase scope. What should the project manager do first?
Impact analysis is the correct first step in change control.
Why this answer
According to the PMBOK Guide, the first step when a change request is received is to evaluate its impact on project constraints such as time, cost, quality, and scope. This impact analysis determines the feasibility and implications before any decision to approve or reject. Direct approval (C) or rejection (D) would be premature without analysis, and escalation to sponsor (A) is not the first step.
During a requirements elicitation meeting, stakeholders provide conflicting information about the desired functionality. What is the best course of action for the business analyst?
Facilitation helps clarify and resolve conflicting requirements.
Why this answer
The business analyst's primary role is to facilitate stakeholder collaboration and resolve conflicts through structured discussion, ensuring that requirements are accurate and agreed upon before development begins. This aligns with the BABOK guide's emphasis on using techniques like workshops or brainstorming to achieve consensus, which prevents costly rework later.
Exam trap
The trap here is that candidates often confuse the business analyst's role with that of a project manager or decision-maker, assuming escalation or authoritative resolution is appropriate, when in fact the BA must facilitate consensus among stakeholders.
How to eliminate wrong answers
Option A is wrong because documenting conflicting information without resolution leads to ambiguous requirements, causing development to proceed on unstable foundations and likely resulting in a product that fails to meet stakeholder needs. Option B is wrong because escalating to senior management bypasses the business analyst's responsibility to facilitate resolution at the stakeholder level, and senior management may lack the detailed domain knowledge to make informed decisions about functionality. Option D is wrong because asking the project manager to decide which stakeholder is correct undermines collaborative decision-making and may create resentment, as the project manager is not typically a domain expert in the specific functionality being discussed.
In project procurement management, what is the primary purpose of the procurement statement of work (SOW)?
The SOW specifies the scope of work for the seller.
Why this answer
The procurement statement of work (SOW) describes the work to be performed by the seller in sufficient detail. Option C is correct. Option A (manage vendor relationship) occurs after contract award and is part of contract administration.
Option B (evaluate vendor proposals) uses the SOW as an input, but the SOW itself is not for evaluation. Option D (define contract terms and conditions) is the purpose of the contract, not the SOW.
During stakeholder analysis, a business analyst identifies a key stakeholder who rarely speaks in meetings but provides detailed written feedback. Which engagement strategy is most appropriate?
Surveys allow the stakeholder to provide detailed feedback in writing, matching their preference.
Why this answer
The stakeholder prefers written communication and rarely speaks in meetings. Surveys or structured feedback forms align with this preference, allowing them to provide detailed input comfortably. Frequent one-on-one meetings (B) may be intimidating or uncomfortable for this stakeholder.
Continuing the current approach (C) fails to actively engage the stakeholder and may miss opportunities to gather their valuable input. Assigning a proxy (D) is unnecessary because the stakeholder is willing to provide input through written channels, and a proxy might not accurately represent their views.
Refer to the exhibit. What is the critical path duration?
The critical path (A-B-D-E) totals 16 days.
Why this answer
The critical path is the longest path through the network. Path A-B-D-E: 3+5+6+2=16 days. Path A-C-D-E: 3+4+6+2=15 days.
Therefore, the critical path duration is 16 days.
During project execution, a key stakeholder requests a significant change that will increase project scope. The project manager performs an impact analysis and determines that the change will delay the project by two weeks and increase costs by 10%. However, the change is critical for regulatory compliance. What should the project manager do first?
Formal change control process requires CCB review and decision.
Why this answer
The correct first step is to submit the change request to the change control board (CCB) because, in formal project management, any change that impacts scope, schedule, or cost must go through the integrated change control process. Even though the change is critical for regulatory compliance, the project manager cannot unilaterally approve or reject it; the CCB has the authority to evaluate the impact analysis and make the final decision.
Exam trap
The trap here is that candidates assume a critical compliance need automatically justifies bypassing the change control process, but the CAPM exam strictly tests adherence to formal procedures regardless of urgency.
How to eliminate wrong answers
Option A is wrong because the project manager does not have the authority to approve a change that increases scope, delays the schedule, and increases costs; approval must come from the CCB. Option B is wrong because rejecting the change outright ignores the regulatory compliance requirement, which could expose the organization to legal or financial penalties. Option D is wrong because implementing the change before approval violates the change control process and could lead to unauthorized scope creep, even if the change is later approved.
A business analyst is working on a project to implement a new inventory management system. The project charter has been approved, and the project manager has asked the analyst to begin requirements elicitation. The analyst notices that the business case did not include a clear problem statement or measurable objectives. Several stakeholders are uncertain about the project's purpose and expected outcomes. The project sponsor is eager to move forward. As the business analyst, what should you do first?
A solid business case provides direction and success criteria for all subsequent activities.
Why this answer
The business case provides the foundational justification for the project, including the problem statement and measurable objectives. Without these, requirements elicitation lacks clear direction, leading to scope creep and misaligned outcomes. The business analyst must first refine the business case with the sponsor and key stakeholders to ensure a shared understanding of the project's purpose and success criteria before proceeding with requirements activities.
Exam trap
The trap here is that candidates often jump to stakeholder analysis (Option C) as a first step, but the CAPM exam tests the sequence of business analysis planning: the business case must be validated before any requirements activities begin.
How to eliminate wrong answers
Option A is wrong because creating a requirements management plan is a process that follows after the business case is clarified; it does not address the missing problem statement and objectives. Option B is wrong because proceeding with requirements elicitation without clear objectives risks gathering irrelevant or conflicting requirements, wasting effort and increasing rework. Option C is wrong because stakeholder analysis identifies who to involve but does not directly resolve the missing problem statement and measurable objectives; the business case must be refined first to guide stakeholder engagement.
Which THREE techniques are commonly used for requirements elicitation?
Surveys can gather requirements from a large number of stakeholders.
Why this answer
Surveys, brainstorming, and interviews are all commonly used requirements elicitation techniques. Surveys efficiently gather input from a large number of stakeholders, brainstorming facilitates creative idea generation in a group setting, and interviews allow for in-depth exploration of individual stakeholder needs. SWOT analysis and Gantt charts are not elicitation techniques; they are used for strategic analysis and project scheduling, respectively.
Exam trap
PMI often tests the distinction between requirements elicitation techniques and project management tools, so candidates mistakenly select SWOT analysis or Gantt charts because they are familiar terms, even though they are not used for eliciting requirements.
Which of the following is a key component of a project scope baseline in predictive project management?
The Work Breakdown Structure (WBS) is a key component of the scope baseline as it defines the hierarchical decomposition of the project scope.
Why this answer
In predictive project management, the scope baseline consists of the approved project scope statement, Work Breakdown Structure (WBS), and WBS dictionary. The WBS is a hierarchical decomposition that breaks down the project work into manageable components, forming the foundation for scope management. Therefore, the WBS is a key component of the scope baseline, making option B correct.
Exam trap
Some may confuse scope baseline with other baselines, but the WBS is specifically part of scope baseline, not budget or schedule. The risk register is part of the risk management plan, not the scope baseline.
Refer to the exhibit. Which task has a dependency that requires the successor to start 2 days after the predecessor starts?
SS+2d indicates Start-to-Start with a 2-day lag.
Why this answer
A Start-to-Start (SS) dependency with a 2-day lag means the successor task starts 2 days after the predecessor starts. Task A has this dependency, matching the requirement. Task D (Option A) has a different dependency, Task B (Option C) has Finish-to-Start, and Task C (Option D) has Start-to-Start but without a lag.
Which is an effective way to prioritize user stories in a product backlog?
These factors ensure the most valuable items are delivered first.
Why this answer
Prioritizing user stories by business value, risk, and dependencies ensures that the most valuable and impactful features are delivered first. Option A (story points) indicates effort or size, not value. Option B (number of tasks) is irrelevant to priority.
Option C (creation date) is chronological and does not reflect importance.
A project manager is evaluating a project governance policy in a predictive plan-based methodology. The policy states: Deny changes to project requirements unless the requester is a member of the Change Control Board (CCB). What effect does this policy have?
Correct: The Deny applies when the source IP is not equal to 10.0.0.0/8.
Why this answer
The policy denies a change to project requirements when the requester is NOT a member of the CCB. Thus, it denies changes from anyone outside the CCB, meaning it effectively allows changes only from CCB members. However, the policy is denial-based, not allowance-based, so the correct description is that it denies changes from all except CCB members.
A project manager is creating the risk management plan. Which document should the project manager reference to identify the risk tolerance of stakeholders?
Correct. The project charter includes the risk appetite and high-level risks, which inform stakeholder risk tolerance.
Why this answer
The project charter contains high-level project risks and the risk appetite of the organization, which reflects stakeholders' risk tolerance. Therefore, it is the appropriate document to reference when creating the risk management plan.
Exam trap
The trap is that candidates often select the stakeholder management plan, but risk tolerance is actually documented in the project charter.
How to eliminate wrong answers
Option A is wrong because the project scope statement defines the project's deliverables, boundaries, and acceptance criteria, but it does not contain stakeholder-specific risk tolerance information. Option C is wrong because the project charter provides high-level risks and the project's purpose, but it lacks the detailed stakeholder analysis needed to determine individual risk tolerances. Option D is wrong because the risk register is an output of the risk management process, not an input to creating the risk management plan; it lists identified risks and responses, not stakeholder risk tolerance.
A BA is identifying stakeholders. Which TWO techniques are commonly used for stakeholder analysis?
Classifies stakeholders by power and interest.
Why this answer
Stakeholder analysis involves identifying and classifying stakeholders based on their influence, interest, power, and impact. The power/interest grid (Option D) and influence/impact grid (Option E) are two commonly used techniques for this classification. Option A (mind mapping) is a brainstorming technique, not specific to stakeholder analysis.
Option B (work breakdown structure) is for scope decomposition. Option C (requirements traceability matrix) is for tracking requirements, not stakeholders.
A project manager is assigned to a project that is in execution phase. The project has a cost performance index (CPI) of 0.8 and a schedule performance index (SPI) of 1.1. Which of the following best describes the current status of the project?
CPI=0.8 (<1) indicates cost overrun; SPI=1.1 (>1) indicates ahead of schedule.
Why this answer
A CPI of 0.8 means the project is earning only $0.80 for every $1.00 spent, indicating it is over budget. An SPI of 1.1 means the project is earning $1.10 for every $1.00 of planned work, indicating it is ahead of schedule. Therefore, the project is over budget but ahead of schedule, making option C correct.
Exam trap
The trap here is that candidates often confuse the direction of the indices, incorrectly assuming a CPI less than 1 means under budget or an SPI greater than 1 means behind schedule, when in fact CPI < 1 indicates over budget and SPI > 1 indicates ahead of schedule.
How to eliminate wrong answers
Option A is wrong because a CPI of 0.8 (less than 1.0) indicates the project is over budget, not under budget. Option B is wrong because while it correctly identifies the project as over budget (CPI < 1.0), it incorrectly states the project is behind schedule when the SPI of 1.1 (greater than 1.0) indicates it is ahead of schedule. Option D is wrong because although it correctly identifies the project as over budget (CPI < 1.0), it incorrectly states the project is behind schedule when the SPI of 1.1 indicates it is ahead of schedule.
What is the primary purpose of the daily stand-up in Scrum?
Identification of impediments is a key outcome of the daily stand-up.
Why this answer
The daily stand-up in Scrum is primarily designed for the team to synchronize their work and identify any impediments that may be blocking progress. It is not a status report to management (option A), as it is a team-internal event. Option C is incorrect because the review of completed work occurs in the sprint review, not the daily stand-up.
Option D is incorrect because while the team may discuss plans for the next 24 hours, the primary purpose is to inspect progress toward the sprint goal and identify impediments, not to create a detailed plan.
Which THREE of the following are types of dependencies that can exist between project activities?
Mandatory dependencies are legally or contractually required or inherent in the nature of the work. They are also known as hard logic and are one of the three correct types.
Why this answer
Mandatory dependencies are legally or contractually required or inherent in the nature of the work. For example, in a construction project, you must complete the foundation before erecting the walls. These are often referred to as 'hard logic' and cannot be changed without altering the project scope or approach.
Exam trap
PMI often tests the distinction between dependency types by including 'resource dependencies' as a distractor, which is not a PMBOK-recognized dependency type but a common misconception from resource-leveling discussions.
A project manager is reviewing the project charter and notices that the business case includes a cost-benefit analysis with a Net Present Value (NPV) of $50,000 and an Internal Rate of Return (IRR) of 12%. The company's required rate of return is 10%. What should the project manager conclude about this project?
IRR (12%) > required rate (10%) and positive NPV indicate financial viability.
Why this answer
The project is financially viable because the NPV is positive ($50,000), indicating that the present value of expected cash inflows exceeds the present value of cash outflows. Additionally, the IRR of 12% exceeds the company's required rate of return (10%), meaning the project's expected return is greater than the cost of capital. Both metrics independently confirm financial feasibility.
Exam trap
PMI often tests the misconception that a positive NPV alone is sufficient without considering the IRR relative to the required rate, or that a higher IRR always means a better project, ignoring scale and cash flow timing.
How to eliminate wrong answers
Option B is wrong because the payback period is not mentioned in the business case; NPV and IRR do not directly measure how quickly the initial investment is recovered. Option C is wrong because a positive NPV of $50,000 means the project is expected to generate a surplus beyond the required return, not just break even. Option D is wrong because both the positive NPV and the IRR exceeding the required rate of return indicate the project is financially viable, not non-viable.
Which practice is a key component of Extreme Programming (XP)?
Pair programming is an XP practice that improves code quality and knowledge sharing.
Why this answer
Pair programming is a core XP practice where two developers work together at one workstation. Sprint Review (option D) is a Scrum ceremony, Backlog Grooming (option C) is a Scrum practice, and Velocity Tracking (option B) is a metric used in various agile methodologies.
An Agile team consistently completes only about 70% of the planned work each sprint. Which action is most likely to improve the team's ability to meet commitments?
Smaller stories are easier to estimate and complete within a sprint.
Why this answer
Breaking down user stories into smaller pieces improves estimation accuracy and reduces the risk of large unfinished items. Increasing team size (B) can cause communication overhead, adding a buffer (C) does not address estimation quality, and reducing sprint length (D) may increase overhead.
After solution implementation, the business analyst discovers that a key performance indicator (KPI) has not improved as expected. What is the most appropriate next step?
Root cause analysis guides corrective actions.
Why this answer
Conducting root cause analysis helps identify why the solution is underperforming. Option B is wrong because requesting additional budget without analysis is premature. Option C is wrong because escalation without analysis is premature.
Option D is wrong because documenting in lessons learned without action is inadequate.
A manufacturing project using predictive plan-based methodology is underway. The project manager identifies a risk that a key raw material supplier may go bankrupt, which would halt production for at least two weeks. The probability is assessed as 30% with a high impact. The project manager plans to hold a risk response planning meeting with the team. One team member suggests identifying an alternative supplier and signing a contingency contract. Another recommends self-insuring by setting aside budget reserves. The project sponsor wants to reduce the probability by investing in supplier financial health monitoring. Which combination of risk responses is MOST appropriate for this risk?
Contingency contract transfers the impact, monitoring reduces probability.
Why this answer
The correct combination is transferring the risk via a contingency contract with an alternative supplier and mitigating the risk by monitoring the supplier's financial health. Transfer involves shifting the financial impact to another party (the alternative supplier through a contingency contract), while mitigation reduces the probability or impact (monitoring financial health). Option B (stockpiling) is a form of mitigation but not mentioned in the stem, and cancelling the project (avoid) is too extreme.
Option A suggests avoid by changing material (not feasible) and accept. Option D suggests accept and ignore, which is not appropriate for a high-impact risk.
Which THREE elements should be included in a needs assessment? (Choose three.)
Needs must align with goals.
Why this answer
Correct are A (Business goals and objectives), C (Problem or opportunity statement), and D (Current state analysis). B and E are solution-oriented artifacts, not part of a needs assessment.
A business analyst is tasked with verifying that the solution meets the defined requirements. Which activity is part of the verification process?
Testing directly verifies that the solution meets requirements.
Why this answer
Testing is a key verification activity that checks if the solution conforms to specified requirements.
A project manager is developing a project schedule for a software development project using a predictive approach. After identifying activities and sequencing them, what is the NEXT step?
This is the next step after sequencing activities.
Why this answer
After sequencing activities, the next process is to estimate activity durations, then develop schedule. Option D is correct.
During project execution, a key team member leaves the company. The project manager needs to quickly reassign tasks to maintain progress. Which document should be consulted first to understand the team member's current responsibilities?
It details team roles, responsibilities, and current assignments.
Why this answer
The resource management plan includes roles, responsibilities, and resource allocation. The other documents are less relevant for task reassignment.
Which TWO of the following are project management process groups?
Closing is one of the five process groups.
Why this answer
The correct answers are B (Closing) and C (Initiating). These are two of the five project management process groups. Scheduling (A), Risk Management (D), and Budgeting (E) are not process groups; they are knowledge areas or other project management terms.
A project manager is leading a construction project with a fixed budget and strict deadline. During execution, a key supplier notifies that a critical material will be delayed by two weeks, which will push the project past the deadline. The project manager reviews the schedule and identifies that the delay can be compensated by fast-tracking two subsequent activities that are currently planned sequentially. What should the project manager do first?
Fast-tracking increases risk, so risk assessment must precede implementation.
Why this answer
The correct first step is to assess the risks of fast-tracking the two activities (Option B). Fast-tracking involves performing activities in parallel that were originally planned sequentially, which can introduce new risks such as rework, resource conflicts, or quality issues. The PMBOK Guide emphasizes that before implementing a schedule compression technique, the project manager must evaluate the associated risks and determine if the benefits outweigh the potential negative impacts.
Since the project has a fixed budget and strict deadline, a risk assessment ensures informed decision-making before proceeding.
Exam trap
The trap here is that candidates may immediately choose to add resources (Option D) or accept the delay (Option A) without recognizing that the PMBOK Guide prescribes risk assessment as the mandatory first step before implementing any schedule compression technique.
How to eliminate wrong answers
Option A is wrong because accepting the delay without exploring schedule compression options violates the proactive management expected in predictive plan-based methodologies, especially when the deadline is strict. Option C is wrong because submitting a change request to extend the deadline should only be considered after evaluating alternatives like fast-tracking or crashing, not as the first action. Option D is wrong because immediately adding resources to the delayed activity (crashing) may increase costs, which conflicts with the fixed budget constraint, and the question specifically identifies fast-tracking as the viable option.
A software development team is transitioning from a plan-driven approach to Scrum. The Product Owner is enthusiastic but struggles to break down the product backlog into small, independent items. The team frequently encounters dependencies between user stories, causing delays in sprints. What is the best course of action for the Scrum Master to address this issue?
Proper story splitting reduces dependencies and improves sprint flow.
Why this answer
The Scrum Master's primary responsibility is to coach the Product Owner and the team on Scrum practices. In this scenario, the root cause is the Product Owner's inability to decompose user stories into small, independent items, which creates dependencies. By coaching the Product Owner on effective story splitting techniques (e.g., using vertical slicing, splitting by workflow steps, or by acceptance criteria), the Scrum Master directly addresses the source of the problem, enabling the team to deliver value incrementally without cross-story delays.
Exam trap
The trap here is that candidates often choose a reactive, team-level solution (like assigning a dependency owner or increasing sprint duration) instead of recognizing that the Scrum Master must coach the Product Owner to prevent dependencies from being created in the first place.
How to eliminate wrong answers
Option B is wrong because assigning a dependency owner is a workaround that does not eliminate the underlying issue of poorly decomposed stories; it adds a role that may create bottlenecks and violates the Scrum principle of self-organization without addressing the root cause. Option C is wrong because increasing sprint duration only masks the problem, reduces feedback frequency, and contradicts the Scrum timebox of one month or less; it does not teach the Product Owner how to create independent backlog items. Option D is wrong because asking developers to manage dependencies during the sprint shifts responsibility away from the Product Owner and the Scrum Master, and it ignores the need for proactive backlog refinement to prevent dependencies from entering the sprint.
A project manager is leading a business analysis effort to define the requirements for a new inventory management system. The stakeholders have conflicting needs regarding real-time data updates versus batch processing. Which business analysis technique should the PM use to facilitate a decision?
Decision trees evaluate consequences of different decisions, helping stakeholders choose.
Why this answer
A decision tree is a structured business analysis technique that evaluates the trade-offs between conflicting stakeholder requirements—in this case, real-time data updates versus batch processing—by quantifying the impact of each approach on project cost and timeline. This enables the project manager to facilitate an objective, data-driven decision rather than relying on subjective preferences.
Exam trap
The trap here is that candidates confuse requirement elicitation or documentation techniques (like process flow diagrams or validation workshops) with analytical decision-making tools, assuming any stakeholder conflict is resolved by gathering more requirements rather than by quantitatively comparing the impacts of each option.
How to eliminate wrong answers
Option A is wrong because developing a process flow diagram maps the current inventory process, which documents existing workflows but does not analyze the cost or schedule implications of the two conflicting technical approaches. Option B is wrong because a Gantt chart is a project scheduling tool used to plan and track requirement gathering activities, not a technique for evaluating trade-offs between real-time and batch processing. Option D is wrong because a requirements validation workshop reviews and confirms that requirements are complete and correct, but it does not provide a quantitative analysis of cost and timeline impacts needed to resolve the conflict between real-time updates and batch processing.
A team is using Scrum and notices that the Product Owner frequently changes priorities during the Sprint, causing the team to rework tasks. What should the Scrum Master do first?
The Scrum Master coaches the Product Owner to respect the Sprint scope.
Why this answer
The Scrum Master's primary responsibility is to ensure Scrum is understood and enacted. The Product Owner is violating the Sprint Backlog rule, which states that once a Sprint starts, the Product Owner cannot change the Sprint Backlog items; only the team can modify the Sprint Backlog to meet the Sprint Goal. By coaching the Product Owner on this rule and the impact of changes (e.g., rework, loss of focus, and potential Sprint Goal failure), the Scrum Master addresses the root cause without disrupting the team's workflow.
Exam trap
The trap here is that candidates may confuse the Product Owner's authority over the Product Backlog with the Sprint Backlog, assuming the Product Owner can change priorities at any time, when in fact the Sprint Backlog is frozen during the Sprint to protect the team's focus and the Sprint Goal.
How to eliminate wrong answers
Option B is wrong because shortening the Sprint duration does not solve the underlying issue of the Product Owner changing priorities; it only reduces the window for changes but still allows the same disruptive behavior within each shorter Sprint. Option C is wrong because asking the team to be flexible and accept changes violates the Scrum principle of a stable Sprint Backlog and undermines the team's ability to deliver a potentially releasable Increment; it normalizes a dysfunctional practice. Option D is wrong because escalating to the project sponsor bypasses the Scrum Master's role as a servant-leader and coach; the issue should be resolved within the Scrum framework first, not escalated externally.
A project manager is assigned a project that has a very low tolerance for scope changes. Which development approach is most appropriate?
Predictive (waterfall) approach is best when scope changes are minimal and requirements are well-understood.
Why this answer
A predictive (waterfall) approach is best when scope changes are minimal and requirements are well-understood. Option B is correct. Incremental (A) delivers portions of the product, which may allow for changes.
Adaptive (C) methods embrace change. Iterative (D) approaches also allow for changes through feedback.
Your organization is initiating a new mobile app development project. The product owner expects to release a minimum viable product (MVP) within three months, with subsequent iterations based on user feedback. The development team is experienced with agile methodologies. The project sponsor, however, is accustomed to traditional waterfall projects and insists on a detailed upfront plan covering all requirements and a fixed schedule. You need to select a project life cycle that balances the product owner's desire for iterative delivery with the sponsor's need for predictability. What is the most appropriate approach?
Iterative life cycle provides structure and allows for incremental delivery, satisfying both parties.
Why this answer
An iterative life cycle allows for early delivery of an MVP and incorporates feedback, while providing some planning structure. Pure agile may be too flexible for the sponsor; waterfall is too rigid. The key is to combine predictability with iteration.
During the execution phase of a software development project, the team discovers a critical bug that requires an immediate fix. The project manager uses the contingency reserve to address this. Which plan-based process is being applied?
This process manages changes to baselines, including using contingency reserves.
Why this answer
D is correct because using the contingency reserve to address a critical bug requires a formal change request to authorize the release of funds from the reserve. This aligns with the Perform Integrated Change Control process, which evaluates, approves, and manages changes to project baselines, including the cost baseline. The project manager must submit a change request, which is then reviewed by the Change Control Board (CCB) before the contingency reserve can be applied.
Exam trap
The trap here is that candidates often confuse using a contingency reserve with simply executing work (Direct and Manage Project Work) or monitoring performance (Monitor and Control Project Work), failing to recognize that any use of baseline reserves must go through formal change control to maintain the integrity of the project baselines.
How to eliminate wrong answers
Option A is wrong because Direct and Manage Project Work is the process of executing the work defined in the project management plan to achieve project objectives, not the process for approving changes to baselines or using reserves. Option B is wrong because Monitor and Control Project Work involves tracking, reviewing, and reporting overall project performance, but it does not include the formal approval of change requests or the authorization to use contingency reserves. Option C is wrong because Close Project or Phase is the process of finalizing all activities across all project management process groups to formally complete the project or phase, and it does not involve using contingency reserves for unplanned work.
A business analyst is evaluating whether a proposed solution aligns with the organization's strategic goals. Which business analysis technique should be used?
SWOT analysis helps evaluate strategic alignment by examining internal and external factors.
Why this answer
SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) is the correct technique because it directly evaluates how a proposed solution aligns with the organization's strategic goals by examining internal capabilities and external market factors. This technique helps the business analyst determine whether the solution leverages organizational strengths and opportunities while mitigating weaknesses and threats, ensuring strategic fit.
Exam trap
The trap here is that candidates often confuse SWOT analysis with gap analysis, assuming both assess alignment, but gap analysis focuses on performance discrepancies rather than strategic fit with organizational goals.
How to eliminate wrong answers
Option A is wrong because MoSCoW analysis (Must have, Should have, Could have, Won't have) is a prioritization technique used to categorize requirements, not to assess alignment with strategic goals. Option B is wrong because gap analysis identifies the difference between the current state and desired future state, but it does not directly evaluate strategic alignment with organizational goals. Option C is wrong because a feasibility study assesses whether a solution is technically, operationally, and economically viable, but it does not specifically measure alignment with strategic objectives.
A business analyst discovers that two requirements conflict with each other. What is the best strategy to resolve this conflict?
Collaborative negotiation is the best approach to resolve conflicts.
Why this answer
Facilitating a meeting with stakeholders allows for negotiation and collaboration to resolve the conflict. Option A is incorrect because asking the sponsor to choose may not address the underlying concerns and could bypass stakeholder input. Option C is incorrect because leaving the decision to the development team may lead to a technical decision that doesn't consider business needs.
Option D is incorrect because including both conflicting requirements without resolution could create inconsistencies, and adding a third requirement doesn't reconcile the original conflict.
Refer to the exhibit. The business analyst is analyzing system requirements for a payment gateway. Based on this error log, which non-functional requirement is most likely to be updated?
Correct: Timeout is a performance attribute.
Why this answer
The error describes a transaction timeout, which relates to system performance. Therefore, the performance requirement for timeout threshold should be reviewed and potentially increased.
Drag and drop the steps for developing a project schedule in the correct order.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Why this order
Schedule development follows: define, sequence, estimate resources and durations, then develop the schedule.
During a Sprint, the development team realizes they have taken on more work than they can complete. According to Scrum, what should they do?
Scrum encourages the team to negotiate with the Product Owner to adjust scope while protecting the Sprint Goal.
Why this answer
In Scrum, the development team is self-managing and responsible for committing to a Sprint Goal. If they realize they have taken on too much work, the correct action is to collaborate with the Product Owner to remove or defer Product Backlog items, as this preserves the Sprint's timebox and focus on the highest-value work. This aligns with the Scrum principle of transparency and inspection, allowing the team to adjust the Sprint Backlog without changing the Sprint duration.
Exam trap
PMI-CAPM often tests the misconception that Scrum teams should simply 'do their best' and deliver partial work (Option B) or escalate to management (Option C), but the correct Scrum behavior is proactive scope negotiation with the Product Owner within the fixed Sprint timebox.
How to eliminate wrong answers
Option B is wrong because delivering whatever is done at the end of the Sprint, regardless of missing items, violates the Scrum principle of a potentially releasable Increment and undermines the Sprint Goal; the team should actively manage scope rather than passively accept failure. Option C is wrong because asking management for more resources contradicts the self-managing nature of Scrum teams and the fixed timebox of a Sprint; Scrum does not allow adding resources mid-Sprint. Option D is wrong because extending the Sprint duration breaks the timebox rule; Sprints are fixed-length events (typically 2-4 weeks) and cannot be extended to accommodate overcommitment.
Practice CAPM by domain
Target a specific domain to shore up weak areas.