Free PMI Certified Associate in Project Management (CAPM) Sample Questions

Correct answer: B — To bring together prequalified stakeholders to discuss expectations and attitudes toward a proposed product

• A. Incorrect. Focus groups involve group discussions, not one-on-one interviews. Structured one-on-one interviews are used for individual detailed requirements gathering, whereas focus groups facilitate group interaction to gather collective insights.
• B. Correct. A focus group brings together prequalified stakeholders to collectively discuss and provide insights about their expectations, perceptions, and attitudes toward a proposed product, service, or project. It is a qualitative technique commonly used to gather feedback and validate ideas early in the project.
• C. Incorrect. While focus groups involve facilitated discussion, their primary purpose is not conflict resolution. Conflict resolution is addressed through techniques like negotiation or mediation, not focus groups.
• D. Incorrect. Focus groups are qualitative in nature and are not used for quantitative risk prioritization. Quantitative risk analysis uses tools like decision tree analysis or Monte Carlo simulations.

Correct answer: C — Cause-and-effect diagram, which maps causes to a problem

• A. Incorrect. A histogram shows the frequency distribution of data, helping identify patterns in numerical values, but it does not map relationships among multiple causes of a problem.
• B. Incorrect. A control chart tracks process performance and stability over time, detecting variation or trends. It is not designed to display interrelated causes of a complex problem.
• C. Correct. A cause-and-effect diagram, also known as a fishbone or Ishikawa diagram, visually organizes potential causes of a problem and their relationships, making it ideal for understanding how multiple factors contribute to an issue.
• D. Incorrect. A scatter diagram shows the correlation between two variables, useful for paired data analysis, but it does not capture many interrelated causes as effectively as a cause-and-effect diagram.

Correct answer: C — To inspect and adapt team processes for continuous improvement

• A. Incorrect. Updating the product backlog with new user stories is typically done during backlog refinement or sprint planning, not in the retrospective. The retrospective focuses on how the team worked and process improvement, not on adding scope items.
• B. Incorrect. Demonstrating working software to stakeholders is the purpose of the sprint review, where the team presents the increment and gathers feedback. The retrospective is an internal team meeting focused on process improvement, not on showcasing deliverables.
• C. Correct. The primary goal of a retrospective is to inspect the team's processes, identify what went well and what could be improved, and adapt for future sprints to foster continuous improvement. It is a key practice for the team to reflect and adjust their workflow, tools, and interactions.
• D. Incorrect. While a retrospective may surface team issues, its main purpose is not specifically to resolve conflicts between the product owner and development team. Conflict resolution can happen in many settings, but the retrospective is primarily for process improvement, not interpersonal conflict resolution.

Correct answer: D — Stakeholder engagement plan

• A. Incorrect. The project charter formally authorizes the project and provides high-level information, such as high-level risks and stakeholders, but it does not detail specific engagement strategies for stakeholders.
• B. Incorrect. The benefits management plan describes how and when the project's benefits will be delivered and measured, not how to engage stakeholders.
• C. Incorrect. The scope management plan defines how the project scope will be defined, validated, and controlled. It does not focus on stakeholder involvement or engagement strategies.
• D. Correct. The stakeholder engagement plan is a subsidiary plan of the project management plan that identifies strategies and actions to effectively engage stakeholders based on their needs, interests, and impact. It includes communication methods, frequency, and approaches to manage expectations and influence.

Correct answer: A — Identified risk events, probability, impact, and planned responses.

• A. Correct. The risk register is the primary document for recording identified risks, their probability, impact, and planned responses. It is a key component of the risk management strategy and is used to track and manage risks throughout the project.
• B. Incorrect. Project cost estimates and the approved budget baseline are part of cost management documents, such as the cost baseline and cost management plan, not the risk register. They track financial performance, not uncertainties.
• C. Incorrect. Task assignments with resource names and availability dates are documented in resource management or staffing plans. They relate to resource allocation, not to risk identification and response.
• D. Incorrect. A timeline with project milestones and deliverable dates is part of the project schedule or milestone chart. The risk register focuses on potential uncertainties and how they will be addressed, not on scheduled dates.

Correct answer: A — It ensures stakeholders get the right information when needed.

• A. Correct. A communication management plan ensures that stakeholders receive the right information at the right time through appropriate channels, which is its primary purpose. It outlines how, when, and by whom information will be shared, keeping the project aligned and supporting timely decision-making.
• B. Incorrect. While a communication management plan can reduce misunderstandings and related risks, it cannot remove all project risks caused by poor communication. Some risks are outside the control of communication planning alone.
• C. Incorrect. The plan can help engage stakeholders and increase buy-in, but it cannot guarantee full support from every stakeholder. Stakeholder attitudes and priorities may still differ despite good communication.
• D. Incorrect. The purpose of communication planning is not to lower the budget by restricting channels. The focus is on effective, timely, and appropriate communication, which may require using multiple channels.

Correct answer: C — Risk register

• A. Incorrect. The stakeholder register records information about stakeholders, such as interests and influence, but is not the primary place for documenting risks or planned responses.
• B. Incorrect. The issue log is used for problems that have already occurred. A potential developer departure is a future risk, not an active issue.
• C. Correct. The risk register is the official document for recording identified risks, their analysis, response plans, and owners. A key developer leaving is a potential schedule risk and should be documented there with the planned response.
• D. Incorrect. A change request is used to propose modifications to project documents or baselines, not to capture an identified risk and its response.

Correct answer: B — Conduct lessons learned and archive project documents.

• A. Incorrect. Transitioning to the next phase is not appropriate at this stage because the project should be closed. Closure activities, such as lessons learned and documentation, must be completed before considering any next phase. If the project is part of a program, the transition occurs after closure.
• B. Correct. After formal acceptance, the project manager must perform project closure activities. Conducting lessons learned and archiving project documents are critical steps to capture knowledge and officially close the project, ensuring organizational process assets are updated.
• C. Incorrect. Unfinished work contradicts the premise that all deliverables have been completed and accepted. The focus after acceptance is on closure, not on assigning additional work.
• D. Incorrect. Updating the risk register with final outcomes may be part of closure, but it is not the immediate next step. Lessons learned and document archiving take priority as they conclude the project's knowledge transfer.

Correct answer: A — Quality management plan

• A. Correct. The quality management plan is the subsidiary plan that defines how quality policies will be implemented and how quality will be measured, monitored, evaluated, and controlled throughout the project.
• B. Incorrect. The risk management plan addresses how risks will be identified, analyzed, and responded to, not how quality will be measured.
• C. Incorrect. The procurement management plan outlines how goods and services will be acquired from outside the project team, not how quality will be measured.
• D. Incorrect. The resource management plan describes how project resources (team, equipment, etc.) will be acquired, allocated, and managed, not how quality will be measured.

Correct answer: B — The project sponsor

• A. Incorrect. The project manager is responsible for planning, leading, and coordinating the project work and ensuring it meets objectives, but is not ultimately accountable for the project's overall success. Accountability rests with a higher authority, typically the project sponsor.
• B. Correct. The project sponsor is the individual or group who provides resources and support, champions the project, and is ultimately accountable for its overall success, including alignment with business objectives and high-level decision-making.
• C. Incorrect. The functional manager oversees a specific department or function and may support the project by providing resources, but does not hold accountability for the project's overall success.
• D. Incorrect. The project team is responsible for executing work and producing deliverables, but not for overall project accountability. Accountability lies with leadership roles such as the sponsor and project manager.

Correct answer: A — Leadership sets the project vision and inspires the team; management executes plans and monitors progress.

• A. Correct. This option captures the core distinction: leadership focuses on setting a vision and inspiring the team, while management focuses on executing plans and monitoring progress. According to the PMBOK Guide, leadership involves guiding and motivating the team toward project objectives, whereas management involves planning, organizing, and controlling work to achieve those objectives. This is the most comprehensive and accurate characterization.
• B. Incorrect. While leadership can involve establishing strategic direction and management coordinates daily activities, this option misses the inspirational and people-focused aspects of leadership. It presents a valid contrast but is less complete than option A, which explicitly highlights the visionary and motivational elements. The PMBOK Guide emphasizes that leadership is about influencing and inspiring, not just direction-setting.
• C. Incorrect. Although leadership does motivate and align people, and management focuses on tasks and schedules, this option oversimplifies management by ignoring its broader functions like planning, organizing, and controlling resources. While it touches on the people-versus-task distinction, it is not as precise or comprehensive as option A in differentiating the two concepts.
• D. Incorrect. Leadership is indeed visionary and seeks opportunities, but management is not merely administrative or about maintaining the status quo. Management actively plans, coordinates, and tracks work to achieve project objectives, and it often involves adapting and improving processes. This option inaccurately portrays management as static and narrow, which contradicts the PMBOK Guide's view of management as a dynamic function.

Correct answer: A — Change control board

• A. Correct. The Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes that exceed the project manager's authority. Involving the CCB ensures changes are handled through formal change control processes, preventing uncontrolled scope creep.
• B. Incorrect. The project team executes the work and may identify or assess the impact of changes, but they do not have the authority to approve scope changes beyond the project manager's threshold. Their role is more operational than governance-related.
• C. Incorrect. The project sponsor provides high-level support and funding and may approve major changes in some organizations, but the standard body for controlling and authorizing routine changes is the Change Control Board. The sponsor typically delegates change approval authority to the CCB for operational changes.
• D. Incorrect. The Quality Assurance team focuses on ensuring quality processes and standards are followed, not on authorizing scope changes. While they may identify issues caused by changes, they do not have the authority to approve or reject change requests.

Correct answer: A — Finalizing all project deliverables for formal acceptance

• A. Correct. Finalizing all project deliverables for formal acceptance is a key activity in predictive, plan-based methodologies, where scope is defined upfront and deliverables are completed sequentially before formal acceptance occurs. While agile projects also have acceptance, this practice is most closely associated with a structured phase-end review in plan-based approaches.
• B. Incorrect. Facilitating a sprint retrospective is an agile practice used to inspect and improve team performance at the end of a sprint. It is specifically tied to iterative and adaptive methodologies like Scrum, not predictive, plan-based projects.
• C. Incorrect. Updating and reprioritizing the product backlog is an agile activity that allows requirements to evolve based on feedback. Predictive projects define scope upfront and manage changes through formal change control, not continuous backlog refinement.
• D. Incorrect. Holding daily coordination meetings (e.g., daily stand-ups) is an agile ceremony to synchronize team activities. While predictive projects may have regular status meetings, this specific practice is characteristic of adaptive methodologies, not plan-based ones.

Correct answer: C — Create WBS

• A. Incorrect. Develop Project Charter is part of the Initiating Process Group, not the Planning Process Group. It formally authorizes the project and grants authority to the project manager, but does not decompose the project scope.
• B. Incorrect. Plan Scope Management is part of the Planning Process Group and determines how scope will be defined, validated, and controlled. It creates the Scope Management Plan but does not produce the hierarchical decomposition of project work.
• C. Correct. Create WBS is the process that subdivides project deliverables and project work into smaller, more manageable components. This hierarchical decomposition defines the total scope of work and is the foundation for further planning.
• D. Incorrect. Validate Scope is part of the Monitoring and Controlling Process Group and involves formalizing acceptance of completed project deliverables. It occurs after work is performed and does not decompose the scope.

Correct answer: B — Developing the project schedule and network diagrams

• A. Comparing actual performance against the project plan is a monitoring and controlling activity, not a planning activity. It occurs after execution begins to track variances and take corrective action.
• B. Developing the project schedule and network diagrams is a core planning activity in a predictive approach. These tools define the sequence and timing of work before execution starts.
• C. Acquiring and onboarding project team members is part of the Executing process group, not Planning. It involves obtaining and integrating human resources into the team.
• D. Identifying stakeholders and analyzing their interests is part of the Initiating process group. While some planning may occur, it is not a direct schedule planning activity.

Correct answer: B — Product Backlog

• A. Incorrect. The Sprint Backlog is a short-term plan for the current sprint, focusing on one iteration, not the primary document for overall adaptive project controls.
• B. Correct. The Product Backlog is the ordered, evolving list of all work items for the product and is the main artifact used to document and manage scope in an adaptive project. It supports continuous reprioritization and serves as a key control mechanism.
• C. Incorrect. The Definition of Done is a quality agreement that states when work is considered complete, but it is not a project control document for tracking or managing the backlog.
• D. Incorrect. A Burndown Chart is a visual tracking tool that shows remaining work over time, but it is not the primary document for controlling the project. It helps monitor progress, while the Product Backlog documents and organizes the work itself.

Correct answer: C — Definition of Done

• A. Incorrect. Acceptance criteria define the specific conditions a backlog item must meet to be accepted by stakeholders, but they are not the primary project control artifact. They are attached to individual items and do not serve as an overarching control for the project or iteration.
• B. Incorrect. The Sprint Goal provides a shared objective and direction for the sprint, but it is not a formal control document. It guides team decisions but does not establish the quality or completeness criteria needed for project control.
• C. Correct. The Definition of Done (DoD) is a critical control artifact in agile projects. It establishes the criteria that must be met for work to be considered complete, ensuring consistency and quality across all deliverables.
• D. Incorrect. A Product Backlog item is a unit of work or requirement, but it does not serve as a control document. It may have acceptance criteria and priority, but it does not define the overarching control for the project.

Correct answer: B — Product backlog

• A. Incorrect. The Sprint backlog is a subset of the Product backlog containing work planned for a specific sprint. It manages short-term execution, not overall project controls.
• B. Correct. The Product backlog is the ordered list of all desired work for the product, prioritized and continuously refined. It serves as the central artifact for documenting and controlling scope over time in adaptive projects.
• C. Incorrect. A burndown chart tracks remaining work over time to monitor progress. It does not document all work or serve as a control document for scope.
• D. Incorrect. A velocity chart measures work completed per iteration for forecasting. It is a performance metric, not a primary project control document.
• E. Incorrect. A cumulative flow diagram visualizes work in different states to identify bottlenecks. It is a monitoring tool, not the primary artifact for documenting project controls.

Correct answer: C — User story

• A. Incorrect. A phase is a grouping used in predictive or hybrid life cycles, not a standard unit for planning Agile iterations. Agile iterations are typically organized around small pieces of value rather than large sequential stages.
• B. Incorrect. A deliverable is a tangible output or result of work, but it is not the primary item used to plan an Agile iteration. Iteration planning usually breaks work down into user stories and tasks that can be completed within the timebox.
• C. Correct. A user story is a common Agile planning item used to describe a small, valuable piece of functionality from the user's perspective. User stories are prioritized and selected into iterations for delivery.
• D. Incorrect. A work package is a term from traditional scope management and work breakdown structures, not Agile iteration planning. It is generally too large and structured for the iterative planning approach used in Agile.

Correct answer: C — Product backlog

• A. Incorrect. The project charter authorizes the project and provides high-level objectives, but it is not used for planning individual iterations or sprints.
• B. Incorrect. The work breakdown structure (WBS) is a traditional predictive planning tool that decomposes scope into deliverables and tasks. It is not the primary artifact for Agile iteration planning.
• C. Correct. The product backlog is a prioritized list of features, enhancements, and fixes. In Agile, it is the key artifact used to plan iterations (sprints) as teams select items from it based on value and capacity.
• D. Incorrect. The risk register documents identified risks, their analysis, and response plans. While important for project management, it is not used to plan project iterations in Agile.

Correct answer: C — Iterations enable the team to inspect and adapt.

• A. Incorrect. Agile does not rely on detailed upfront planning to prevent changes; instead, it expects change and uses iterative planning to accommodate it.
• B. Incorrect. While iterations provide a timeboxed structure, the scope is not fixed to prevent change. Agile emphasizes flexibility and adaptation over rigid control.
• C. Correct. Iterations give the team regular opportunities to inspect progress, gather feedback, and adapt the plan based on changing needs. This is a core agile practice for managing change effectively.
• D. Incorrect. Deferring changes until the end of the project is characteristic of predictive approaches, not agile. Agile encourages incorporating feedback and change throughout the project lifecycle.

Correct answer: B — Select Story Y because it has a higher value-to-effort ratio.

• A. Incorrect. While absolute business value is important, selecting based solely on it ignores the effort required. This can lead to overcommitment or inefficient use of resources, as the team may not consider the cost of delivery.
• B. Correct. The value-to-effort ratio is a key Agile prioritization metric, balancing benefit against cost. It helps the team maximize delivered value for the least relative effort, ensuring optimal use of capacity.
• C. Incorrect. Sprint length is time-boxed and should not be adjusted to fit selected stories. Doing so disrupts sprint cadence and can lead to scope creep or unrealistic planning. The team should select high-priority work that fits within fixed capacity.
• D. Incorrect. Asking the product owner for more information may be valid if requirements are unclear, but here the team has sufficient data (value and effort) to compare stories. The best choice is to prioritize based on value-to-effort ratio.

Correct answer: B — Could have

• A. Incorrect. 'Critical' describes importance or urgency, but it is not a standard prioritization category in agile frameworks. Prioritization methods like MoSCoW use 'Must have', 'Should have', 'Could have', and 'Won't have', not 'Critical'.
• B. Correct. 'Could have' is a common prioritization label in agile frameworks such as MoSCoW, where it identifies lower-priority items that are desirable but not essential. This makes it the best fit among the options provided.
• C. Incorrect. 'Complex' refers to difficulty of work, not a standard priority category. While complexity can influence planning and sequencing, it is not the classification being asked for here.
• D. Incorrect. 'Costly' describes expense, but it is not a standard agile prioritization label. Cost may affect prioritization decisions, but the term itself does not fit the expected category.

Correct answer: B — After the "must-be" feature but before the "one-dimensional" feature

• A. Incorrect. An 'attractive' feature delights customers but is not the highest priority in the Kano Model. Must-be features address basic expectations and dissatisfaction, so they take precedence over delighters. Prioritizing solely on delight risks missing foundational needs.
• B. Correct. In the Kano Model, features are prioritized in this order: 'must-be' (basic expectations) first, then 'one-dimensional' (linear satisfaction), followed by 'attractive' (delighters). This ensures essential functionality is delivered before enhancements that exceed expectations.
• C. Incorrect. Although an 'attractive' feature is not required for basic functionality, it still adds significant customer value and is not the lowest priority. It is typically prioritized after must-be and one-dimensional features, not at the bottom of the backlog.
• D. Incorrect. 'Attractive' and 'one-dimensional' features have different impacts on satisfaction. One-dimensional features directly increase satisfaction as performance improves, while attractive features are unexpected delights. They are not assigned the same priority in the Kano Model.

Correct answer: D — Business Analyst

• A. Incorrect. A Process Manager oversees and optimizes process execution but does not typically define business requirements or analyze solutions.
• B. Incorrect. A Process Owner is accountable for the design, performance, and governance of a process, but does not focus on documenting business requirements or stakeholder needs.
• C. Incorrect. A Product Owner prioritizes features and manages the product backlog in Agile environments, but is not primarily responsible for business analysis tasks such as requirement definition.
• D. Correct. A Business Analyst is responsible for eliciting, analyzing, and documenting business requirements, analyzing processes, and ensuring solutions align with stakeholder needs.

Correct answer: C — Product Owner

• A. Incorrect. The Process Owner is responsible for managing and improving a specific business process, not for defining product vision or prioritizing the backlog. This role focuses on process efficiency rather than product value.
• B. Incorrect. The Subject Matter Expert (SME) provides specialized knowledge and expertise on a particular topic but does not typically define the product vision or prioritize the backlog. Their role is advisory, not decision-making for the product.
• C. Correct. The Product Owner is accountable for defining the product vision, managing the product backlog, and prioritizing features or user stories to maximize value in an Agile environment. This role represents the customer and ensures the team works on the highest-value items.
• D. Incorrect. An External Stakeholder may provide input, feedback, or requirements but is not responsible for defining the product vision or prioritizing the backlog. Their influence is indirect, and they lack the authority of the Product Owner.

Correct answer: B — Performed primarily during upfront project planning

• A. In predictive (waterfall) projects, business analysis is not conducted incrementally throughout all phases. That approach is characteristic of adaptive or agile methodologies. In waterfall, most analysis is completed upfront before detailed design and development begin.
• B. Correct. In predictive methodologies, business analysis activities are primarily performed during the upfront planning phase. The goal is to gather, analyze, and baseline requirements early so that later phases can follow a defined plan.
• C. Incorrect. Business analysis is not limited to final testing and deployment. While those stages may validate requirements, the core analysis work happens much earlier in the project lifecycle to define scope and requirements.
• D. Incorrect. Business analysis is essential in predictive projects and is not omitted. Development cannot proceed without defined requirements; analysis is critical for defining scope, requirements, and stakeholder needs.

Correct answer: B — Create a product roadmap and facilitate user story mapping sessions

• A. Incorrect. A detailed BRD with formal sign-off is a waterfall practice, not agile. Agile favors iterative, evolving documentation and just enough upfront detail rather than exhaustive specifications.
• B. Correct. A product roadmap provides high-level scope and direction, while user story mapping helps visualize and break down work in an agile context. This aligns with agile principles of collaboration and iterative planning, giving the product owner the needed clarity.
• C. Incorrect. While scope does evolve in agile, simply stating that it is not fixed does not address the product owner's need to understand the high-level scope. The BA should provide a practical technique to define and communicate scope at a high level.
• D. Incorrect. Estimating the entire project upfront contradicts agile's adaptive planning approach. Agile estimation is done incrementally as more information becomes available, typically at the user story or iteration level.

Correct answer: B — Meet with the team to clarify and elaborate on the user story

• A. Incorrect. Agile methods favor just-in-time elaboration and collaboration over comprehensive documentation. Producing a detailed specification for every story contradicts agile principles, slows delivery, and reduces the adaptive nature of agile.
• B. Correct. The BA should facilitate collaboration with the team to clarify the user story and provide just-in-time elaboration as needed. In agile, ongoing conversation and iterative refinement are preferred to ensure shared understanding and alignment with stakeholder needs.
• C. Incorrect. Allowing the team to implement their own interpretation without clarification can lead to inconsistent implementation and rework. Agile requires a common understanding, so the BA should help the team reach that before proceeding.
• D. Incorrect. Escalating to management for enforcement is not an agile approach. Agile teams are self-organizing and should resolve misunderstandings through direct collaboration and communication rather than top-down mandates.

Correct answer: C — Host regular video meetings at a convenient global time and use online tools for updates.

• A. Incorrect. Forcing schedule adjustments ignores time zone constraints and can lead to burnout and resentment. Effective communication should be practical, inclusive, and considerate of global team availability.
• B. Incorrect. Overusing high-priority flags desensitizes recipients and reduces their effectiveness. Urgency should be used appropriately, not as a default for all messages.
• C. Correct. Hosting regular video meetings at a convenient global time ensures real-time collaboration while respecting time zones. Using online tools supports asynchronous updates, keeping everyone informed and engaged.
• D. Incorrect. Personalized daily email summaries can provide updates but lack real-time interaction and may be inefficient or untimely. They do not adequately address time zone challenges or foster collaboration.

Correct answer: B — Suggest discussing the technical details in a dedicated follow-up meeting.

• A. Incorrect. Providing a complete technical response immediately may overwhelm the audience and derail the presentation. High-level presentations should focus on strategic alignment, and CAPM/PMI communication practices emphasize tailoring the message to the stakeholder and context.
• B. Correct. Suggesting a dedicated follow-up meeting allows the technical question to be addressed in the appropriate level of detail without disrupting the presentation. This respects the executive's interest while maintaining focus on the broader audience and keeping the meeting on track.
• C. Incorrect. Ignoring the question can appear dismissive and unprofessional, potentially damaging stakeholder trust and engagement. Good stakeholder communication requires acknowledging questions and responding appropriately, even if the full answer is deferred.
• D. Incorrect. Telling the executive the question is off-topic is unnecessarily dismissive and may damage stakeholder relationships. A better approach is to acknowledge the question and offer a more suitable time or forum for the technical discussion.

Correct answer: C — Encrypted email or a secure project management platform.

• A. Incorrect. Town halls are open to all employees and lack confidentiality, making them unsuitable for sensitive or restricted stakeholder communication.
• B. Incorrect. Mass communications to the entire organization are too broad and do not provide the confidentiality or access control needed for sensitive project information.
• C. Correct. Encrypted email or a secure project management platform provides confidentiality and restricts access to authorized stakeholders, making it appropriate for sensitive information.
• D. Incorrect. Casual chat apps often lack encryption, access controls, and auditability, making them unsuitable for secure or formal stakeholder communication.

Correct answer: B — To communicate strategic direction and planned product evolution.

• A. Incorrect. A product roadmap is a high-level strategic document, not a detailed project schedule or task assignment tool. Detailed schedules and tasks are captured in project plans or work breakdown structures.
• B. Correct. A product roadmap communicates the strategic direction and planned evolution of a product over time. It aligns stakeholders on the vision, goals, and major initiatives.
• C. Incorrect. Customer-reported issues and bugs are tracked in issue logs or defect trackers, not in a product roadmap. While they may influence priorities, they are not the primary purpose.
• D. Incorrect. Technical architecture and system design are documented in architectural diagrams or design specifications. A product roadmap is a strategic planning tool, not a detailed technical document.

Correct answer: B — Features that align with the product vision and provide high value with reasonable effort.

• A. Incorrect. Prioritizing features solely based on effort without considering value can lead to low-impact deliverables. Product roadmaps should balance value, effort, and strategic alignment to support business goals and user needs.
• B. Correct. Product roadmaps prioritize features that align with the product vision, deliver high value, and are feasible with reasonable effort. This ensures the team focuses on the most beneficial work first while keeping delivery realistic and strategic goals met.
• C. Incorrect. Even for important customers, the roadmap should not include every requested feature regardless of cost or strategic fit. Roadmaps must balance stakeholder needs with product strategy, value, and constraints to avoid unsustainable development.
• D. Incorrect. Technical interest may influence implementation choices, but it should not drive roadmap priorities by itself. Roadmap decisions should be based on business value, customer needs, and alignment with the product vision, not solely on what the team finds interesting.

Correct answer: B — Prioritize based on strategic alignment and customer impact, and present to the CEO.

• A. Incorrect. Blindly following a directive without evaluating strategic alignment or business impact is not a best practice. Product managers should balance stakeholder input with data-driven decisions, and the roadmap should reflect strategic priorities and customer needs.
• B. Correct. Prioritizing based on strategic alignment and customer impact ensures the roadmap delivers the most value. Framing the recommendation around outcomes such as reducing churn and presenting it to the CEO demonstrates leadership and informed decision-making.
• C. Incorrect. While team input on feasibility is useful, voting is not a sound basis for roadmap prioritization. Roadmaps should be driven by business strategy and value, not by internal popularity.
• D. Incorrect. Attempting to complete all themes simultaneously typically spreads resources too thin, reducing focus and quality. A roadmap should sequence work based on priority, capacity, and expected value.