For IIBA CBAP/ CCBA Business Analysis Certification Course, visit www. Mybacentral. Com
Assess your preparation before you take your final Certification of Capability in Business Analysis (CCBA) exam by IIBA. Identify areas of improvements or knowledge areas that would require additional preparation. This level will test applicant’s knowledge as well as experience in business analysis in form of a scenario based exam. This exam has 130 multiple choice questions to be attempted in 3 hours. These questions are NOT official questions from IIBA. The questions are, however, comparable to an examination in terms of formulation, difficulty and covered Read moresubjects. The number of questions, as well as, the available time correspond to the "official examination".
A) Predictive approaches ensure the solution is fully defined before implementation begins, where as Adaptive approaches allow for rapid delivery of business value in short iterations.
B) Predictive approaches maximize control and minimize risk, where as Adaptive approaches allow for a higher degree of uncertainty.
C) Predictive approaches assume that requirements need not be defined before implementation, where as Adaptive allow requirements to be clarified and refined through iterative process.
A and B only.
A, B and C.
You will use the appropriate documentation at the discretion of the business analysis team.
You will use the project management information system.
You will use whatever business analysis forms are most appropriate.
You will use standardized templates.
Adaptive approach defines requirements through experimentation.
Adaptive approach does not define the requirements until after a solution for the problem has been identified.
Adaptive approach defines requirements using standardized templates.
Adaptive approach defines requirements through team interaction.
Predictive approaches determine how priorities will be diagnosed for the project solution.
Predictive approaches encourage changes that prevent errors and omissions.
Predictive approaches typically have meetings daily to discuss the business analysis requirements process.
Predictive approaches typically call for a significant amount of formality and detail.
Communications in an Adaptive approach to business analysis focus more on the frequency of communication.
Communications in an Adaptive approach typically use face-to-face channels.
Communications in an Adaptive approach focus more on formal communications.
Communications in an Adaptive approach are all ad hoc.
Using this task, we can understand which organizations and departments are relevant to the change and the best way to collaborate and communicate with them.
Using this task, we can understand which stakeholders are relevant to the change and the best way to collaborate and communicate with them.
Using this task, we can understand which organizations and departments that are likely affected by a problem that a project must solve.
Using this task, we can understand which people are relevant to the change and the best way to collaborate and communicate with them.
It's important to identify the stakeholders so the business analyst knows who to report to.
It's important to identify the stakeholders so the business analyst knows who to bill for the project.
If appropriate stakeholders are not identified, we may not be able to uncover their needs which can result in rework of business analysis work.
It's important to identify the stakeholders so the stakeholders know who is the business analyst.
What needs to be communicated, to whom and when.
What is the formality required and delivery means.
When the assessment of capabilities should happen.
Frequency of communication and level of details.
Using this task, we can plan business analysis work from selection of a methodology to planning the individual activities, tasks, and deliverables.
Using this task, we can understand which stakeholders are relevant to the change and the best way to collaborate and communicate with them.
Using this task, we can define a process for requesting, analyzing and approving change requests and describes how approvals and prioritization decisions will be made for requirements and designs.
Using this task, we can define how business analysis information such as requirements and designs are captured, stored, and traced for long-term use.
Description of steps for requesting changes
Describe stakeholders responsible for requesting, analyzing and approving change requests
Describe elements of change request such as costs and benefits of the proposed changes, efforts and time estimates, risks, priority etc
All of the above
Business Analysis Approach
Stakeholder Engagement Approach
Business Analysis Governance Approach
Business Analysis Information Management Approach
Business Analysis Approach
Stakeholder Engagement Approach
Business Analysis Governance Approach
Business Analysis Information Management Approach
Using this task, we can understand which Business Analysis Information is relevant to the change.
Using this task, we can define a process for requesting, analyzing and approving Business Analysis Information.
Using this task, we can define how Business Analysis Information as requirements and designs will be captured, stored, and traced for long-term use.
None of the above
Domain Subject Matter Expert
Sponsor
Project Manager
End User
Rate this question:
Project Manager
Customer
Sponsor
Domain Subject Matter Expert
Rate this question:
Domain Subject Matter Expert
Project manager
Regulator
Implementation Subject Matter Expert
Rate this question:
To understand which stakeholder needs are within scope and which one are outside scope.
To respond if the elicitation activity strays from the intended scope.
To manage stakeholder expectations.
All of the above
By educating stakeholders on elicitation techniques.
Publish an agenda in advance.
Requesting stakeholders to review supporting materials.
All of the above.
Setting up logistics prior to elicitation activity.
Securing supporting material.
Choosing the right techniques and ensuring each technique is performed correctly.
Preparing stakeholders for the elicitation activity.
Business Analysis Approach
Needs
Stakeholder engagement approach
Existing Business Analysis Information
Rate this question:
Collaborative elicitation
Elicitation through research
Elicitation through experiments
None of the above.
Keeping it focused to produce the intended information at the desired level of detail.
Keeping it on track as per scope of the change initiative.
Determining when there is sufficient elicitation in order to stop the activity.
All of the above.
Collaborative elicitation
Elicitation through research
Elicitation through experiments
None of the above.
Business Analysis Approach
Existing Business Analysis Information
Supporting Materials
None of the above
Rate this question:
Business Analysis Approach
Elicitation activity plan
Stakeholder engagement approach
Existing Business Analysis Information
Rate this question:
Collaborate with stakeholders to ensure their inputs are correctly captured.
Collaborate with stakeholders to ensure that they agree with the results.
Identify problems, errors, omissions, conflicts, ambiguities and resolve discrepancies in the elicited information.
All of the above.
Business Analysis Approach
Elicitation Activity Plan
Existing Business Analysis Information
Unconfirmed elicitation results
Business Analysis Approach
Information Management Approach
Stakeholder engagement approach
Business Analysis Information
As stakeholders can influence business analysis work.
As stakeholders have authority over the approval of business analysis work.
As stakeholders are an important source of needs, constraints, and assumptions.
All of the above.
A) Negotiation and conflict resolution
B) Communication skills
C) Organization and Time Management
A and B only.
Business Analysis Approach
Business Objectives
Stakeholder engagement approach
Recommended Actions
Rate this question:
Implementation subject matter experts
Domain subject matter experts
Sponsor
End-user
Operational Support
Domain subject matter experts
Sponsor
Project Manager
Implementation subject matter experts
Domain subject matter experts
Customer
Project Manager
Implementation subject matter experts
Domain subject matter experts
End user
Sponsor
Brainstorming
Focus Groups
Collaborative Games
Workshops
End-user
Project Manager
Domain Subject Matter Expert
Sponsor
Formal Documentation
Informal Documentation
Presentations
All of the above
Formal Documentation
Informal Documentation
Presentations
All of the above
Group collaboration
Individual collaboration
Emails
All of the above
Group collaboration
Individual collaboration
Emails
All of the above
Stakeholders need to agree on time and resource commitments.
Stakeholders need to have explicit understanding of the expectations and desired outcomes of the commitment.
Stakeholders need to agree on terms and conditions of the commitments.
All of the above.
Depends - Necessity
Depends -Efforts
Derive
Validate
True
False
Rate this question:
Dependencies
Cost
Risk
Penalty
Dependencies
Time sensitivity
Risk
Benefit
Dependencies
Cost
Risk
Penalty
Prioritize Requirements
Organize Requirements
Verify Requirements
Validate Requirements
Increase in benefits by accepting the change
Total cost of implementing the change
Impact to schedule or delivery dates
Priority of requirement or design before being proposed for change.
Rate this question:
Interviews
Reviews
Workshops
User Stories
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Related Topics
Recent Quizzes
Featured Quizzes
Popular Topics
Wait!
Here's an interesting quiz for you.