503 questions total · 7pages · All types, answers revealed
Page 7 of 7
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 A 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
Option A is correct because 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
Options A and C are correct because Initiating and Closing are process groups. B, D, and E are not process groups; they are knowledge areas or other 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
Option C is correct because 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
Option A is correct because 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 approaches are designed for stable requirements and minimal changes.
Why this answer
A predictive (waterfall) approach is best when scope changes are minimal and requirements are well-understood. Option B is correct. Adaptive (A) methods embrace change.
Iterative (C) and incremental (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
Option B is correct because involving stakeholders who own the requirements facilitates negotiation. A is wrong because ignoring leads to issues later. C is wrong because adding new requirement doesn't resolve.
D is wrong because voting may not address underlying 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
Option B is correct because in Scrum, the team collaborates with the Product Owner to adjust the Sprint scope while preserving the Sprint Goal. Option A is wrong because management is not involved in day-to-day adjustments. Option C violates the timeboxed Sprint.
Option D is not transparent; the team should negotiate scope changes proactively.
A project manager is developing the project schedule for a construction project. The team has identified all activities and their dependencies. Which tool should the project manager use to determine the critical path?
CPM calculates the critical path.
Why this answer
The Critical Path Method (CPM) is the correct tool because it calculates the longest path through the project network diagram by analyzing activity durations and dependencies, identifying which activities have zero float and thus determine the project's minimum completion time. The question specifically asks for determining the critical path, which is the core output of CPM, not just visualizing or estimating durations.
Exam trap
The trap here is that candidates confuse PERT with CPM because both use network diagrams, but PERT is for probabilistic duration estimation while CPM is specifically for identifying the critical path via float calculations.
How to eliminate wrong answers
Option A is wrong because the Work Breakdown Structure (WBS) is a hierarchical decomposition of project deliverables and work packages, not a scheduling tool; it does not include dependencies or durations needed to calculate the critical path. Option C is wrong because Program Evaluation and Review Technique (PERT) is a probabilistic method for estimating activity durations using optimistic, pessimistic, and most likely times, but it does not directly determine the critical path; CPM is the deterministic method for that. Option D is wrong because a Gantt chart is a visual bar chart showing activities over time, but it does not perform the forward/backward pass calculations required to identify the critical path; it merely displays the schedule after CPM analysis.
A project manager is defining the business analysis approach for a new software development project. The stakeholders are located in different countries and have varying levels of technical expertise. Which business analysis framework is most suitable for ensuring effective communication and collaboration?
Agile promotes continuous collaboration and adaptability.
Why this answer
Agile emphasizes iterative communication and collaboration, making it ideal for distributed teams with diverse expertise.
During Sprint Planning, the team realizes the password reset story involves a third-party email service that has not been integrated yet. The team has no experience with that service. What is the best action?
A spike reduces uncertainty and informs estimation.
Why this answer
The team has no experience with the third-party email service, and integrating it involves unknown technical risks. A time-boxed spike (Option B) is the best action because it allows the team to research the integration within a defined timebox, reducing uncertainty before committing to the story in a Sprint. This aligns with the Scrum principle of managing risk through validated learning, not through guesswork or scope changes.
Exam trap
PMI often tests the misconception that 'just figure it out during the Sprint' (Option A) is acceptable, but the CAPM expects you to recognize that unknown technical risks require a spike to protect the Sprint Goal and avoid waste.
How to eliminate wrong answers
Option A is wrong because accepting the story without understanding the third-party service's API, authentication (e.g., OAuth 2.0), or rate limits risks incomplete work and Sprint failure. Option C is wrong because adding more developers does not resolve the lack of knowledge about the email service's integration specifics; it may even increase coordination overhead without addressing the root cause. Option D is wrong because removing the story from the Product Backlog is premature; the story has business value, and a spike can provide the necessary research to proceed.
A project manager identifies a risk that could cause a 10-day delay. The probability of occurrence is 30%. What is the expected monetary value (EMV) of this risk?
EMV = 0.3 × 10 = 3 days.
Why this answer
EMV is calculated as Probability × Impact. Here, 0.3 × 10 days = 3 days. EMV is used to quantify risk in monetary terms, but in this case impact is in days.
Which TWO of the following are commonly used requirements elicitation techniques?
Prototyping allows stakeholders to interact with a model to refine requirements.
Why this answer
Brainstorming and Prototyping are direct elicitation techniques. Variance Analysis, Monte Carlo Simulation, and Parametric Estimating are from other knowledge areas (monitoring, risk, cost).
Refer to the exhibit. A business analyst has documented the current and target states for invoice processing. What business analysis technique is being used?
Gap analysis compares current and desired states to identify differences.
Why this answer
The business analyst is comparing the current state and target state of invoice processing to identify the differences or gaps that need to be addressed. This is the core definition of gap analysis, which is a technique used to determine the steps required to move from the current state to the desired future state. The exhibit explicitly shows a 'Current State' and 'Target State' for invoice processing, making gap analysis the correct technique.
Exam trap
The trap here is that candidates may confuse gap analysis with root cause analysis because both involve analyzing problems, but gap analysis focuses on the difference between current and target states, while root cause analysis digs into the origin of a single problem.
How to eliminate wrong answers
Option A is wrong because a feasibility study assesses whether a project or solution is viable in terms of cost, time, and resources, not by comparing current and target states. Option B is wrong because SWOT analysis evaluates internal Strengths and Weaknesses and external Opportunities and Threats, not a direct comparison of current and target process states. Option D is wrong because root cause analysis is used to identify the underlying cause of a problem or defect, not to document the difference between current and target states.
Refer to the exhibit. Based on the server health check, which requirement is most likely to be triggered?
Correct: Disk usage at 92% with critical error.
Why this answer
The error message indicates a critical disk space issue on /var/log, so expanding disk space is the most likely requirement. CPU and memory are within normal ranges, and replacing the server is premature.
A financial services company is adopting Scrum for a critical compliance project. The team has six developers, one product owner, and one Scrum Master. After three sprints, the product owner is frustrated because the team has only delivered 40% of the planned features. The team says they are working full capacity but keep getting interrupted by urgent production support requests from the operations team. The Scrum Master notices that the team’s velocity is dropping each sprint. The product owner insists on increasing the sprint length from two weeks to four weeks to allow more time for delivery. However, the compliance deadline is fixed. The Scrum Master must recommend a course of action. What should the Scrum Master do?
This acknowledges support work as legitimate and helps the team focus by limiting multitasking.
Why this answer
The root cause is that the team is multitasking between sprint work and support requests. Increasing sprint length would delay feedback and hide the problem. The best action is to address the interruptions by having the product owner prioritize support requests as part of the backlog, and possibly allocate a dedicated support person if needed.
Removing the Scrum Master is not helpful. Telling the team to work harder ignores the systemic issue. Adding a second daily stand-up adds ceremony, not capability.
In Kanban, the team is experiencing frequent bottlenecks at the testing stage. Which practice should they adopt to improve flow?
WIP limits expose bottlenecks and encourage flow.
Why this answer
In Kanban, limiting Work in Progress (WIP) at each stage is a core practice to expose bottlenecks and improve flow. By capping the number of items allowed in testing, the team prevents work from piling up, forcing them to finish existing tasks before pulling new ones. This directly addresses the frequent bottlenecks by making the constraint visible and actionable, enabling the team to focus on completing testing rather than starting more work.
Exam trap
The trap here is that candidates often confuse adding more testers (Option C) as a quick fix for a bottleneck, but the CAPM exam emphasizes that Kanban focuses on limiting WIP to expose and address constraints rather than simply adding resources.
How to eliminate wrong answers
Option A is wrong because increasing batch size of work items typically increases cycle time and variability, worsening bottlenecks rather than improving flow. Option B is wrong because daily stand-up meetings are a Scrum event for coordination and impediment identification, but they do not directly control or limit the amount of work in progress to alleviate a specific bottleneck. Option C is wrong because adding more testers to the testing phase may provide temporary relief but does not address the systemic flow issue; it often leads to increased coordination overhead and can mask the root cause of the bottleneck, violating the Kanban principle of making policies explicit and improving the system rather than adding resources.
You are the project manager for a large infrastructure project using a predictive plan-based methodology. The project has a critical path duration of 200 days. After 50 days of execution, a major delay occurs on a critical path activity due to unforeseen ground conditions, adding 20 days to that activity. The project has no float on the critical path. The sponsor requests a recovery plan to bring the project back on schedule. The team proposes two options: (1) crash activity X on the critical path by adding overtime, costing $10,000 and saving 5 days; (2) fast-track activity Y and Z by starting Y earlier, saving 10 days but increasing risk. What is the BEST integrated approach?
Combines two compression techniques to recover most of the delay, then formally adjusts the schedule.
Why this answer
With a 20-day delay, the best approach combines fast-tracking (10 days) and crashing (5 days) to recover 15 days, then negotiate a schedule change for the remaining 5 days. Option D is correct. Option A only fast-tracks, insufficient.
Option B only crashes, insufficient. Option C crashes and accepts, delaying completion.
A team using Scrum has a velocity of 30 story points per Sprint. The Product Owner wants to plan for the next release with 150 story points of work remaining. The team is stable. Which release planning approach aligns with agile principles?
This approach uses empirical data for forecasting while keeping detailed planning short-term.
Why this answer
Option D is correct. Agile planning is iterative and based on empirical data; detailed planning for future Sprints is wasteful. Option A is too rigid.
Option B assumes stability. Option C adds unnecessary buffers.
In a Kanban system, what is the primary purpose of limiting Work in Progress (WIP)?
WIP limits reveal bottlenecks when a column hits its limit, prompting the team to address the constraint and improve flow.
Why this answer
Option C is correct because WIP limits help identify bottlenecks by preventing overloading of the system. Option A is wrong as it's not about measuring team speed directly. Option B is wrong since it doesn't assign tasks.
Option D is wrong because while quality may improve, the primary purpose is flow management.
Which TWO of the following are true regarding a project's life cycle?
Hybrid life cycles blend elements of both predictive and adaptive to suit project needs.
Why this answer
Option A is correct because hybrid life cycles intentionally blend predictive (plan-driven) and adaptive (iterative) approaches to leverage the strengths of both. For example, a project might use a predictive phase for requirements gathering and high-level design, then switch to adaptive sprints for development and testing. This allows flexibility in execution while maintaining upfront planning where needed.
Exam trap
The trap here is that candidates often confuse the project life cycle with the product life cycle, assuming they are the same or that the project life cycle defines the product life cycle, when in fact the product life cycle is the broader umbrella.
A project manager is creating the project schedule. The team estimates that the optimistic time for an activity is 10 days, the pessimistic time is 30 days, and the most likely time is 15 days. Using PERT three-point estimation, what is the expected duration?
Correct calculation using PERT formula.
Why this answer
The PERT three-point estimate formula is (Optimistic + 4×Most Likely + Pessimistic) / 6. Plugging in the values: (10 + 4×15 + 30) / 6 = (10 + 60 + 30) / 6 = 100 / 6 = 16.67 days. This weighted average gives more influence to the most likely estimate, reflecting a beta distribution.
Exam trap
The trap here is that candidates often use a simple arithmetic mean (average) instead of the weighted PERT formula, leading them to select 18.33 days (Option B).
How to eliminate wrong answers
Option B (18.33 days) is wrong because it results from using a simple average (10+15+30)/3 = 18.33, ignoring the PERT weighting factor of 4 for the most likely time. Option C (20.00 days) is wrong because it incorrectly uses the midpoint between optimistic and pessimistic (10+30)/2 = 20, which disregards the most likely estimate entirely. Option D (15.00 days) is wrong because it assumes the expected duration equals the most likely time, failing to account for the influence of optimistic and pessimistic extremes.
A business analyst is selecting a business analysis framework for a small project with limited budget. Which framework characteristic is most important to consider?
Scalability allows the framework to be adapted without waste.
Why this answer
For a small project with a limited budget, the most important characteristic of a business analysis framework is scalability, because it allows the framework to be tailored to the project's size and complexity without incurring unnecessary overhead or costs. A framework that is too rigid or comprehensive would waste resources on activities that do not add value for a small project, while a scalable approach ensures that only essential analysis tasks are performed. This directly aligns with the principle of 'just enough' business analysis, which is critical when budget constraints are tight.
Exam trap
The trap here is that candidates often choose 'comprehensiveness' (Option C) because they assume a framework must cover all scenarios to be effective, but the CAPM exam tests the understanding that frameworks must be tailored to project constraints, and for a small budget, scalability is the key enabler of cost efficiency.
How to eliminate wrong answers
Option B is wrong because alignment with industry standards, while beneficial for consistency and interoperability, is not the most critical factor when budget is limited; a small project can still succeed without strict adherence to standards if the framework is scalable. Option C is wrong because comprehensiveness to cover all possible scenarios would introduce excessive documentation and analysis activities, driving up costs and time, which is counterproductive for a small project with a limited budget. Option D is wrong because integration with existing project management tools is a convenience feature, not a primary driver; a scalable framework can be adapted to work with minimal tooling, and forcing integration could add unnecessary expense.
A business analyst is working on a project to develop a mobile banking application. During the requirements analysis phase, the BA creates a set of user stories and acceptance criteria. The BA then conducts a peer review with the development team. The team points out that the stories are too large and vague to estimate. The BA needs to refine the requirements to make them actionable. The project is using an agile methodology with two-week sprints. What should the BA do?
Splitting stories makes them estimable and sprint-ready.
Why this answer
In agile methodologies, user stories must be small enough to fit within a single sprint and provide clear, testable acceptance criteria for estimation and development. Splitting large, vague stories into smaller, specific stories with acceptance criteria directly addresses the team's inability to estimate, enabling accurate sprint planning and incremental delivery. This aligns with the INVEST principle (Independent, Negotiable, Valuable, Estimable, Small, Testable) for effective user stories.
Exam trap
PMI often tests the misconception that adding more detail or creating a prototype is sufficient to make stories actionable, but the core agile requirement is that stories must be small enough to be estimable and completed within a single sprint.
How to eliminate wrong answers
Option B is wrong because simply adding more detail to existing large stories does not reduce their size; they remain too large for a two-week sprint and still cannot be reliably estimated. Option C is wrong because creating a prototype is a discovery technique that may clarify requirements but does not inherently produce actionable, estimable user stories; it adds an extra step and delays refinement. Option D is wrong because asking the team to re-estimate stories that are known to be too large and vague will yield unreliable estimates, violating the core agile principle that stories must be estimable to be planned.
Before approving a major IT system upgrade, the steering committee wants to understand whether the proposed solution is technically feasible and aligns with the organization's strategic goals. The business analyst should recommend conducting which type of analysis?
Feasibility study evaluates viability before significant investment.
Why this answer
A feasibility study assesses technical, economic, and operational viability before committing to a project. A business case is built after feasibility; ROI analysis is part of the business case; SWOT analysis is for strategic positioning.
In a project to implement a new customer relationship management (CRM) system, the business analyst needs to understand the current workflows and identify areas for improvement. Which technique should be used?
Process modeling captures current workflows and identifies improvement opportunities.
Why this answer
Process modeling is the correct technique because it visually maps out the current workflows, showing the sequence of activities, decision points, and handoffs in the CRM system. This allows the business analyst to identify inefficiencies, bottlenecks, and areas for improvement in the existing processes before designing the new system.
Exam trap
The trap here is that candidates often confuse 'document analysis' (reviewing existing materials) with 'process modeling' (creating a visual representation of workflows), leading them to pick A when the question specifically asks for a technique to understand and improve workflows.
How to eliminate wrong answers
Option A is wrong because document analysis involves reviewing existing documentation (e.g., user manuals, process documents) to gather information, but it does not actively model or visualize workflows to identify improvement areas. Option C is wrong because benchmarking compares performance metrics against industry standards or competitors, which is useful for setting targets but not for understanding current internal workflows. Option D is wrong because root cause analysis is used to identify the underlying causes of a specific problem or defect, not to map and analyze entire workflows for improvement.
A project manager is estimating activity durations for a software development project. The team has historical data from similar projects, but the current project involves new technology that could cause delays. Which estimating technique should the project manager use to account for uncertainty?
Incorporates uncertainty via three values.
Why this answer
Three-point estimating (C) is correct because it explicitly accounts for uncertainty by using optimistic, most likely, and pessimistic estimates. The new technology introduces unknown risks, making the triangular or PERT distribution ideal for modeling the potential delay range.
Exam trap
The trap here is that candidates often choose analogous estimating (B) because it seems quick and uses past data, but they miss that new technology invalidates the similarity assumption, making three-point estimating the correct choice for uncertainty.
How to eliminate wrong answers
Option A is wrong because parametric estimating uses statistical relationships between historical data and variables (e.g., lines of code per hour) but does not inherently model uncertainty from novel technology. Option B is wrong because analogous estimating relies on historical data from similar projects, which is less reliable when new technology introduces unknown delays. Option D is wrong because bottom-up estimating aggregates detailed estimates from individual work packages, but it does not incorporate a formal uncertainty range unless combined with three-point estimates.
In a Kanban system, the team notices that work items are spending too much time in the 'In Progress' column. Which practice should the team adopt to improve flow?
WIP limits prevent overloading and help identify bottlenecks.
Why this answer
Setting a strict Work In Progress (WIP) limit for the 'In Progress' column directly addresses the bottleneck by capping the number of items the team can work on simultaneously. This forces the team to finish existing work before pulling new items, reducing multitasking and cycle time. In Kanban, WIP limits are the primary mechanism to expose flow inefficiencies and improve throughput.
Exam trap
PMI often tests the misconception that increasing WIP limits or removing columns will 'simplify' the process, when in fact the correct Kanban response to a bottleneck is to enforce stricter limits to expose and resolve the constraint.
How to eliminate wrong answers
Option A is wrong because longer development cycles increase batch size and delay feedback, worsening flow rather than improving it. Option B is wrong because increasing the WIP limit would allow more items to accumulate in the column, exacerbating the bottleneck and increasing lead time. Option C is wrong because removing the 'In Progress' column hides the bottleneck and eliminates the ability to visualize and manage work in that state, violating a core Kanban principle of making work visible.
A Product Owner frequently misses backlog refinement sessions, leaving user stories vague. The Development Team is struggling to estimate and plan Sprints. What fundamental Scrum role is being neglected?
The Product Owner is accountable for the Product Backlog, including its content, availability, and prioritization. Frequent absence from refinement neglects this duty.
Why this answer
Option C is correct because the Product Owner is responsible for maximizing the value of the product and managing the Product Backlog, including its refinement. Option A is wrong as the Scrum Master is a facilitator and coach. Option B is wrong as the Development Team does own the Sprint Backlog.
Option D is wrong as the Project Manager role does not exist in pure Scrum.
Match each project constraint to its typical trade-off.
Drag a concept onto its matching description — or click a concept then click the description.
What work is included
Time available for completion
Budget allocated
Standards to be met
People and equipment available
Why these pairings
Constraints often require balancing in the triple constraint model.
A project manager notices that the project's cost performance index (CPI) is 0.85. What does this indicate?
Correct: CPI less than 1 means cost overrun.
Why this answer
CPI < 1 indicates that the project is over budget, as the value earned is less than the cost incurred.
Which TWO of the following are valid techniques for schedule compression in a predictive project?
Fast tracking performs activities in parallel.
Why this answer
Options B and D are correct. Crashing adds resources, fast tracking overlaps activities. Option A is wrong because resource leveling can lengthen schedule.
Option C is wrong because lag increases duration. Option E is wrong because Monte Carlo simulation is a modeling technique, not compression.
Which TWO of the following are considered business analysis planning activities?
Stakeholder analysis is a key planning activity.
Why this answer
Options A and C are correct because business analysis planning includes selecting techniques (A) and conducting stakeholder analysis (C). B is solution design, D is elicitation execution, E is project selection.
In a predictive project, the project manager must formally accept the project's deliverables. Which process group does this activity belong to?
Correct: Deliverables are formally accepted during project or phase closing.
Why this answer
Formal acceptance of deliverables occurs during the Closing process group, specifically in the Validate Scope and Close Project processes.
A business analyst is using a business analysis framework to identify stakeholders. Which technique is most effective for ensuring all affected parties are considered?
A stakeholder map systematically identifies and categorizes stakeholders.
Why this answer
Option C is correct because stakeholder mapping, when validated with experts, systematically identifies all affected parties by visually representing relationships, influence, and impact. This technique leverages expert judgment to cross-check the map against organizational knowledge, ensuring no stakeholder group is overlooked. It is more comprehensive than ad-hoc methods because it follows a structured framework (e.g., PMI's stakeholder identification process) and incorporates validation to fill gaps.
Exam trap
The trap here is that candidates confuse 'brainstorming' (Option A) as a comprehensive technique, but the CAPM exam requires a structured, validated approach (stakeholder mapping with expert validation) to ensure all affected parties are considered, not just those immediately visible.
How to eliminate wrong answers
Option A is wrong because brainstorming with the project team is unstructured and relies on the team's limited perspective, often missing stakeholders outside their immediate awareness (e.g., regulatory bodies or downstream users). Option B is wrong because one-on-one interviews with known stakeholders only capture their personal views, creating a snowball effect that may still miss indirect or marginalized stakeholders not in the interviewee's network. Option D is wrong because distributing a questionnaire to the organization is passive and relies on self-identification, which can lead to low response rates and overlook stakeholders who do not see themselves as affected (e.g., future users or external auditors).
A business analyst is working on a project to implement a new human resources software. The project is using an Agile framework with two-week sprints. After three sprints, the product owner is frustrated because the team has not delivered any working functionality that can be demoed. The business analyst realizes that the user stories lack acceptance criteria and are too large to complete in a sprint. The team is also spending too much time on documentation. As the business analyst, what should you do to improve the situation?
Smaller stories with acceptance criteria are easier to estimate and demonstrate.
Why this answer
Option B is correct because decomposing stories and adding acceptance criteria improves clarity and delivery. Option A ignores root causes. Option C lengthens sprints but doesn't fix story quality.
Option D avoids the real issue.
How many work packages are at WBS level 2 (the second level) in this exhibit?
The three decomposition elements at level 2 are Planning, Execution, and Closure.
Why this answer
Option C is correct. Level 1 is '1.0 Project'. Level 2 consists of '1.1 Planning', '1.2 Execution', and '1.3 Closure' — that's three work packages.
Option A counts only two, option B counts four incorrectly, option D counts six (the leaf nodes).
You are a project manager working on a large infrastructure project under a strong matrix organization. The project charter has been signed, and you have been given authority to manage the project. However, the functional manager of the engineering department is refusing to assign the promised resources, claiming that another project has higher priority. You have already held a meeting with the sponsor and functional manager, but the functional manager remains uncooperative. The sponsor is concerned about the project's viability. What is the most effective course of action?
The sponsor has authority to prioritize projects and ensure resource commitments are honored.
Why this answer
In a strong matrix, the project manager has significant authority, but functional managers still control resources. The best action is to refer to the project charter and sponsor to enforce resource commitments. Option A is too adversarial.
Option B is premature rescheduling. Option D undermines the project manager's authority.
A project manager sees this JSON policy for cloud resources. Which project management process is being supported by enforcing these tags?
Tracking costs and resource usage.
Why this answer
Option B is correct because the policy enforces cost control and resource allocation, which are part of Monitoring and Controlling. Option A is wrong because Initiating is about authorization. Option C is wrong because Executing is about doing the work.
Option D is wrong because Closing is about finalizing.
A project manager is estimating activity durations for a new software development project. The manager has data from three similar previous projects, but the new project is slightly larger in scope. Which estimating technique is most appropriate given the available data?
Uses historical data from similar projects to estimate durations; appropriate here.
Why this answer
Option D is correct because analogous estimating uses historical data from similar projects. Option A is wrong because three-point estimating requires optimistic, pessimistic, and most likely estimates, which are not provided. Option B is wrong because parametric estimating uses a statistical relationship, not just historical data.
Option C is wrong because bottom-up estimating is detailed and time-consuming.
Which THREE factors should a business analyst consider when selecting an elicitation technique for a project?
Stakeholder availability influences technique choice (e.g., workshops vs surveys).
Why this answer
A is correct because stakeholder availability directly impacts the feasibility of scheduling and conducting elicitation activities such as interviews, workshops, or focus groups. If key stakeholders are unavailable, the chosen technique may be impractical or yield incomplete information, making this a primary logistical consideration in technique selection.
Exam trap
The trap here is that candidates often confuse 'project manager's preference' or 'cost' as valid selection criteria, but the CAPM exam specifically tests the BABOK's three primary factors: stakeholder availability, type of information needed, and level of detail required.
Based on the exhibit, what is the most significant risk for the upcoming iteration?
The planned 30 points exceed the average velocity of 21, indicating overcommitment.
Why this answer
The exhibit shows a planned velocity of 40 story points per iteration, but the historical velocity data indicates the team consistently completes only 30 story points. This mismatch means the team is overcommitting, which will likely lead to unfinished work and reduced quality. In Agile, using historical velocity as a baseline is critical for realistic iteration planning.
Exam trap
PMI often tests the misconception that a team can simply increase velocity by working harder or adding resources, rather than respecting historical data as a reliable predictor of capacity.
How to eliminate wrong answers
Option B is wrong because scope creep from new requirements is a product backlog management issue, not the most significant risk shown in the exhibit; the exhibit focuses on velocity data, not backlog changes. Option C is wrong because the team's velocity is not dropping—it is stable at 30 story points—and adding more team members often disrupts team dynamics and does not guarantee increased velocity. Option D is wrong because the velocity is not trending upward; it is flat at 30, making the plan to deliver 40 unrealistic.
Refer to the exhibit. What is the duration of the critical path?
Correct calculation of longest path.
Why this answer
Option A is correct. The critical path is A -> C -> D with a total duration of 5 + 4 + 6 = 15 days. The other path A -> B -> D is 5+3+6=14 days.
In Extreme Programming (XP), which practice involves integrating and testing the entire system multiple times per day?
CI ensures that code is integrated and tested frequently, reducing integration issues.
Why this answer
Option C is correct. Continuous integration (CI) is the practice of integrating code changes frequently, often multiple times per day, followed by automated testing. Option A (pair programming) involves two developers working together.
Option B (TDD) focuses on writing tests before code. Option D (refactoring) is about improving code structure.
Refer to the exhibit. The project manager is reviewing deployment logs. Which statement best describes the event?
The error was followed by a successful retry, indicating resolution.
Why this answer
Option A is correct because the error indicates an issue that was resolved by a retry. Option B is incorrect because an error did occur. Option C is incorrect because the retry was successful.
Option D is incorrect because no warning was logged.
Page 7 of 7
Practice CAPM by domain
Target a specific domain to shore up weak areas.