Pass the IIBA Certified Business Analysis Professional CBAP Questions and answers with ExamsMirror

The BA should ensure the business needs are articulated from the enterprise perspective, because this will help to align the needs with the strategic goals and objectives of the organization, and to ensure the needs are relevant, feasible, and beneficial for the enterprise as a whole. The other options are not the primary focus of the BA at this stage of defining the business opportunity. While traceability, solution description, and risk assessment are important aspects of business analysis, they are more relevant for later stages of the business analysis process, such as requirements analysis, solution design, and solution evaluation. References: CBAP Handbook, CBAP Study Guide, BABOK Guide

Compromising is a conflict resolution technique that requires that all parties in the conflict must give up something in order to reach a mutually acceptable solution. Compromising involves finding a middle ground or a trade-off that satisfies some of the interests or needs of each party, but not all of them. Compromising is useful when the parties have equal power and the conflict is not very important or complex. However, compromising may also result in a suboptimal outcome that does not fully address the root cause of the conflict or create a lasting agreement. References: [IIBA BABOK Guide v3], section 2.2.2.5, page 26; CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 181; Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam, question 254.

A business analyst is responsible for preparing the business architecture, feasibility studies, and business cases. A business analyst is a professional who analyzes the needs and problems of an organization and its stakeholders, and proposes solutions that deliver value to them. A business analyst performs various tasks, such as eliciting, analyzing, validating, and managing requirements, conducting stakeholder analysis, modeling business processes, designing solutions, assessing risks, and evaluating alternatives. A business analyst also prepares various documents, such as business architecture, feasibility studies, and business cases, to communicate the business needs and the proposed solutions to the relevant stakeholders and decision-makers. A business architecture is a description of the current and future state of the business, including its vision, goals, objectives, strategies, capabilities, processes, and organizational structure. A business architecture helps to align the business and IT strategies, and to identify the gaps and opportunities for improvement. A feasibility study is an assessment of the technical, financial, and operational viability of a proposed project or initiative. A feasibility study helps to determine if the project is worth pursuing, and if it can be successfully implemented within the given constraints and resources. A business case is a document that provides the justification and rationale for a proposed project or initiative, based on its expected costs, benefits, risks, and impacts. A business case helps to secure the approval and funding for the project, and to measure its performance and outcomes. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, pages 3-4, 47, 343

Business Analysis Professional Resources | IIBA®, under Business Analysis Body of Knowledge (BABOK ®) Guide, Business Analysis Standard, and Standards, Regulations, and Best Practices

The Differences Between Feasibility Studies and Business Cases

 The user interface is the part of a system that allows the actual users to interact with one another, the system, or data moved between two users. The user interface is the means by which the users can input, view, manipulate, or output information through the system. The user interface can be graphical, textual, auditory, tactile, or a combination of these. The user interface is an important aspect of the user experience and usability of the system. The user interface should be designed to meet the user needs, preferences, and expectations, as well as the system requirements and constraints. References: IIBA BABOK Guide v3, section 9.1.2, page 326; CBAP / CCBA Certified Business Analysis Study Guide, chapter 7, page 251; CBAP Exam Questions - Institute i4, question 241.

An Ishikawa diagram, also known as a fishbone diagram or a cause-and-effect diagram, is a graphical tool that shows the causes of a certain event. It is one of the seven basic tools of quality control and it is widely used in product design and quality defect prevention. A common use of this diagram is to identify potential factors causing an overall effect, such as a problem or a goal. It helps identify causal factors and contributing causes by organizing them into categories, such as people, processes, equipment, materials, environment, etc. The diagram can be created by brainstorming the causes and grouping them into major categories. The diagram can then be analyzed to find the root causes and the most significant causes of the effect. References:

Ishikawa diagram - Wikipedia, paragraph 1

Cause and Effect Diagram (aka Ishikawa, Fishbone) - Six Sigma Study Guide, paragraph 1

Quality tool: Cause and effect diagram | CQI | IRCA, paragraph 1

 The BA should proceed by obtaining approval to change the policies that are either constraining or insufficient to achieve the value desired by the future state. This is because the BA’s role is to align the solution with the business need and ensure that it delivers value to the stakeholders. If the existing policies are preventing or limiting the value realization, the BA should seek to change them by following the appropriate governance process and obtaining the necessary buy-in from the policy owners and other affected parties. Modifying the solution to comply with the policies, identifying an assumption about future state value, or modeling two future states are not the best options because they do not address the root cause of the problem and may result in suboptimal or ineffective solutions. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Strategy Analysis, page 254

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 5: Strategy Analysis, section 5.3: Define Future State, page 99

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 6: Strategy Analysis, page 254

The project charter is the document that is created first after the project is awarded and the statement of work is handed over to the project manager. The project charter is a high-level document that formally authorizes the initiation of the project and defines the project vision, objectives, scope, deliverables, stakeholders, roles and responsibilities, assumptions, constraints, risks, and success criteria. The project charter also identifies the project sponsor, the project manager, and the project budget and schedule. The project charter provides the direction and guidance for the project and serves as a reference point for future decisions and changes. The project charter is usually created by the project sponsor or the customer, in collaboration with the project manager and the business analyst, and approved by the key stakeholders. References: [IIBA BABOK Guide v3], section 5.1.1, page 161; CBAP / CCBA Certified Business Analysis Study Guide, chapter 6, page 233; CBAP Sample Questions, question 243.

The marketing department (AAC) is a key stakeholder for launching an existing product in another channel, as they are responsible for defining the requirements, confirming the elicitation results, and validating the solution. Therefore, they have a high influence on the project, as they can affect the decisions and outcomes of the project. They also have a high impact from the project, as they will be directly affected by the changes and benefits of the new channel. According to the stakeholder analysis technique, influence and impact are two dimensions that can be used to categorize and prioritize stakeholders12. A stakeholder with high influence and high impact is considered a primary stakeholder, who should be actively involved and engaged throughout the project

The BA needs to consider metrics and key performance indicators (KPIs) when using basic statistical sampling concepts to measure the objective of a solution implemented. Metrics and KPIs are quantitative measures that are used to evaluate the performance, progress, and value of a solution, process, or activity. They can help the BA to determine if the solution is meeting the expected outcomes and benefits, and to identify any gaps, issues, or opportunities for improvement. Metrics and KPIs can also help the BA to communicate the results and impact of the solution to the stakeholders and the organization. Some examples of metrics and KPIs that can be used to measure the objective of increasing the number of customer calls resolved per hour are: average call duration, first call resolution rate, customer satisfaction score, and call resolution efficiency. Frequency and timing, financial analysis, and benchmarking and market analysis are not the best options to consider when using basic statistical sampling concepts, because they are either too general, too specific, or not directly related to the objective of the solution. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 8: Solution Evaluation, page 337

Business Analysis Body of Knowledge (BABOK) Guide, Version 3, Chapter 8: Solution Evaluation, section 8.2: Analyze Performance Measures, page 153

Business Analysis Professional Resources, IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Skillsoft Book, Chapter 8: Solution Evaluation, page 337

A Pareto diagram is a type of chart that displays the frequency of problems or causes in a process in descending order by bars, and the cumulative percentage of the total number of problems or causes by a line. The Pareto diagram helps to identify the most significant defects or issues that need to be prioritized for improvement. It is based on the Pareto principle, which states that 80% of the problems are caused by 20% of the causes. A Pareto diagram is one of the seven basic quality tools that are widely used in quality management and process improvement. References:

Pareto chart - Wikipedia

What Are the 7 Basic Quality Tools? | Lucidchart Blog, under 7 quality tools

What is a Pareto Chart? Analysis & Diagram | ASQ