USA / CA +1 (877) 872 2860

UK +44 330 808 9340

Australia +61 279 080 154

Info@AdaptiveUS.com

Get Started for Free
adaptiveus2022logo             

100% Success in IIBA Exams or 100% Refund. That's a Promise.

                 Member Login

    Adaptive US Free ECBA Exam Questions

     

    #Q15.Tools that facilitate recording; organizing; storing and sharing requirements and designs are _________.

    1. Requirements (traced) 
    2. Modeling notations/ standards 
    3. Requirements management tools 
    4. Modeling tools 

    Answer: C - Requirements management tools

    Explanation: Purpose of the tool

    BABoK V3.0 - Section 5.1.5 - Guidelines and Tools #4 - Requirements Management Tools/Repository: used to store and manage business analysis information. The tool may be as simple as a text document or as complex as a dedicated requirements management tool.


    #Q14. Which of the following is expressed as conditions that increase the likelihood or severity of a negative impact to value?

    1. Influences
    2. Impact
    3. Tolerance
    4. Risks

    Answer: D - Risks

    Explanation: BABoK V3.0 - Section 6.3.4.3 - Negative Impact to Value - Risks are expressed as conditions that increase the likelihood or severity of a negative impact to value.


    #Q13. Stakeholders usually prioritize their requirements into which of the following categories?

    1. High 
    2. Medium
    3. Low
    4. Very Low

    Answer: A - High.

    Explanation: This is a common scenario BABoK V3.0 - Section 5.3.4.2 - Stakeholders may also have difficulty characterizing any requirement as a lower priority, and this may impact the ability to make necessary trade-offs. In addition; stakeholders may (intentionally or unintentionally) indicate a priority to influence the result to their desired outcome.


    #Q12. Which of the following prioritization factors considers consequences resulting from not implementing a requirement?

    1. Benefit 
    2. Penalty 
    3. Cost 
    4. Risk 

    Answer: B- Penalty

    Explanation: Definition: BABoK V3.0 - Section 5.3.4.1 - Paragraph 2 - Point #2 -Penalty: the consequences that result from not implementing a given requirement. This includes prioritizing requirements in order to meet regulatory or policy demands imposed on the organization; which may take precedence over other stakeholder interests. Penalty may also refer to the negative consequence of not implementing a requirement that improves the experience of a customer.


    #Q11. Business Analyst C wants to prioritize requirements based on the highest value that it can provide. Which of the following factors will help C the most?

    1. Penalty 
    2. Cost 
    3. Benefit 
    4. Risk 

    Answer: C- Benefit

    Explanation: Definition

    BABoK V3.0 - Section 5.3.4.1 - Paragraph 2 - Point #1 -Benefit: the advantage that accrues to stakeholders as a result of requirement implementation; as measured against the goals and objectives for the change. The benefit provided can refer to a specific functionality; desired quality; or strategic goal or business objective.

    BABoK V3.0 - Section 6.4.6 - Techniques - Process Modelling: used to describe how work would occur in the solution scope or during the change.

    ECBA Thinkific Trial

    #Q10. Which of the following provides a plan to transition from the current state to the future state?

    1. Business policies  
    2. Change strategy
    3. Current state description
    4. BA performance assessment

    Answer: B- Change strategy

    Explanation: Definition

    BABoK V3.0 - Glossary - Change strategy: A plan to move from the current state to the future state to achieve the desired business objectives.


    #Q9. Business analyst A has decomposed BA information into components to further examine constraints or assumptions that impact the components. What is A doing?

    1. Modeling requirements  
    2. Analyzing requirements
    3. Implementing requirements
    4. Representing attributes

    Answer: B - Analyzing requirements

    Explanation: BABoK V3.0 - Section 7.1.4.2 - Analyze Requirements - Business analysis information is decomposed into components to further examine for:

    • anything that must change to meet the business need;
    • anything that should stay the same to meet the business need;
    • missing components;
    • unnecessary components; and
    • any constraints or assumptions that impact the components.

    #Q8.Which of the following describes how all of the business analysis information for a change relates including the relationship between various types of information?

    1. Business analysis information architecture 
    2. Architectural framework 
    3. Viewpoints 
    4. Views

    Answer: A- Business analysis information architecture

    Explanation: BABoK V3.0 - Section 7.4.4.5 - Business Analysis Information Architecture - The structure of the business analysis information is also an information architecture. This type of architecture is defined as part of the task Plan Business Analysis Information Management (p. 42). The information architecture is a component of the requirements architecture because it describes how all of the business analysis information for a change relates. It defines relationships for types of information such as requirements; designs; types of models; and elicitation results.


    #Q7. If there are no relationships between requirements that link elements in two different and conflicting ways; then the relationship satisfies which of the following quality criteria?

    1. Consistent
    2. Unambiguous
    3. Necessary
    4. Defined

    Answer: A- Unambiguous

    Explanation: BABoK V3.0 - Section 7.4.4.4 - Relate and Verify Requirements Relationships - Unambiguous: there are no relationships that link elements in two different and conflicting ways.


    #Q6. A set of conventions that define how requirements will be represented; organized and related is known as:

    1. Views
    2. Viewpoints
    3. Architecture
    4. Attributes

    Answer: A- Viewpoints

    Explanation: BABoK V3.0 - Section 7.4.4.1 - Requirements Viewpoints and Views A viewpoint is a set of conventions that define how requirements will be represented; how these representations will be organized; and how they will be related. Viewpoints provide templates for addressing the concerns of particular stakeholder groups.

    Webinar CTA

    #Q5. Which of the following stakeholders can participate in specify and model requirements tasks?

    1. Only Sponsor and PM
    2. Only developers and implementation SME
    3. Only technical architect and PM
    4. Any stakeholders

    Answer: D- Any stakeholders

    Explanation: BABoK V3.0 - Section 7.1.7 - Any stakeholder: business analysts may choose to perform this task themselves and then separately package and communicate the requirements to stakeholders for their review and approval, or they might choose to invite some or all stakeholders to participate in this task.


    #Q4. Which of the following can be used for quality control when verifying requirements and designs?

    1. Data model
    2. Templates
    3. Information management approach
    4. Checklists

    Answer: D- Checklists

    Explanation: BABoK V3.0 - Section 7.2.4.3 - Checklists - Checklists are used for quality control when verifying requirements and designs.


    #Q3. Which of the following is used to record the meaning of relevant business terms while analyzing requirements?

    1. Glossary.
    2. Scope model
    3. State model
    4. Data dictionary

    Answer: A- Glossary

    Explanation: BABoK V3.0 - Section 7.1.6 - Techniques - Glossary: used to record the meaning of relevant business terms while analyzing requirements.


    #Q2.The main reason for implementing appropriate levels of abstraction is because:

    1. Not all stakeholders find value in the entire set of requirements
    2. Requirements do not have necessary attributes
    3. Requirements have missing components
    4. Stakeholders don’t have an interest

    Answer: A- Not all stakeholders find value in the entire set of requirements

    Explanation: BABoK V3.0 - Section 7.1.4.4 - Implement the Appropriate Levels of Abstraction - The level of abstraction of a requirement varies based on the type of requirement and audience for the requirement. Not all stakeholders require or find value in the complete set of requirements and models. It may be appropriate to produce different viewpoints of requirements to represent the same need for different stakeholders. Business analysts take special care to maintain the meaning and intent of the requirements overall representations.


    #Q1.Which of the following techniques can be used to model the rationale of a change?

    1. Roles and Permissions Matrix
    2. Organizational modeling
    3. Business capability analysis
    4. Decision modeling

    Answer: D- Decision modeling

    Explanation: BABoK V3.0 - Section 7.1.4.1 - Model Requirements - Paragraph 3 - Point #2 - Rationale: models represent the ‘why’ of a change. Techniques used to represent the rationale include Decision Modelling; Scope Modelling; Business Model Canvas; Root Cause Analysis; and Business Rules Analysis.