20 Context Practice Questions & Answers

Every Context practice question from the ECBA Practice Test, with the correct answer and a short explanation.

1. A junior business analyst finds a detailed process description on the department's shared drive. The file lists no author, and the content refers to a team structure that no longer exists. What is the best next action before using it as input to the analysis?
- A.Treat the file as authoritative, because it is stored in the department's official repository.
- B.Update the file with the current team structure and circulate it as the approved description.
- C.Ask the current process owner to confirm which parts still reflect how the work is done today.✓ Answer
- D.Discard the file entirely and rebuild the process description from interviews with new staff.
Document analysis obliges the analyst to judge the currency and relevance of source material before relying on it, and a reference to a team that no longer exists is a direct signal that the content may be out of date. Checking with the person who owns the process, and recording what was confirmed and what was not, is how information quality is established; storage in an official repository is not itself evidence of accuracy, and a foundational analyst does not republish a revised version on personal authority.
Source: IIBA, The Business Analysis Standard and BABOK Guide — Plan Business Analysis Information Management; Document Analysis (currency and relevance of source material)Report a problem with this question
2. During a peer review, a colleague works through each requirement statement asking whether it is written clearly enough that a tester could tell objectively if it has been met. Which activity is the colleague performing?
- A.Verifying the requirements, by judging whether the written statements meet quality standards.✓ Answer
- B.Confirming elicitation results, by checking notes against what stakeholders actually said.
- C.Validating the requirements, by judging whether they deliver value to the business.
- D.Approving the requirements, by obtaining agreement so that the work can move forward.
Verification asks whether the artifact itself is of sufficient quality and usable for its purpose, which is exactly what a check for testable, unambiguous wording is. Validation asks a different question — whether the requirement actually delivers business value — approval asks whether stakeholders agree so work can proceed, and confirming elicitation results only checks that notes match what was said in the session.
Source: IIBA BABOK Guide — Verify Requirements and Designs versus Validate Requirements, Approve Requirements and Designs, and Confirm Elicitation ResultsReport a problem with this question
3. A business analyst supports an initiative in a regulated industry where every requirement change must be traceable to a named approver. The team is used to agreeing changes verbally in its daily stand-up. What should the analyst do?
- A.Follow the organization's formal approval process and record who approved each change and when.✓ Answer
- B.Ask for a waiver from the regulator so the team can keep its lighter approval routine.
- C.Skip the approval step and rely on traceability links alone to show where every change originated.
- D.Keep the verbal practice, since the formality of approval is a matter of team preference.
Approval is always required, but how formal it must be is set by the context, and a regulated environment demands an auditable record rather than a verbal understanding. The level of rigour is driven by policy and regulation, not by what the team finds convenient, and traceability links show relationships between items — they do not record that a named person agreed to a change.
Source: IIBA BABOK Guide — Approve Requirements and Designs (formality of approval scales with the context); The Business Analysis Standard, regulated contextsReport a problem with this question
4. Midway through an initiative, stakeholders keep asking who originally requested a particular requirement and how urgent it is. Nobody can answer without reopening old meeting notes. What should the analyst propose?
- A.Baseline the requirement set so the approved version is protected from further edits.
- B.Add traceability links from each requirement to the design elements that satisfy it.
- C.Record requirement attributes such as source, urgency and status alongside each requirement.✓ Answer
- D.Raise the level of abstraction so that requirements stay stable while the details keep changing.
Requirement attributes are the metadata held about a requirement — source, author, priority, status, owner, urgency and similar — and planning which attributes to capture is part of deciding how business analysis information will be stored and accessed. Traceability records relationships between items, a baseline freezes an approved version, and changing the level of abstraction alters how much detail is written, so none of those answers the question of who asked for something and how pressing it is.
Source: IIBA BABOK Guide — Plan Business Analysis Information Management (requirements attributes, traceability, level of abstraction)Report a problem with this question
5. An analyst is asked to write a requirement so that other teams can reuse it in future initiatives. The draft currently states that the clerk types the claim number into the green legacy terminal screen. What should the analyst change?
- A.Move the requirement into the design section, because it describes how the work is done.
- B.Leave it as written and add an attribute marking it as reusable across future initiatives.
- C.Restate the requirement in terms of the need it serves, free of initiative-specific solution detail.✓ Answer
- D.Add the screen name and field position so any future team knows exactly what was built.
Maintaining requirements for reuse means keeping them accurate and consistent beyond the initiative that produced them, and a requirement is reusable only when it is written at a level free of solution-specific or initiative-specific detail. Naming a particular terminal screen ties the statement to one implementation, so adding more of that detail, relocating it, or simply tagging it reusable leaves it just as unusable elsewhere.
Source: IIBA BABOK Guide — Maintain Requirements and Designs (maintaining requirements for reuse)Report a problem with this question
6. After a session in which stakeholders reviewed the analyst's notes, two items were confirmed as accurate and one was disputed by two participants who remember it differently. What should the analyst do with this result?
- A.Hold all three items unrecorded until the dispute is settled in a follow-up session.
- B.Record only the confirmed items, because content still in dispute is not reliable yet.
- C.Decide which version of the disputed item is correct and document that as the agreed outcome.
- D.Record both the confirmed items and the disputed one, flagging the dispute for resolution.✓ Answer
The outcome of a validation step is itself business analysis information and belongs in the repository, including the unresolved point, because an open discrepancy is exactly what stakeholders need visibility of. At foundational level the analyst flags a conflict for review rather than choosing between stakeholder accounts, and withholding the record leaves the team working from memory.
Source: IIBA BABOK Guide — Confirm Elicitation Results and Plan Business Analysis Information Management (recording validation outcomes and open discrepancies)Report a problem with this question
7. A reporting solution meets its agreed specifications, but a year after release most departments still compile figures by hand. Interviews show that staff do not know what the solution can do and no one has defined who refreshes the underlying data. How is this best characterized?
- A.A solution limitation, since the solution clearly fails to deliver its expected value.
- B.An enterprise limitation, since the barrier lies in operations and awareness, not the solution.✓ Answer
- C.A requirements defect, since the original requirements missed what the users in the field needed.
- D.A risk, since the shortfall in value has not yet been confirmed by measured performance data.
Enterprise limitations are factors outside the solution that hold back value — culture, awareness, undefined supporting processes, reporting lines and the organization's practical ability to operate what was delivered. Here the solution performs as specified, so the constraint is operational and cultural rather than internal to the solution, and calling it a solution defect would point improvement effort at the wrong place.
Source: IIBA BABOK Guide — Assess Enterprise Limitations versus Assess Solution Limitations; The Business Analysis Standard, underused solution exampleReport a problem with this question
8. A claims solution performs well at every step except one: an overnight data transfer that frequently finishes late, leaving the steps that follow working from stale figures. What does this situation illustrate?
- A.An internal component dependency, where overall performance is capped by the weakest component.✓ Answer
- B.An enterprise limitation, where the surrounding organization cannot absorb the new solution.
- C.A business rule, where the policy governing data refresh timing has not been written down.
- D.An assumption, where the team believed the transfer would complete but never confirmed it.
Assessing solution limitations begins with identifying dependencies among the solution's own components, because the value the whole delivers is held down by its least effective part no matter how well the others work. The constraint here sits inside the solution and is observed, not merely believed, so it is neither an enterprise limitation nor an unverified assumption nor a policy statement.
Source: IIBA BABOK Guide — Assess Solution Limitations (identify internal solution component dependencies)Report a problem with this question
9. While planning, the team notes the following: a vendor has said it will expose an interface next quarter, nothing has been agreed in writing, and work is being scheduled as though the interface will arrive. How should the analyst classify this statement?
- A.As a planning flaw, because relying on unconfirmed information is an error in the approach.
- B.As a business rule, because it governs how the organization handles vendor interfaces.
- C.As a constraint, because the vendor's timetable restricts what the solution can include.
- D.As a stated assumption, because it is believed true and unverified, yet work depends on it.✓ Answer
An assumption is something held to be true without confirmation that the work nonetheless depends on, which is precisely the situation when a verbal vendor promise drives the schedule. A constraint is a restriction that genuinely limits the solution, such as a regulation or a fixed budget, a business rule governs organizational behaviour, and recording an assumption openly is sound practice rather than a flaw.
Source: IIBA BABOK Guide — Analyze Current State and Plan Business Analysis Approach (assumptions, constraints and business rules)Report a problem with this question
10. Partway through analysis, an analyst learns that a regulation in one operating region forbids the data transfer the preferred design depends on. The analyst is working under the direction of a senior analyst. What is the best next action?
- A.Document the restriction, adjust the plan around it, and raise it with the senior analyst.✓ Answer
- B.Proceed with the preferred design and record the regulation as a risk to be handled later on.
- C.Remove the affected region from scope so the preferred design can be kept as it is.
- D.Ask the stakeholders to seek an exemption so the original plan can continue unchanged.
A regulatory restriction is part of the context that bounds the work, so the analyst recognizes it, adapts the plan so that analysis stays aligned with reality, and escalates it to whoever has the authority to decide. Treating a legal prohibition as a deferred risk understates it, and a foundational analyst does not change scope or seek exemptions on personal initiative.
Source: IIBA BABOK Guide — Analyze Current State (policies and regulatory environment); The Business Analysis Standard, adapting the approach to contextReport a problem with this question
11. A solution produces an incorrect output roughly once a week and operations staff correct it by hand. Management asks the analysis team what should be done about it. What should the analyst contribute first?
- A.A recommendation to rebuild the failing component, since the defect keeps recurring weekly.
- B.A change request removing the affected output from scope until the defect can be resolved.
- C.A decision that the error is acceptable, because staff already correct it without difficulty.
- D.An assessment of the severity, likelihood of recurrence and operational impact, recorded for decision.✓ Answer
Investigating a solution problem leads to an impact assessment covering severity, how likely the problem is to recur, its effect on operations and the organization's capacity to absorb it, and that assessment is what lets stakeholders choose to resolve, mitigate or accept. Jumping straight to rebuilding, accepting or descoping skips the analysis that makes any of those choices defensible, and the decision itself is not the analyst's to make.
Source: IIBA BABOK Guide — Assess Solution Limitations (investigate solution problems; impact assessment)Report a problem with this question
12. While describing the current state, an analyst notes that two of the industry's major suppliers have merged and that the remaining supplier now dictates delivery terms. Where does this observation belong in the current-state description?
- A.Among the business policies, since delivery terms are rules the organization has to follow.
- B.Among the external influencers, which bound what the change can realistically achieve.✓ Answer
- C.Among the internal assets, since supplier relationships are resources the organization holds.
- D.Among the capabilities, since sourcing materials is one of the things the business does.
External influencers include industry structure, competitors, customers, suppliers, the political and regulatory environment, technology and wider economic conditions — forces the organization does not control but must work within. Supplier consolidation is such a force, whereas internal assets, policies and capabilities all describe things the organization itself owns, sets or performs.
Source: IIBA BABOK Guide — Analyze Current State (external influencers versus internal assets, policies and capabilities)Report a problem with this question
13. A team first agrees that all process content will be drawn using one agreed notation with a standard set of attributes, and then produces the actual process models for the initiative. Which pair correctly names these two things?
- A.The agreed conventions are a framework; the models produced are the architecture.
- B.The agreed conventions are a viewpoint; the models produced are a view.✓ Answer
- C.The agreed conventions are a template; the models produced are a baseline.
- D.The agreed conventions are a view; the models produced are the viewpoint.
A viewpoint is the set of conventions, notations and attributes agreed for representing one class of requirements, while a view is the actual set of requirements for a specific solution expressed through that viewpoint. Reversing the two is the common error; the collection of views is what makes up the requirements architecture, and neither term means a template or a baseline.
Source: IIBA BABOK Guide — Define Requirements Architecture (requirements viewpoints and views)Report a problem with this question
14. A junior analyst is told that the initiative needs a requirements architecture. A developer replies that the technical team already owns the system architecture, so the work would be duplicated. How should the analyst explain the difference?
- A.The requirements architecture describes the technology components and interfaces to be used.
- B.The requirements architecture is the same work, simply documented in business language.
- C.The requirements architecture structures the requirements so they fit together as one whole.✓ Answer
- D.The requirements architecture is the sequence in which requirements will be delivered.
Requirements architecture is the structure of the requirements themselves, assembled so that they support one another and collectively achieve the objectives rather than standing as a pile of individually valid statements. Confusing it with system or technology architecture is the standard trap, and it is neither a translation of technical design nor a delivery sequence.
Source: IIBA BABOK Guide — Define Requirements Architecture (purpose: requirements support one another to achieve the objectives)Report a problem with this question
15. An organization plans to connect its existing ordering process to a newly adopted externally hosted platform. A junior analyst is asked what this means for the analysis work. What is the most appropriate response?
- A.The analysis narrows to data mapping, since integration is mostly a matter of matching fields.
- B.The analysis is unchanged, because the requirements of the ordering process have not been altered.
- C.The analysis widens to new interfaces and dependencies, so requirement views must be reconciled.✓ Answer
- D.The analysis passes to the vendor, whose platform now determines the requirements to be met.
Integrating with another platform introduces interfaces and dependencies that cut across process, data and security requirements, and the requirements architecture exists to reconcile those views so the set tells one coherent story. The analyst also raises concerns such as data latency and protection for specialists to address rather than resolving them alone, and no technology choice transfers ownership of the requirements to a vendor.
Source: IIBA BABOK Guide — Define Requirements Architecture (relate and verify views; completeness); The Business Analysis Standard, technology as a contextual factorReport a problem with this question
16. Reviewing the requirements as a set, an analyst finds that the data model allows a customer to hold several active accounts while the process model assumes each customer has exactly one. What should the analyst do?
- A.Update the process model to allow several accounts, since the data model is more precise.
- B.Update the data model to allow a single account, since the process reflects how the work is really done.
- C.Record both as valid, because each model is correct from the viewpoint it was drawn from.
- D.Flag the contradiction for the stakeholders to resolve, noting where the two views disagree.✓ Answer
Completeness in a requirements architecture means there are no missing or contradictory requirements, so a conflict between two views is a genuine defect in the set even though each model reads correctly on its own. At foundational level the analyst identifies and documents the conflict and refers it for resolution instead of deciding which model wins, because that decision changes what the business has agreed.
Source: IIBA BABOK Guide — Define Requirements Architecture (completeness; relate and verify)Report a problem with this question
17. A stakeholder submits the following requirement for the new portal: the portal must be user-friendly. Measured against the quality characteristics of requirements, what is the main problem with it?
- A.It is not atomic, because friendliness bundles several separate capabilities into one line.
- B.It is neither unambiguous nor testable, so no one can judge objectively whether it is met.✓ Answer
- C.It is not prioritized, because no ranking against the other requirements has been given.
- D.It is not feasible, because usability cannot be achieved within the agreed time and budget.
Unambiguous means it is clear whether a solution meets the need, and testable means the requirement can be objectively verified, so a subjective adjective with no measurable expression fails both at once. Prioritization is a separate property that can be added later, and usability is perfectly feasible once it is expressed in terms someone can check.
Source: IIBA BABOK Guide — Verify Requirements and Designs (characteristics of requirements and designs quality: unambiguous, testable)Report a problem with this question
18. A requirement reads: the system shall record the payment, notify the customer, and update the ledger. A reviewer objects to the way the statement is written. Which quality characteristic is at issue?
- A.Atomic, because the statement combines three separate capabilities that should stand alone.✓ Answer
- B.Complete, because the statement omits detail needed to guide the work that follows.
- C.Concise, because the statement includes content that adds nothing to the need.
- D.Consistent, because the three parts conflict with requirements agreed elsewhere.
An atomic requirement is self-contained and can be understood, prioritized, traced and tested on its own, which a statement bundling three distinct capabilities cannot be, since any one part could pass while another fails. Concise concerns extraneous wording, consistent concerns conflicts with other requirements, and complete concerns missing detail, none of which is the defect here.
Source: IIBA BABOK Guide — Verify Requirements and Designs (characteristics of requirements and designs quality: atomic)Report a problem with this question
19. An analyst joining a new organization prefers a documentation format used at a previous employer. The new organization has approved templates and a required notation for process models. What should the analyst do?
- A.Use the preferred format, since the quality of the content matters more than its presentation.
- B.Use both formats in parallel so stakeholders can choose whichever one they find clearer.
- C.Use the preferred format for drafts and convert to approved templates only at sign-off.
- D.Use the organization's approved templates and notation, proposing changes through its channels.✓ Answer
Planning the business analysis approach requires it to fit the organization's own policies, procedures, methodologies and standards, so existing templates and an agreed notation take precedence over personal preference. Standards also make artifacts comparable and reviewable across initiatives; if they genuinely hinder the work, the analyst proposes a change through the organization's route rather than working around them.
Source: IIBA BABOK Guide — Plan Business Analysis Approach (organizational policies, methodologies, frameworks and standards)Report a problem with this question
20. An initiative is being delivered in short increments with stakeholder feedback after each one. A junior analyst asks when the business analysis approach should be settled. What is the best answer?
- A.Leave the approach informal, because adaptive work gains nothing from a defined method.
- B.Revisit the approach as each increment is planned, adapting it to what the feedback shows.✓ Answer
- C.Settle the approach once the first increment is accepted, and then keep it fixed from then on.
- D.Settle the approach fully at the start, so the team has a stable baseline to work against.
In adaptive work the business analysis approach is planned again at the start of each iteration, because the point of working in increments is to let feedback reshape how the work is done. Planning the approach once and freezing it is characteristic of predictive delivery, and having no defined approach at all is not adaptive practice but an absence of method.
Source: IIBA BABOK Guide — Plan Business Analysis Approach (planning repeats each iteration in adaptive approaches); The Business Analysis Standard, predictive and adaptive approachesReport a problem with this question

Practice questions based on the IIBA ECBA Exam Blueprint, The Business Analysis Standard and the BABOK Guide. ECBA, IIBA and BABOK are marks of the International Institute of Business Analysis; this site is not affiliated with or endorsed by IIBA. The exam was restructured around nine domains, so older preparation material organised by the previous knowledge areas is out of date — study the current blueprint on IIBA's site. IIBA publishes no passing score, so the threshold used here is our own practice target, not an official one. Based on the IIBA ECBA Exam Blueprint

1. A junior business analyst finds a detailed process description on the department's shared drive. The file lists no author, and the content refers to a team structure that no longer exists. What is the best next action before using it as input to the analysis?

2. During a peer review, a colleague works through each requirement statement asking whether it is written clearly enough that a tester could tell objectively if it has been met. Which activity is the colleague performing?

3. A business analyst supports an initiative in a regulated industry where every requirement change must be traceable to a named approver. The team is used to agreeing changes verbally in its daily stand-up. What should the analyst do?

4. Midway through an initiative, stakeholders keep asking who originally requested a particular requirement and how urgent it is. Nobody can answer without reopening old meeting notes. What should the analyst propose?

5. An analyst is asked to write a requirement so that other teams can reuse it in future initiatives. The draft currently states that the clerk types the claim number into the green legacy terminal screen. What should the analyst change?

6. After a session in which stakeholders reviewed the analyst's notes, two items were confirmed as accurate and one was disputed by two participants who remember it differently. What should the analyst do with this result?

7. A reporting solution meets its agreed specifications, but a year after release most departments still compile figures by hand. Interviews show that staff do not know what the solution can do and no one has defined who refreshes the underlying data. How is this best characterized?

8. A claims solution performs well at every step except one: an overnight data transfer that frequently finishes late, leaving the steps that follow working from stale figures. What does this situation illustrate?

9. While planning, the team notes the following: a vendor has said it will expose an interface next quarter, nothing has been agreed in writing, and work is being scheduled as though the interface will arrive. How should the analyst classify this statement?

10. Partway through analysis, an analyst learns that a regulation in one operating region forbids the data transfer the preferred design depends on. The analyst is working under the direction of a senior analyst. What is the best next action?

11. A solution produces an incorrect output roughly once a week and operations staff correct it by hand. Management asks the analysis team what should be done about it. What should the analyst contribute first?

12. While describing the current state, an analyst notes that two of the industry's major suppliers have merged and that the remaining supplier now dictates delivery terms. Where does this observation belong in the current-state description?

13. A team first agrees that all process content will be drawn using one agreed notation with a standard set of attributes, and then produces the actual process models for the initiative. Which pair correctly names these two things?

14. A junior analyst is told that the initiative needs a requirements architecture. A developer replies that the technical team already owns the system architecture, so the work would be duplicated. How should the analyst explain the difference?

15. An organization plans to connect its existing ordering process to a newly adopted externally hosted platform. A junior analyst is asked what this means for the analysis work. What is the most appropriate response?

16. Reviewing the requirements as a set, an analyst finds that the data model allows a customer to hold several active accounts while the process model assumes each customer has exactly one. What should the analyst do?

17. A stakeholder submits the following requirement for the new portal: the portal must be user-friendly. Measured against the quality characteristics of requirements, what is the main problem with it?

18. A requirement reads: the system shall record the payment, notify the customer, and update the ledger. A reviewer objects to the way the statement is written. Which quality characteristic is at issue?

19. An analyst joining a new organization prefers a documentation format used at a previous employer. The new organization has approved templates and a required notation for process models. What should the analyst do?

20. An initiative is being delivered in short increments with stakeholder feedback after each one. A junior analyst asks when the business analysis approach should be settled. What is the best answer?