Exam CBAP topic 1 question 481 discussion

i guess ans is C. non-functional requirements Explanation-Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs. (From Google)

Requirements at the highest level are best suited for re-use therefore the answer is B= Business Requirements

Non-Functional requirements are often good candidates for reuse in multiple change initiatives because they typically define system qualities such as performance, security, scalability, reliability, and usability. These types of requirements are often applicable across different projects or initiatives, regardless of the specific business functionality being implemented.

In general, non-functional requirements are always strong candidates for reuse. And here is mentioned about deployments, so it's non-functional requirements obviously.

B. Business requirements Business requirements, when clearly named, defined, and stored in a manner that makes them easily retrievable, can be reused within the current initiative, within similar initiatives, within similar departments, and throughout the entire organization, as stated in BABOK. Requirements at higher levels of abstraction, such as business requirements, tend to be more reusable compared to those tied to specific solutions or organizational structures. Therefore, business requirements are potential candidates for reuse in multiple upcoming change initiatives. Pg 85

C is easy to reuse

Babok pg 85. Requirements at high levels of abstraction may be written with limited reference to specific solutions. Requirements that are represented in a general manner, without direct ties to a particular tool or organizational structure, tend to be more reusable. These requirements are also less subject to revision during a change. As requirements are expressed in more detail, they become more tightly associated with a specific solution or solution option. Specific references to applications or departments limit the reuse of requirements and designs across an organization. Requirements that are intended for reuse reflect the current state of the organization. Stakeholders validate the proposed requirements for reuse before they can be accepted into a change.

Babok pg 85. Requirements at high levels of abstraction may be written with limited reference to specific solutions. Requirements that are represented in a general manner, without direct ties to a particular tool or organizational structure, tend to be more reusable. These requirements are also less subject to revision during a change. As requirements are expressed in more detail, they become more tightly associated with a specific solution or solution option. Specific references to applications or departments limit the reuse of requirements and designs across an organization. Requirements that are intended for reuse reflect the current state of the organization. Stakeholders validate the proposed requirements for reuse before they can be accepted into a change.

Also BABOK Page 303,44,16 ans-non-functional

pls check babok v3 page 44 and page 16

Ans is Business Requirement

I believe it is B - Business requirements: statements of goals, objectives, and outcomes that describe why a change has been initiated. They can apply to the whole of an enterprise, a business area, or a specific initiative. They are most general of all other types, doesn't describe the solution or current stakeholders needs.