Free IIBA CCBA Practice Exam with Questions & Answers | Set: 7

The BA should store the requirements package on a secure shared drive that has access control and encryption to protect the sensitive information from unauthorized access or modification. This will ensure that the requirements are available for future reference and can be traced to the solution. Printing the requirements package and distributing it to stakeholders in person may compromise the confidentiality and integrity of the information. Archiving the requirements package in the business analysis portal may not provide adequate security measures for sensitive information. Sending the requirements package to stakeholder in a password protected email may expose the information to interception or hacking. References: [A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide)], Chapter 3: Business Analysis Planning and Monitoring, Section 3.6: Plan Requirements Management Process, Task 3.6.2: Define Requirements Change Process, Page 58. [Business Analysis for Practitioners: A Practice Guide], Chapter 3: Requirements Elicitation and Analysis, Section 3.7: Requirements Traceability, Page 66.

 A predictive development process is a type of approach that follows a predefined and detailed plan for delivering the solution, with minimal changes and uncertainties1. A predictive development process is suitable for the initiative that has a short deadline and a regulatory mandate, as it can help the BA and the stakeholders to ensure that the solution meets the compliance requirements and the schedule constraints. A predictive development process can also help to manage the risks and expectations of the stakeholders, as it provides clear and consistent scope, requirements, and deliverables2. The other options are not the best approaches for the initiative, as they may not be able to handle the complexity and urgency of the project. A crystal clear development process is a type of agile approach that focuses on collaboration, communication, and feedback, with frequent iterations and adjustments3. A Kanban development process is a type of lean approach that visualizes theworkflow, limits the work in progress, and optimizes the flow of value. An adaptive development process is a type of approach that responds to changes and uncertainties, with flexible and iterative planning and delivery. References:

1: Predictive Development Process: Definition, Characteristics and Examples

2: Why Use a Predictive Development Process?

3: Crystal Clear Development Process: Definition, Principles and Practices

: [Kanban Development Process: Definition, Principles and Practices]

: [Adaptive Development Process: Definition, Characteristics and Examples]

According to the BABOK® Guide, a risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives. A business analyst (BA) should identify, analyze, and manage risks throughout the business analysis process. In this scenario, the potential organizational restructure is a risk that could affect the requirements and the solution scope of the new system. Therefore, the BA should record this risk and assess its probability and impact on the project objectives. The BA should also plan how to respond to this risk if it materializes, such as by revising the requirements or modifying the solution design. This way, the BA can proactively manage the risk and minimize its negative effects on the project. References:

[BABOK® Guide], section 10.1: Risk Analysis and Management

CCBA Exam Questions & Answers with Explanations, question 25

Sample size is the number of observations or data points that are used to measure the performance of a solution. Sample size is an important consideration for the BA to obtain reliable and valid information, as it affects the accuracy, precision, and confidence of the results. A larger sample size can reduce the sampling error and increase the representativeness of the population, but it may also increase the cost and time of data collection. A smaller sample size can save resources and time, but it may also introduce bias and uncertainty in the results. Therefore, the BA should determine the appropriate sample size based on the purpose, scope, and quality criteria of the performance measurement12. The other options are not directly related to the data collection process, although they may influence the analysis and interpretation of the data. References:

1: BABOK® Guide v3, Chapter 7: Solution Evaluation, Section 7.3: Analyze Performance Measures

2: Business Analysis Expert Certification, CCBA® | IIBA®

 The BA should use a quality control checklist to address the project manager’s concern about incomplete requirements. This is because a quality control checklist is a tool that helps to verify that the requirements meet the quality criteria and standards defined for the project. A quality control checklist can help to identify and correct any errors, omissions, inconsistencies, or ambiguities in the requirements. Using a quality control checklist can also help to avoid schedule delays caused by incomplete requirements. The other options are not directly related to checking the completeness of the requirements. References:

BABOK Guide, section 4.2.3: Verify Requirements

CCBA Practice Test, question 102

The BA can find out which stakeholder has the authority to approve, deny, or defer the change request from the governance approach. The governance approach defines how decisions are made regarding business analysis activities and deliverables. It specifies who are involved in making decisions, what are their roles and responsibilities, what are the criteria and processes for decision making, and how decisions are communicated and documented. The governance approach can help to identify which stakeholder has decision-making authority over change requests. References: : BABOK Guide v3, Section 2.4

The BA should consider the number of systems being affected by the requirement when performing an impact analysis of this change. This is because an impact analysis is a technique that involves assessing the potential effects of a change on the existing or proposed solution, business processes, stakeholders, or organization. The number of systems being affected by the requirement is an important factor that can influence the feasibility, cost, risk, and complexity of implementing the change. The other options are not as relevant or significant as considering the number of systems being affected by the requirement. References:

BABOK Guide, section 10.16: Impact Analysis

CCBA Practice Test, question 104

 The element of stakeholder management that the BA is performing when negotiating and resolving conflict with stakeholders to ensure they participate in required BA activities is gaining agreement on commitments. This means that the BA is establishing consensus or acceptance among stakeholders regarding their roles, responsibilities, expectations, deliverables, and timelines for a project or a solution. The BA is also addressing any differences or disputes among stakeholders that may hinder their participation or collaboration.

The other options are incorrect because:

Option A is incorrect because confirming elicitation results is not an element of stakeholder management, but an element of elicitation. Confirming elicitation results means verifying and validating that the information gathered from stakeholders during elicitation activities is accurate, complete, clear, and consistent.

Option C is incorrect because monitoring stakeholder engagement is not an element of stakeholder management, but an element of stakeholder analysis. Monitoring stakeholder engagement means assessing and tracking the level of involvement, interest, influence, and impact of stakeholders throughout a project or a solution.

Option D is incorrect because planning stakeholder engagement is not an element of stakeholder management, but an element of stakeholder analysis. Planning stakeholder engagement means defining and documenting the strategies, methods, and activities for engaging and communicating with stakeholders.

References:

BABOK Guide v3, section 2.5: Manage Stakeholder Collaboration

CCBA Exam Questions, question 19

Creating an agenda is a useful activity to ensure a productive and focused workshop, as it helps to define the purpose, scope, objectives, participants, roles, and expected outcomes of the workshop. It also helps to manage time and expectations, and to avoid distractions and conflicts. Documenting feedback, facilitating the workshop, and reserving a location are also important activities, but they are not done in advance of the workshop. References: BABOK Guide v3, page 54; CCBA Mock Test, question 18

Dependencies are the relationships between requirements that indicate that one requirement is contingent on another requirement. Dependencies can affect the feasibility, value, and risk of the requirements, and therefore, they should be taken into account when prioritizing the requirements. The business analyst should identify and document the dependencies between the requirements, and analyze how they impact the project scope, schedule, and budget. The business analyst should also communicate the dependencies to the business owner and other stakeholders, and help them to prioritize the requirements based on the dependencies and the business objectives.References: BABOK Guide v3, page 156; CCBA Mock Test, question 7

 A business analysis information package is a collection of information that summarizes the results of business analysis activities. It helps to organize and present the scanned notes, documents, andphotos of whiteboards in a coherent and consistent manner. Meeting with stakeholders or users, or managing stakeholder collaboration are possible next steps after developing the package. References: BABOK Guide v3, page 387; CCBA Mock Test, question 5

The BA should assess the impact of the forthcoming legislation immediately when it is logged in the action items register. This is because assessing the impact of a change is a technique that involves analyzing how a change affects the existing or proposed solution, business processes, stakeholders, or organization. Assessing the impact of the forthcoming legislation immediately can help the BA to identify and mitigate any potential risks or issues that might have an impact on the proposed architecture and plan accordingly. The other options are not as urgent or appropriate as assessing the impact immediately. References:

BABOK Guide, section 10.16: Impact Analysis

CCBA Practice Test, question 115

The BA missed the element of understanding stakeholder roles, which is part of the task of identifying stakeholders in the business analysis planning and monitoring knowledge area. The BA should have identified the roles and responsibilities of the stakeholders, including who has the authority to approve the requirements, before eliciting, specifying, and modelling them. This would have avoided the delay and confusion caused by the wrong sign-off authority. The other options are not relevant to the question, as they are related to different tasks or knowledge areas. References: [A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide)], Chapter 3: BusinessAnalysis Planning and Monitoring, Section 3.1: Plan Stakeholder Engagement, Task 3.1.1: Identify Stakeholders, Page 36. [Business Analysis for Practitioners: A Practice Guide], Chapter 2: Needs Assessment, Section 2.2: Identify Stakeholders, Page 23.

The BA should review the use case scenarios after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Reviewing the use case scenarios means verifying and validating that they are accurate, complete, clear, consistent, and aligned with the stakeholder needs and expectations. Reviewing the use case scenarios can help to ensure the quality and correctness of the requirements.

The other options are incorrect because:

Option A is incorrect because identifying all the roles and responsibilities is not an action that the BA takes after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Identifying all the roles and responsibilities means defining and documenting the functions or duties that stakeholders perform within an organization or a project. Identifying all the roles and responsibilities can help to engage and collaborate with the relevant stakeholders.

Option C is incorrect because conducting a requirements workshop is not an action that the BA takes after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Conducting a requirements workshop means facilitating a structured session with stakeholders to elicit, analyze, communicate, or validate requirements. Conducting a requirements workshop can help to gather information from multiple stakeholders in an interactive way.

Option D is incorrect because creating acceptance criteria is not an action that the BA takes after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Creating acceptance criteria means defining and documenting the conditions or standards that must be met by a solution to be accepted by stakeholders. Creating acceptance criteria can help to evaluate the performance and value of the solution.

References:

BABOK Guide v3, section 10.46: Use Cases

CCBA Exam Questions, question 22

 Logistics setup is a technique that defines the physical and technical arrangements for conducting elicitation activities, such as location, time, equipment, and materials1. Logistics setup can help theBA to handle the situation where not everyone could attend the meeting because of their individual dispersed locations, by adjusting the arrangements to accommodate the remote participants, such as using online conferencing tools, sending the agenda and materials in advance, and recording the session for later review2. The other options are not the things that the BA needs to adjust to handle the situation, but rather the things that the BA may have already defined or planned before the elicitation activities. Project stakeholders are the people or groups who have an interest or influence in the project or the solution3. Elicitation scope is a technique that defines the boundaries and sources of information for the elicitation activities. Elicitation technique is a technique that defines the methods and practices for obtaining information from the stakeholders. References:

1: BABOK® Guide v3, p. 50

2: Logistics Setup: Definition, Elements and Examples

3: BABOK® Guide v3, p. 13

: BABOK® Guide v3, p. 51

: BABOK® Guide v3, p. 52