An atomic requirement is one that is self-contained and can be understood independently of other requirements or designs. It encapsulates a single piece of functionality or a single need without reference to other requirements. This characteristic ensures that the requirement can be considered, implemented, and tested on its own merits. Atomic requirements are essential for clear communication, effective analysis, and traceability throughout the project lifecycle.
The concept of atomic requirements is discussed in various business analysis resources and is aligned with the guidelines provided by the International Institute of Business Analysis (IIBA). It is a fundamental aspect of creating clear and effective requirements documentation123.

Requirements that are good candidates for reuse are those that are not tied to a specific tool, technology, or system. These requirements are generally applicable across various contexts and can be used in multiple projects without significant changes. They are typically high-level business requirements that describe what the business needs without prescribing how to achieve it. This makes them flexible and adaptable to different situations, which is essential for reuse.
The concept of reusable requirements is discussed in the context of Business Analysis, where it is emphasized that requirements should be general enough to apply to multiple situations while still being specific enough to provide value. They should also be stable, meaning they are unlikely to change over time1.

The correct answer is C. BABOK's Risk Analysis and Management technique states that each risk can be described in a risk register that supports the analysis of risks and plans for addressing them. In practice, a risk register is used to record risks and help evaluate and prioritize them based on factors such as likelihood and impact, so that response efforts can be directed appropriately.
Option A is incorrect because a risk register does not automatically eliminate any category of risk. Its purpose is to document, analyze, and support response planning for risks.
Option B is incorrect because the register is not intended to focus only on one type of risk, such as highly impactful but unlikely risks. It is meant to provide a structured basis for considering all relevant risks.
Option D is incorrect because risks are not categorized randomly. Business analysis relies on structured assessment so that risk decisions are based on meaningful criteria, especially probability and impact.

When requirements express contractual obligations, acceptance criteria are necessary. These criteria ensure that the requirements meet the agreed-upon standards and conditions set forth in the contract. They provide a clear and measurable way to determine whether the requirements have been met satisfactorily. Acceptance criteria are used to evaluate whether the solution fulfills the contract's terms, and they form the basis for the formal acceptance of the project's deliverables. References: The BABOK Guide discusses the importance of acceptance criteria, especially when dealing with requirements that have contractual implications, ensuring that the deliverables meet the predefined standards and are accepted by the stakeholders1.

The correct answer is C. Approval of requirements and designs requires stakeholder agreement. The business analyst should present the requirements and designs to the appropriate stakeholders, support discussion, resolve concerns, and obtain agreement through the defined governance process. Option A is wrong because approval cannot be based only on the analyst's personal judgment, especially for a regulated and customer- facing solution such as mobile banking. Option B is wrong because developers may contribute technical input, but they do not replace stakeholder approval. Option D is incomplete because submitting documents to a project manager does not necessarily obtain stakeholder agreement. The best approach is collaborative review and feedback with the decision makers and relevant stakeholders.