For IIBA ECBA Course and ECBA Practice Test 2 & 3, visit www. Mybacentral. Com
[Updated for revised ECBA Exam Blueprint w. E. F. March 01, 2021]
Assess your preparation before taking your final Entry Certificate in Business Analysis (ECBA) exam by IIBA. Identify areas of improvement or knowledge areas that would require additional preparation. This is a knowledge-based exam with 50 multiple choice questions to be attempted in 90 minutes. This test is the FIRST test of 3 SERIES tests. These questions are NOT official questions from IIBA. The questions are, however, comparable to an examination in terms of formulation, difficulty, Read moreand covered subjects. The number of questions and the available time corresponds to the "official examination."
The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to achieve its goals.
The practice of enabling change in the context of an enterprise by defining needs and recommending solutions that deliver value to stakeholders.
Identification of business needs and determine solutions to business problems.
Identifying business problems and selecting which solutions will best resolve those problems.
The BACCM is a conceptual framework for business analysis
The BACCM can be used to describe and communicate about business analysis using a common terminology.
The core concepts in BACCM are independent of the other core concepts.
The six core concepts in BACCM are Change, Needs, Solutions, Stakeholders, Value and Contexts.
Rate this question:
A requirement represents a need and provides understanding regarding the potential value that could be delivered if it is fulfilled.
A design represents a solution and provides a solution blueprint that shows solution components and relationship between them.
Risk is the effect of uncertain events on the value delivered by a change initiative or a solution, or the enterprise.
All of the above
Creative Thinking
Systems Thinking
Learning
Complex Reasoning
Trustworthiness
Personal Accountability
Ethics
Adaptability
Industry and Organization Knowledge
Business Acumen
Domain Knowledge
Solution Knowledge
How and when tasks will be performed.
Deliverables that should be produced.
Indicative set of techniques that will be used.
All of the above.
Change to requirements can occur any time after planning business analysis approach.
Changes to requirements can occur at any time.
Change to requirements can occur any time after planning business analysis governance.
Change to requirements can occur at any time before the key stakeholders approve the identified requirements.
Requirements for ad hoc sales contest
Requirements for seasonal marketing campaign
Regulatory requirements
All of the above
Rate this question:
True
False
Rate this question:
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.
Collaborative elicitation
Elicitation through research
Elicitation through experiments
None of the above.
Using this task we can understand the scope of the elicitation activity, select appropriate techniques, and plan for appropriate resources.
Using this task we can check the information gathered during an elicitation session for accuracy and consistency with other information.
Using this task we can understand stakeholder needs and identify potential solutions.
None of the above.
Business Analysis Approach
Elicitation Activity Plan
Existing Business Analysis Information
Unconfirmed elicitation results
True
False
Rate this question:
Implementation subject matter experts
Domain subject matter experts
Sponsor
End-user
Implementation subject matter experts
Domain subject matter experts
Customer
Project Manager
Focus Groups
Survey or Questionnaire
Interviews
Observation
Document Analysis
Interviews
Workshops
Reviews
Requirements life cycle begins with the representation of a business need as a requirement.
Requirements life cycle ends when a solution is fully developed and implemented.
Requirements life cycle ends when a solution and the requirements that represent it are retired.
None of the above.
Rate this question:
Textual document.
Requirements management tool.
Traceability matrix using a spreadsheet.
None of the above.
Regularly update requirements.
Regularly update relationships among requirements.
Regularly update requirements attributes such as requirement’s source, priority, complexity etc.
All of the above.
In a general manner and at high levels of abstraction.
Without direct ties to a particular tool or organizational structure.
With limited reference to specific solutions.
All of the above
True
False
Rate this question:
Requirements Modelling tool
Prototyping and simulation tools
Traceability
Issue tracking tools
True
False
Rate this question:
Conversation interaction tools such as e-mails.
Collaboration tools such as wikis, document sharing etc.
Requirements maintenance and tracking tools.
Issue tracking tools.
Regulator
Sponsor
Domain Subject Matter Expert
Operational Support
Interviews
Reviews
Workshops
User Stories
Requirements are focused on the need while designs are focused on the solution.
A requirement leads to a design which in turn may drive the discovery and analysis of more requirements which again are used to define more detailed designs.
Requirements and designs may be either high-level or very detailed.
All of the above.
Current State Description
Future State Description
Unconfirmed Elicitation Results
None of the above
Rate this question:
Requirements and designs should be aligned with the needs of the stakeholders and should not be conflicting with other requirements
Requirements and designs should not contain extra or unnecessary details.
Requirements and designs should be enough to guide further work and are at the appropriate level of detail.
Requirements and designs should be self-contained and can be understood independent of other requirements or designs.
Using this task we can describe requirements or designs in detail using various techniques.
Using this task we can ensure that requirements or designs are developed in enough detail, are consistent, and are of high quality.
Using this task we can ensure that requirements or designs delivers business value and supports the organization's goals and objectives.
None of the above.
We need to identify and define assumptions to validate design in terms of supporting a requirement.
We need to identify and define assumptions to evaluate alignment of requirements with the solution scope.
We need to identify and define assumptions to evaluate actual benefits from the solution after it is implemented.
We need to identify and define assumptions so that associated risks can be managed.
The Business analysis information architecture describes how all of the business analysis information for a change relates.
The business analysis information architecture is a not a component of the requirements architecture.
The Business analysis information architecture describes relationships for type of business analysis information such as requirements designs, types of models and elicitation results.
The business analysis information architecture can be used to verify that the relationships are complete and so it ensures that requirements architecture is complete.
Rate this question:
Solution components or releases
Departments
Functions
All of the above
Cost to purchase and/or implement the solution.
Cost to maintain and operate the solution.
Value from next best design option or alternative not selected.
Costs due to human, information and physical resources.
Domain and Implementation subject matter expert
Project Manager
Customer, End-user and Sponsor
Operational support
Domain subject matter expert
Regulator
Implementation subject matter expert
Sponsor
Metrics and Key Performance Indicators
Reviews
Financial Analysis
Acceptance and evaluation criteria.
Scope Modelling
Functional Decomposition
Organizational Modelling
Workshops
Show the stimuli flowing between objects. The stimulus is a message and the arrival of the stimulus at the object is called an event.
Quickly analyze various aspects of the current state of the business process undergoing change.
Detail user interface requirements and integrate them with other requirements such as use cases, scenarios, data and business rules.
Describe and analyze the different possible states of an entity within a system, how that entity changes from one state to another, and what can happen to the entity when it is in each state.
Non-Functional Requirements Analysis
Business Rules Analysis
Business Capability Analysis
Business Model Canvas
Business Requirements
Stakeholder Requirements
Functional Requirements
Non-Functional Requirements
Conceptual data model
Logical data model
Physical data model
None of the above
Data Model
Glossary
Concept Model
Business Model Canvas
Observation
Prototyping
Interviews
Surveys
Use Cases and Scenarios
Business Rules Analysis
Prototyping
Data Flow Diagrams
Document Analysis
Interviews
Workshops
Reviews
Backlog Management
Reviews
Workshops
Item Tracking
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.