I85PREP
⌘ K
TEST ARCHED study materials
TEST ARCHED study resources

TEST ARCHED practice questions

One question at a time. Build your TEST ARCHED understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Project and Program Fundamentals

In project management, what distinguishes a project from ongoing operations?

  1. A project is managed exclusively by the finance department
  2. A project is temporary and produces a unique product, service, or result Correct answer.
  3. A project is funded only from operating budgets rather than capital budgets
  4. A project is permanent and repeats the same output each cycle

Explanation

A project is a temporary endeavor undertaken to create a unique product, service, or result; its temporary nature means it has a defined start and end. Ongoing operations are repetitive and sustain the business. This temporary-and-unique pairing is the defining contrast used throughout project fundamentals.

Question 2Project and Program Fundamentals

A program is best described as which of the following?

  1. A single large project with a longer schedule than usual
  2. A recurring operational process owned by a functional manager
  3. A group of related projects, subsidiary programs, and program activities managed in a coordinated manner Correct answer.
  4. A temporary organization created only to respond to a legal dispute

Explanation

A program is a group of related projects, subsidiary programs, and program activities managed in a coordinated way to obtain benefits not available from managing them individually. Coordination and aggregated benefit are the key ideas. Size or duration alone does not turn a project into a program.

Question 3Project and Program Fundamentals

Which statement correctly describes the relationship between portfolios and programs?

  1. A portfolio and a program are synonyms in all governance models
  2. A program contains portfolios that are grouped by shared technology
  3. A portfolio contains only programs and never standalone projects
  4. A portfolio is a collection of projects, programs, and subsidiary portfolios managed as a group to achieve strategic objectives Correct answer.

Explanation

A portfolio is a collection of projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives. Portfolios may include standalone projects as well as programs. Programs sit within portfolios and focus on coordinated benefits rather than overall strategic alignment.

Question 4Project and Program Fundamentals

What is the primary purpose of a project management office (PMO) in an organization?

  1. To standardize project-related governance processes and facilitate sharing of resources, methodologies, tools, and techniques Correct answer.
  2. To personally execute all project deliverables on behalf of project managers
  3. To audit only the financial statements of completed projects
  4. To replace the project sponsor in approving all scope changes

Explanation

A PMO standardizes governance processes and facilitates sharing of resources, methodologies, tools, and techniques across projects. Its form can range from supportive to controlling to directive. It supports project delivery rather than performing the project work itself.

Question 5Project and Program Fundamentals

Which document formally authorizes the existence of a project and gives the project manager authority to apply organizational resources?

  1. The project management plan
  2. The benefits management plan
  3. The project charter Correct answer.
  4. The stakeholder register

Explanation

The project charter formally authorizes the project and empowers the project manager to apply organizational resources to project activities. It is typically issued by the sponsor or initiating authority. Other planning documents are developed after this authorization.

Question 6Project and Program Fundamentals

A stakeholder has high power to influence the project and high interest in its outcome. Which engagement approach is most appropriate?

  1. Keep satisfied by addressing concerns without heavy involvement
  2. Monitor with minimal effort and occasional status updates
  3. Ignore until the stakeholder raises a concern
  4. Manage closely with active engagement and regular communication Correct answer.

Explanation

Stakeholders with high power and high interest should be managed closely, meaning they are actively engaged and receive regular, substantive communication. Their combination of influence and concern means their needs can materially affect the project. Low-effort approaches suit stakeholders whose power or interest is low.

Question 7Project and Program Fundamentals

Which of the following is an example of a project constraint rather than an assumption?

  1. A fixed regulatory deadline that the project must meet Correct answer.
  2. An expectation that the sponsor will approve the design in one review
  3. A forecast that user adoption will reach eighty percent
  4. A belief that a key vendor will deliver on time

Explanation

A constraint is a limiting factor that affects project execution, such as a fixed regulatory deadline. Assumptions are factors considered true for planning purposes without proof. Beliefs, forecasts, and expectations are therefore assumptions, while the deadline is a binding limit.

Question 8Project and Program Fundamentals

Which knowledge area is primarily concerned with identifying, evaluating, and managing the people and organizations that can affect or be affected by the project?

  1. Project stakeholder management Correct answer.
  2. Project schedule management
  3. Project procurement management
  4. Project quality management

Explanation

Stakeholder management covers identifying stakeholders, planning engagement, and managing and monitoring engagement. Procurement deals with acquiring goods and services, quality with meeting requirements, and schedule with timing. The people-and-organizations focus points specifically to stakeholder management.

Question 9Project and Program Fundamentals

A project manager is developing the project management plan and needs to define how scope will be validated and controlled. Which plan component is the most direct source for this information?

  1. The resource management plan
  2. The communications management plan
  3. The scope management plan Correct answer.
  4. The risk management plan

Explanation

The scope management plan describes how scope will be defined, developed, monitored, controlled, and validated. It is a subsidiary component of the project management plan. Resource, communications, and risk plans address different knowledge areas and do not specify scope validation procedures.

Question 10Project and Program Fundamentals

A project team is decomposing deliverables into progressively smaller components until the work can be reliably estimated and managed. What is this technique called?

  1. Resource leveling
  2. Critical path analysis
  3. Work breakdown structure decomposition Correct answer.
  4. Rolling wave planning

Explanation

Decomposition is the technique of breaking deliverables down into smaller, more manageable work packages within a work breakdown structure. It continues until the work can be estimated and controlled at a reasonable cost. Rolling wave planning is iterative elaboration over time, and the other options relate to schedule and resources.

Question 11Project and Program Fundamentals

A key supplier fails to deliver a component on the agreed date, delaying a critical activity. Which project management process area most directly addresses this situation?

  1. Develop project charter, because the baseline must be reauthorized
  2. Manage quality, because the component is defective
  3. Control procurements, because supplier performance is at issue Correct answer.
  4. Control schedule, because the activity slipped

Explanation

Control procurements monitors contract performance and manages supplier relationships, including delivery failures. While the schedule is affected, the root cause is supplier performance under an agreement. Quality management addresses defects, and the charter is not reissued for schedule slippage.

Question 12Project and Program Fundamentals

What is the main difference between a predictive (waterfall) life cycle and an adaptive (agile) life cycle?

  1. Predictive life cycles cannot use a work breakdown structure
  2. Adaptive life cycles deliver value in iterative increments and welcome changing requirements Correct answer.
  3. Predictive life cycles do not require a project manager
  4. Adaptive life cycles forbid any upfront planning

Explanation

Adaptive life cycles deliver work in iterative increments and expect requirements to evolve, while predictive life cycles plan most scope early and manage change formally. Both can use a work breakdown structure and both require management. Adaptive approaches still include planning, just at different levels of detail and timing.

Question 13Project and Program Fundamentals

A project has an earned value of 40,000, a planned value of 50,000, and an actual cost of 45,000. What does the schedule performance index indicate?

  1. The project is ahead of schedule
  2. The project is behind schedule Correct answer.
  3. The schedule cannot be assessed without the budget at completion
  4. The project is on schedule

Explanation

The schedule performance index equals earned value divided by planned value, here 40,000 divided by 50,000, or 0.80. A value below 1.0 means less work was completed than planned, so the project is behind schedule. Budget at completion is not required to compute this index.

Question 14Project and Program Fundamentals

In a project network diagram, what does the critical path represent?

  1. The sequence of activities with the longest total duration that determines the shortest possible project duration Correct answer.
  2. The path that contains only activities assigned to the project manager
  3. The path with the most activities regardless of their durations
  4. The sequence of activities with the lowest total cost

Explanation

The critical path is the longest-duration path through the network and therefore determines the shortest possible project duration. Activities on it have zero or negative total float in most cases. Counting activities or costs does not define criticality.

Question 15Project and Program Fundamentals

A risk has a high probability of occurring and a severe potential impact on cost. Which response strategy is being applied when the team purchases insurance to cover the loss?

  1. Accept
  2. Transfer Correct answer.
  3. Exploit
  4. Avoid

Explanation

Transferring a risk shifts the financial consequence to a third party, commonly through insurance or warranties. Avoidance eliminates the threat, exploitation pursues an opportunity, and acceptance retains the risk. Insurance does not remove the risk event but shifts its financial burden.

Question 16Project and Program Fundamentals

Which estimating technique uses historical data from similar past projects to estimate the duration or cost of the current project?

  1. Parametric estimating
  2. Analogous estimating Correct answer.
  3. Bottom-up estimating
  4. Three-point estimating

Explanation

Analogous estimating uses historical data from a similar project as the basis for the current estimate. It is generally faster and less costly but less accurate than detailed methods. Parametric and bottom-up methods rely on unit rates or component-level aggregation, and three-point uses weighted scenarios.

Question 17Project and Program Fundamentals

A project manager documents that a deliverable must be accepted by the client before final payment is released. Which project document most appropriately records this requirement?

  1. The issue log
  2. The acceptance criteria within the scope statement or requirements documentation Correct answer.
  3. The risk register
  4. The team charter

Explanation

Acceptance criteria define the conditions that must be met for a deliverable to be accepted and are recorded in scope and requirements documentation. They give the basis for scope validation. The risk register, team charter, and issue log address different concerns.

Question 18Project and Program Fundamentals

Which statement best describes the role of the project sponsor?

  1. The sponsor provides resources and support, champions the project, and approves key decisions Correct answer.
  2. The sponsor is always a member of the PMO
  3. The sponsor performs the technical work and reports to the project manager
  4. The sponsor manages daily task assignments for the team

Explanation

The sponsor authorizes the project, provides resources and executive support, and champions it within the organization. Sponsors also approve key decisions such as the charter and major changes. They do not typically perform technical work or assign daily tasks.

Question 19Project and Program Fundamentals

A project manager notices that two team members disagree about who owns a specific deliverable. Which interpersonal and team skill is most relevant to resolving this?

  1. Conflict management Correct answer.
  2. Cost aggregation
  3. Configuration management
  4. Procurement negotiation

Explanation

Conflict management addresses disagreements among team members and helps reach a productive resolution. Ownership disputes are interpersonal conflicts that benefit from a defined resolution approach. Cost, procurement, and configuration activities do not directly address role disagreements.

Question 20Project and Program Fundamentals

Which of the following best illustrates the concept of progressive elaboration?

  1. All risks are identified once during planning and then closed
  2. The project charter is rewritten at the end of each phase
  3. High-level requirements are refined into greater detail as more information becomes available Correct answer.
  4. The project scope is fully defined at initiation and never revised

Explanation

Progressive elaboration means developing project details in increments as information improves over time. Early documents are high-level and become more detailed as the project advances. It does not mean the charter is repeatedly rewritten or that risk identification happens only once.

Question 21Project and Program Fundamentals

A project manager is comparing bids from three vendors and wants to ensure the evaluation criteria were defined before proposals were received. Which principle does this support?

  1. Fair and transparent source selection Correct answer.
  2. Quality assurance
  3. Resource leveling
  4. Cost-plus contracting

Explanation

Defining evaluation criteria before receiving proposals supports fair, transparent source selection and reduces bias. It ensures all sellers are assessed against the same standard. Contract type, scheduling, and quality processes are separate concerns.

Question 22Project and Program Fundamentals

An organization runs several unrelated initiatives that together support a single strategic goal, and leadership wants to prioritize investment across them. Which management level is designed for this?

  1. Program management, because the initiatives share a common outcome
  2. Portfolio management, because it prioritizes components against strategic objectives Correct answer.
  3. Operations management, because the initiatives are recurring
  4. Project management, because each initiative must optimize its own schedule

Explanation

Portfolio management selects and prioritizes the mix of components that best achieves strategic objectives, including unrelated initiatives. Programs coordinate related projects for shared benefits, which does not fit initiatives described as unrelated. Project management focuses on delivering an individual project.

Question 23Project and Program Fundamentals

A project is on schedule but has a cost performance index of 0.85 and a schedule performance index of 1.0. Which interpretation is most defensible?

  1. Earned value cannot be interpreted without the estimate at completion
  2. The project is behind schedule and needs schedule compression
  3. The project is under budget and should release contingency funds
  4. The project is spending more than planned for the work completed and needs cost corrective action Correct answer.

Explanation

A cost performance index below 1.0 means the project is getting less value per unit of cost than planned, indicating overspending relative to work performed. A schedule performance index of 1.0 indicates the schedule is on track. Corrective action should target cost performance rather than schedule compression.

Question 24Project and Program Fundamentals

During scope validation, a client rejects a deliverable that meets all documented requirements but does not match an undocumented expectation. What is the most appropriate project management response?

  1. Accept the deliverable as complete because documented requirements were met
  2. Immediately revise the deliverable without documentation to preserve the relationship
  3. Escalate to terminate the project because acceptance failed
  4. Record the gap, assess whether the expectation is a legitimate change, and process it through change control Correct answer.

Explanation

Scope validation compares deliverables to documented acceptance criteria; an undocumented expectation is a potential change, not automatic nonconformance. The gap should be recorded and evaluated through integrated change control so impacts on scope, schedule, and cost are assessed. Uncontrolled rework or termination is disproportionate.

Question 25Project and Program Fundamentals

A project manager identifies that a key resource is available only during a narrow window, which constrains scheduling options. Which scheduling concept does this illustrate?

  1. A risk that must be transferred to a vendor
  2. An assumption that can be ignored during scheduling
  3. A quality requirement for the deliverable
  4. A resource constraint that may require resource leveling or schedule adjustment Correct answer.

Explanation

Limited resource availability during a specific window is a resource constraint that can force schedule adjustments such as resource leveling or resequencing. Constraints limit the options available to the scheduler. It is not an assumption to ignore, a transferable risk, or a quality requirement.

Question 26Project and Program Fundamentals

Which document formally authorizes a project and names the project manager?

  1. The work breakdown structure
  2. The project charter Correct answer.
  3. The stakeholder register
  4. The project management plan

Explanation

The project charter is the document issued by the sponsor or initiating authority that formally authorizes the project and identifies the project manager. The project management plan describes how the project will be executed and controlled, while the WBS and stakeholder register are later planning outputs. Without a charter, the project manager lacks formal authority to apply resources.

Question 27Project and Program Fundamentals

A project manager is defining how requirements will be collected, documented, and managed throughout the project. Which subsidiary plan is being created?

  1. The requirements management plan Correct answer.
  2. The scope management plan
  3. The quality management plan
  4. The communications management plan

Explanation

The requirements management plan describes how requirements will be elicited, analyzed, documented, and managed, including configuration and traceability. The scope management plan describes how scope will be defined, validated, and controlled. The quality and communications plans address quality assurance and information flow, not requirement lifecycle management.

Question 28Project and Program Fundamentals

Which statement accurately distinguishes a project from ongoing operations?

  1. A project is temporary and produces a unique product, service, or result, whereas operations are ongoing and repetitive. Correct answer.
  2. A project is ongoing and repetitive, whereas operations are temporary and produce unique outputs.
  3. A project is always funded by external customers, whereas operations are always funded internally.
  4. A project has no defined start or end date, whereas operations are constrained by a fixed schedule.

Explanation

A project is a temporary endeavor undertaken to create a unique product, service, or result, with a definite beginning and end. Operations are ongoing, repetitive activities that sustain the business. Funding source and schedule constraints do not define the distinction.

Question 29Project and Program Fundamentals

A project manager is creating a hierarchical decomposition of the total scope of work to be performed by the project team. What is this technique called?

  1. Resource leveling
  2. Network diagramming
  3. Earned value analysis
  4. Work breakdown structure creation Correct answer.

Explanation

Work breakdown structure creation is the process of decomposing the total scope into manageable work packages. Network diagramming sequences activities, resource leveling adjusts the schedule for resource constraints, and earned value analysis measures performance. Only WBS creation produces the hierarchical scope decomposition.

Question 30Project and Program Fundamentals

A project manager wants to estimate project duration by applying a weighted average of optimistic, most likely, and pessimistic estimates to each activity. Which estimating technique is being used?

  1. Three-point estimating Correct answer.
  2. Analogous estimating
  3. Parametric estimating
  4. Bottom-up estimating

Explanation

Three-point estimating uses optimistic, most likely, and pessimistic values to calculate an expected duration or cost, often through a weighted average such as the PERT formula. Analogous estimating uses historical similarity, parametric estimating uses statistical relationships, and bottom-up estimating aggregates detailed lower-level estimates.

Question 31Project and Program Fundamentals

During project execution, a project manager notices that a team member consistently completes tasks late, affecting the schedule. Which project management process is most directly concerned with tracking this performance?

  1. Develop project charter
  2. Monitor and control project work Correct answer.
  3. Acquire project team
  4. Plan quality management

Explanation

Monitor and control project work is the process of tracking, reviewing, and reporting overall project progress and performance against the plan. It identifies variances such as late task completion and triggers corrective action. The other processes occur earlier and do not directly track execution performance.

Question 32Project and Program Fundamentals

A project manager is implementing a change control process. Which document defines the process for submitting, evaluating, and approving changes to the project?

  1. The project charter
  2. The change management plan Correct answer.
  3. The stakeholder engagement plan
  4. The risk register

Explanation

The change management plan describes how changes will be requested, assessed, approved, and implemented, including the roles of the change control board. The project charter authorizes the project, the stakeholder engagement plan addresses stakeholder involvement, and the risk register records identified risks. Only the change management plan defines the change control process.

Question 33Project and Program Fundamentals

A project manager is leading a team meeting to define how the team will make decisions, resolve conflicts, and share information. Which document is being created?

  1. The resource management plan
  2. The communications management plan
  3. The project charter
  4. The team charter Correct answer.

Explanation

The team charter establishes ground rules, decision-making processes, conflict resolution approaches, and communication norms for the project team. The project charter authorizes the project, while the resource and communications management plans describe broader planning for resources and information. The team charter specifically captures the team's operating agreements.

Question 34Project and Program Fundamentals

A project manager wants to ensure that the project meets the needs of the business while also satisfying stakeholder expectations. Which document provides the highest-level business justification and success criteria?

  1. The issue log
  2. The requirements traceability matrix
  3. The business case Correct answer.
  4. The project management plan

Explanation

The business case establishes the business justification for the project, including the problem or opportunity, expected benefits, and high-level success criteria. The project management plan describes how the project will be executed, while the traceability matrix and issue log are supporting documents. The business case is used to authorize the project and align it with strategic objectives.

Question 35Project and Program Fundamentals

A project manager is developing a strategy to ensure that stakeholders remain engaged throughout the project. Which process is being performed?

  1. Plan stakeholder engagement Correct answer.
  2. Identify stakeholders
  3. Manage stakeholder engagement
  4. Monitor stakeholder engagement

Explanation

Plan stakeholder engagement is the process of developing approaches to involve stakeholders based on their needs, interests, and potential impact. Manage stakeholder engagement involves executing those strategies, while monitoring tracks their effectiveness. Identifying stakeholders is the earlier process of determining who the stakeholders are.

Question 36Project and Program Fundamentals

A project manager is using a method that delivers work in small, incremental releases and welcomes changing requirements. Which life cycle is being used?

  1. Adaptive Correct answer.
  2. Iterative
  3. Predictive
  4. Incremental

Explanation

An adaptive life cycle is one that is designed to respond to high levels of change and uncertainty, often using short iterations and frequent feedback. Predictive life cycles plan the work in detail upfront and resist changes. Iterative and incremental life cycles are related but do not inherently embrace changing requirements to the same degree.

Question 37Project and Program Fundamentals

A project manager is calculating the total planned value of all work scheduled to be completed by a specific date. Which earned value metric is being determined?

  1. Earned value (EV)
  2. Planned value (PV) Correct answer.
  3. Actual cost (AC)
  4. Cost variance (CV)

Explanation

Planned value is the authorized budget assigned to scheduled work at a given point in time. Earned value measures the value of work actually performed, actual cost measures the money spent, and cost variance is the difference between earned value and actual cost. Planned value reflects the planned schedule baseline.

Question 38Project and Program Fundamentals

A project manager is facilitating a meeting to determine the root cause of a recurring defect. Which tool or technique is most appropriate?

  1. A histogram
  2. A cause-and-effect diagram Correct answer.
  3. A Pareto chart
  4. A control chart

Explanation

A cause-and-effect diagram, also called a fishbone or Ishikawa diagram, is used to identify and organize potential root causes of a problem. A control chart monitors process stability over time, a Pareto chart prioritizes issues by frequency, and a histogram displays data distribution. Only the cause-and-effect diagram specifically structures root cause analysis.

Question 39Project and Program Fundamentals

A project manager is analyzing a network diagram to determine the longest path through the project. What is the significance of this path?

  1. It shows the activities that have no dependencies.
  2. It represents the sequence of activities with the most float.
  3. It indicates the path with the lowest risk.
  4. It determines the shortest possible project duration. Correct answer.

Explanation

The longest path through the network diagram is the critical path, which determines the shortest possible project duration because any delay on this path delays the entire project. It typically has zero or negative total float. The other options mischaracterize the critical path.

Question 40Project and Program Fundamentals

A project manager is evaluating whether to buy a software component or develop it in-house. Which analysis technique is being used?

  1. Cost-benefit analysis
  2. Reserve analysis
  3. Value engineering
  4. Make-or-buy analysis Correct answer.

Explanation

Make-or-buy analysis is used to determine whether work should be performed internally or acquired from an external source, considering factors such as cost, capacity, and risk. Cost-benefit analysis compares the costs and benefits of alternatives, value engineering seeks to improve value, and reserve analysis determines contingency buffers. The specific decision of internal versus external sourcing is make-or-buy.

Question 41Requirements and Scope Definition

In requirements engineering, which characteristic distinguishes a functional requirement from a non-functional requirement?

  1. A functional requirement applies only to hardware; a non-functional requirement applies only to software.
  2. A functional requirement specifies a behavior or service the system must perform; a non-functional requirement constrains qualities or attributes such as performance or security. Correct answer.
  3. A functional requirement is always written by the customer; a non-functional requirement is always written by the developer.
  4. A functional requirement describes a quality attribute; a non-functional requirement describes a behavior or service.

Explanation

Functional requirements state what the system must do, such as calculating a total or sending a notification. Non-functional requirements qualify those behaviors by constraining quality attributes like availability, latency, or usability. The other pairings invert or misattribute the definitions.

Question 42Requirements and Scope Definition

A stakeholder states: 'The system should be easy to use.' Why is this a poor requirement as written?

  1. It is verifiable because usability is universally understood.
  2. It is a functional requirement and functional requirements must be verbal.
  3. It is too long and should be split into multiple sentences.
  4. It is ambiguous and not measurable, so it cannot be objectively tested. Correct answer.

Explanation

A good requirement must be verifiable, meaning a test can determine whether it is met. 'Easy to use' lacks a measurable criterion such as task completion time or error rate, so different reviewers would judge it differently. Length and sentence count are not the issue.

Question 43Requirements and Scope Definition

Which activity in requirements engineering is primarily concerned with discovering what stakeholders need from a proposed system?

  1. Requirements management
  2. Requirements validation
  3. Requirements elicitation Correct answer.
  4. Requirements traceability

Explanation

Elicitation is the discovery activity: interviewing, observing, and workshopping with stakeholders to surface needs and constraints. Validation checks that stated requirements are correct and complete, while management and traceability handle change and linkage.

Question 44Requirements and Scope Definition

What is the primary purpose of defining the system boundary during scope definition?

  1. To estimate the total project cost before requirements are gathered.
  2. To assign developers to specific modules of the codebase.
  3. To choose the programming language for implementation.
  4. To decide which requirements are in scope for the system and which belong to its environment. Correct answer.

Explanation

The system boundary separates what the system under development will do from what external actors, systems, or adjacent projects handle. Clarifying it prevents scope creep and duplicated responsibility. Cost, staffing, and technology choices follow from scope but are not its purpose.

Question 45Requirements and Scope Definition

A requirement reads: 'The system shall allow a registered user to reset a password via email within 30 seconds.' Which pair of attributes does this requirement best exemplify?

  1. A user interface guideline combined with a data constraint.
  2. A functional behavior combined with a measurable performance constraint. Correct answer.
  3. A business rule combined with a legal constraint.
  4. A non-functional constraint combined with a design constraint.

Explanation

The reset capability is a functional behavior, and the 30-second limit is a quantified performance constraint attached to it. Combining both in one statement is acceptable when the constraint is directly tied to the behavior. The other options mislabel the nature of the two parts.

Question 46Requirements and Scope Definition

Why is traceability from requirements to test cases valuable during scope definition and later phases?

  1. It guarantees the project will finish on schedule.
  2. It eliminates the need for stakeholder review.
  3. It automatically generates source code from requirements.
  4. It shows which requirements are covered by verification and exposes gaps or orphan tests. Correct answer.

Explanation

Traceability links each requirement to design elements and test cases, making coverage visible. Gaps, where a requirement has no test, and orphans, where a test maps to no requirement, can then be identified. It supports but does not replace review, scheduling, or implementation.

Question 47Requirements and Scope Definition

Which statement best describes the difference between a goal and a requirement?

  1. A goal is verifiable and testable, while a requirement is aspirational and vague.
  2. A goal is a high-level, often qualitative intention, while a requirement is a specific, verifiable statement of what the system must do. Correct answer.
  3. A goal and a requirement are identical and used interchangeably in all methodologies.
  4. A goal applies only to business stakeholders, while a requirement applies only to technical staff.

Explanation

Goals capture broad intentions such as 'reduce manual data entry' and are refined into requirements that can be tested. Requirements are precise enough for design and verification. The other options invert, restrict, or conflate the two concepts.

Question 48Requirements and Scope Definition

A project team uses a use case diagram to show actors and their interactions with the system. What does this diagram primarily help define?

  1. The version control branching strategy for the codebase.
  2. The non-functional performance budget for each actor.
  3. The functional scope in terms of who uses the system and which services they invoke. Correct answer.
  4. The internal database schema and table relationships.

Explanation

A use case diagram identifies external actors and the services the system provides to them, which frames functional scope. It does not specify internal data structures, performance budgets, or development tooling. It is a communication aid for scope, not a design artifact.

Question 49Requirements and Scope Definition

During a requirements workshop, two departments claim ownership of the same approval workflow. What is the most appropriate first step to resolve the scope conflict?

  1. Escalate immediately to the legal department for arbitration.
  2. Document the conflict, identify the authoritative decision-maker, and negotiate a single agreed scope. Correct answer.
  3. Implement both versions and let users decide at runtime.
  4. Remove the workflow from scope entirely to avoid disagreement.

Explanation

Conflicting stakeholder claims are resolved through structured negotiation with the party empowered to decide. Recording the conflict preserves traceability and ensures a documented resolution. Building duplicates or dropping needed functionality creates larger problems later.

Question 50Requirements and Scope Definition

A team decomposes a large system into a set of features for an incremental release. Which principle best keeps the defined scope coherent?

  1. Each increment should deliver a vertical slice of value that can be validated with stakeholders. Correct answer.
  2. Each increment should be defined solely by the number of story points it contains.
  3. Each increment should deliver all database tables before any user-facing feature.
  4. Each increment should avoid stakeholder review until the final release.

Explanation

Vertical slices deliver end-to-end value that stakeholders can review, which validates scope early and reduces risk. Horizontal technical layers and point totals alone do not demonstrate value. Deferring review until the end concentrates risk.