IIBA Updated CBAP Exam Questions and Answers by jai

 A constraint is a factor that limits the options or the performance of the project or the solution. Constraints are usually imposed by external factors, such as laws, regulations, standards, policies, resources, time, or budget. Constraints can affect the feasibility, desirability, and suitability of the solution, and may require trade-offs or compromises among the requirements. A constraint is different from a requirement, which is a condition or capability that the solution must have or meet to satisfy the stakeholder needs and expectations123.

In this question, the $300,000 represents a constraint, as it is a factor that limits the options or the performance of the solution. The customer demands that the solution should not cost more than $300,000 to implement and support for one year, which means that the solution must fit within this budget constraint. This constraint may affect the choice of technologies, processes, or features that the solution can include, and may require prioritizing or eliminating some requirements to meet the budget limit. References: 1: BABOK® Guide v3, section 3.4.2 Assess Capability Gaps, page 70 2: CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 109 3: Business Analysis Techniques: Identifying Constraints, page 24

 User classes, profiles, or roles are model types that categorize and describe the people who directly interact with a solution. They help to identify the different types of users, their characteristics, needs, preferences, and behaviors. They also help to define the requirements, features, and functions that are relevant for each user group. User classes, profiles, or roles can be represented in various ways, such as personas, user stories, use cases, or user interface prototypes12. References:

User Classes, Profiles, and Roles

User Modeling: Definition, Methods, and Examples

 Requirements elicitation is not a business analysis planning and monitoring approach, but a business analysis task that involves identifying and documenting the needs and expectations of stakeholders. Business analysis planning and monitoring is the knowledge area that covers the tasks of defining the business analysis approach, planning the business analysis activities, managing the business analysis performance, and communicating the business analysis information. The other three options are examples of techniques that can be used in business analysis planning and monitoring, such as structured walkthroughs for validating the business analysis approach, decision analysis for selecting the best solution option, and process modeling for defining the business analysis process. References: BABOK Guide, Business Analysis Planning and Monitoring, Requirements Elicitation and Collaboration

 According to the BABOK® Guide, conflicts among stakeholders are inevitable and must be resolved before formal approval of the requirements can be obtained. The business analyst is responsible for facilitating the resolution of conflicts by using various techniques such as problem-solving, negotiation, or escalation. The business analyst should not make the decision for the stakeholders, nor should the decision be based on seniority or deferred until later. References: BABOK® Guide v3, section 4.5.5, page 142; CBAP® Handbook, section 4.4, page 6.