IIBA Certified Business Analysis Professional CBAP Exam Practice Test

Answer : C

The CFO's resistance to replacing the older vehicles and suggesting that the truck drivers manually send the truck location from a handheld mobile device every 20 minutes is an opportunity cost. An opportunity cost is the value of the next best alternative that is foregone as a result of making a decision. In this case, the opportunity cost of not replacing the older vehicles is the potential loss of customer satisfaction, retention, and loyalty due to the less accurate and less convenient tracking system. The CFO is choosing to save money on the upfront cost of buying new trucks, but at the expense of losing the competitive advantage and long-term benefits of having a live parcel tracking system.Reference:

IIBA BABOK Guide, Section 10.23, Decision Analysis

Opportunity Cost: Definition, Real-World Examples, How to Calculate, The Balance

What is Opportunity Cost and How to Calculate It, Investopedia

Answer : A

The Delphi technique is a type of requirements elicitation technique that is based on a survey method. The Delphi technique involves sending a series of questionnaires to a group of experts who have knowledge or experience in the domain of the project or the solution. The questionnaires are designed to elicit opinions, ideas, or feedback on the requirements or the issues related to the project or the solution. The responses from the experts are collected and analyzed by a facilitator, who then provides a summary of the results and the areas of agreement or disagreement to the experts. The facilitator also prepares a new questionnaire based on the feedback and sends it back to the experts for another round of responses. This process is repeated until a consensus is reached or a sufficient level of information is obtained. The Delphi technique is useful for gathering requirements from a large and diverse group of stakeholders who are geographically dispersed or have conflicting views. The Delphi technique also helps to reduce the influence of dominant or biased individuals and to encourage honest and independent opinions. The Delphi technique is different from a workshop, which is a type of requirements elicitation technique that involves bringing together a group of stakeholders in a face-to-face or virtual setting to collaborate and exchange information on the requirements or the issues related to the project or the solution. The workshop is facilitated by a moderator, who guides the discussion and ensures the participation and contribution of all the attendees. The workshop is useful for generating a large number of ideas and finding solutions for a specific problem in a short time. The workshop also helps to build rapport and trust among the stakeholders and to resolve conflicts or misunderstandings. The Delphi technique is also different from a round table, which is a type of requirements elicitation technique that involves inviting a group of stakeholders to a formal or informal meeting to share their perspectives and insights on the requirements or the issues related to the project or the solution. The round table is moderated by a leader, who introduces the topic and encourages the dialogue and debate among the participants. The round table is useful for exploring different viewpoints and opinions and for gaining a deeper understanding of the problem and the context. The round table also helps to foster a sense of involvement and ownership among the stakeholders and to identify the areas of agreement or disagreement. The Delphi technique is not a prototyping, which is a type of requirements elicitation technique that involves creating a simplified or partial version of the solution or a component of the solution and presenting it to the stakeholders for feedback. The prototype can be either low-fidelity or high-fidelity, depending on the level of detail and functionality. The prototype is useful for validating and verifying the requirements and for demonstrating the feasibility and usability of the solution. The prototype also helps to reduce the ambiguity and uncertainty of the requirements and to increase the satisfaction and acceptance of the solution.Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, page 180-181.

Top 10 Most Common Requirements Elicitation Techniques, paragraph 9

Software Engineering | Requirements Elicitation - GeeksforGeeks, paragraph 6

Delphi Method Forecasting Definition and How It's Used - Investopedia, paragraph 1

The Delphi Technique - Students 4 Best Evidence, paragraph 1

Answer : B

Videoconferencing is a communication technique that allows business analysts to interact with stakeholders who are not collocated. It enables real-time audio and visual communication, which can facilitate collaboration, feedback, and decision making. Videoconferencing can also help build rapport and trust among stakeholders, as well as reduce travel costs and time.Videoconferencing is one of the many communication techniques that business analysts can use to elicit information and collaborate with stakeholders in different geographical locations1234.Reference:1: How to create a business analysis communication plan - Lucidchart2: Business Analysis Techniques: Eliciting Information and Collaborating with Stakeholders3: Key sets of BA: analysis and communication techniques - Exposit4: Communication strategy for stakeholder engagement -- SustaiNet

Answer : D

Risk governance is the process of establishing organizational checks and balances with a proper segregation of front, back, and middle office functions for effective risk management. Risk governance is the set of roles, responsibilities, policies, procedures, and standards that define how risk management is performed and overseen within an organization. Risk governance helps to ensure that risk management is aligned with the organizational strategy, objectives, and values, and that risk management activities are coordinated, consistent, and transparent across the organization.Risk governance also helps to promote a risk-aware culture and to foster accountability and ownership of risk management among the stakeholders12. A risk response plan is a document that describes the strategies and actions to address the identified and prioritized risks. A risk response plan is the output of the risk analysis process, which evaluates the risks and determines the appropriate responses to them.A risk response plan helps to implement the risk governance policies and procedures, and to execute the risk management plan13. A risk analysis is a process that evaluates the identified and prioritized risks, and determines the appropriate responses to them. A risk analysis is a sub-process of the risk management process, which encompasses risk identification, risk estimation, risk analysis, and risk monitoring and control.A risk analysis helps to develop strategies and actions to avoid, reduce, transfer, or accept the risks, and to allocate resources and contingency reserves for risk management14. A risk management plan is a document that describes how risk management will be performed and controlled throughout the project or the solution lifecycle. A risk management plan is the output of the scope and plan initiation process, which defines the scope, objectives, approach, and deliverables of the risk management process.A risk management plan helps to implement the risk governance policies and procedures, and to guide the risk management activities and decisions15.Reference:

CBAP Handbook

Risk Governance - iiba.org

Risk Response Plan - iiba.org

Risk Analysis - iiba.org

Risk Management Plan - iiba.org

Answer : D

Option D shows the correct use of theincluderelationship between the three use cases. This means that the ''Pass a two-factor authentication'' use case is a mandatory part of both the ''Change system parameters'' and the ''Setup new supervisor'' use cases, and it always occurs whenever either of them is executed. The arrow points from the base use case to the included use case, as per the UML notation. Option C is incorrect because it uses theprotectrelationship, which is a non-standard extension of the UML notation. It indicates that the ''Pass a two-factor authentication'' use case is a security requirement for the other two use cases, but it does not specify how or when it is executed. Options A and B are incorrect because they use theextendrelationship, which means that the ''Pass a two-factor authentication'' use case is an optional extension of the other two use cases, and it only occurs under certain conditions. This does not reflect the requirement that the two-factor authentication is mandatory for both functions.Reference:

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 10: Techniques, pp. 424-425.

[UML 2.5 Specification], Chapter 18: Use Cases, pp. 637-638.

Answer : C

The initiating process group is the one that occurs at the beginning of the project. It involves defining the project scope, objectives, and deliverables, obtaining the project authorization, identifying the key stakeholders, and establishing the project manager's authority. The initiating process group helps to set the vision and direction of the project, and aligns it with the strategic goals of the organization. The initiating process group also ensures that the project is feasible, viable, and desirable, and that it has the necessary support and resources to proceed.Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47

Project Management Process Groups - Villanova University, under Initiating Process Group

The Five Traditional Process Groups Explained - Project Management Academy, under Initiating Phase

Answer : B

Prioritizing requirements by the likelihood of success is a technique that can help build confidence and trust among the project stakeholders, especially if the project is complex, risky, or has a long duration. By delivering some of the requirements that have a high chance of success early in the project, the business analyst can demonstrate the value of the project and the effectiveness of the business analysis process. This can also help reduce resistance to change and increase user satisfaction and adoption. Some of the other factors that can be used to prioritize requirements are business value, urgency, dependency, risk, cost, and effort.Reference:

Certified Business Analysis Professional (CBAP) Handbook, page 6, section 4. Review the Exam Blueprint.

BABOK Guide v3, page 34, section 4.2.3. Prioritize Requirements.