Which of the following can be used to determine if requirements align to the product's objectives?

Context diagrams are a technique that can be used to determine if requirements align to the

product’s objectives. Context diagrams are a technique that involves creating a visual representation

of the product and its interactions with its environment, such as other systems, processes, or

stakeholders. Context diagrams can help to define and clarify the scope, boundaries, and interfaces

of the product. Context diagrams can also help to verify that the requirements are consistent and

compatible with the product’s objectives and value proposition. Five Whys is not a technique that

can be used to determine if requirements align to the product’s objectives. Five Whys is a technique

that involves asking a series of why questions to identify the root cause of a problem or an effect.

Five Whys can help to understand and resolve the underlying issues or needs that drive the

requirements, but it does not directly compare or evaluate the requirements against the product’s

objectives. Activity network diagrams are not a technique that can be used to determine if

requirements align to the product’s objectives. Activity network diagrams are a tool that involves

creating a graphical representation of the sequence and dependencies of the activities or tasks in a

project or a process. Activity network diagrams can help to plan and manage the schedule,

resources, and risks of a project or a process, but they do not depict or assess the requirements or

the product’s objectives. Business use cases are not a technique that can be used to determine if

requirements align to the product’s objectives. Business use cases are a tool that involves describing

and documenting how a stakeholder interacts with a system or a solution to achieve a specific goal or

outcome. Business use cases can help to specify and communicate the functionality and behavior of

a system or a solution, but they do not measure or validate the requirements or the product’s

objectives. Reference: Business Analysis for Practitioners: A Practice Guide 1, page 78-79; PMI

Professional in Business Analysis (PMI-PBA)® Examination Content Outline 2, page 16.