CCNA Business Analysis Frameworks Questions

A requirements traceability matrix (RTM) is a grid that links requirements to their sources, such as business goals, stakeholder needs, and other requirements. It helps ensure that each requirement adds value and aligns with strategic objectives. In this scenario, the BA can use an RTM to demonstrate how the online banking feature's requirements support customer retention and call center reduction. This provides clear traceability from requirements to business goals.

A Requirements Traceability Matrix links each requirement backwards to its source and forwards to the test case verifying it, providing bidirectional coverage. This satisfies the stem's mapping constraint precisely, unlike a requirements document or scope statement that lacks that paired linkage.

Nominal group technique structures group input by having participants silently generate ideas, then share them one at a time, and finally vote or rank them. This prevents dominant personalities from controlling the discussion and ensures quieter members contribute. In this scenario, it directly addresses the imbalance in participation and helps the BA gather balanced input on the contentious process change.

The requirements traceability matrix maps each requirement to related artefacts — design documents, test cases, deliverables — in a grid, making dependencies and coverage visible. This satisfies the stem's demand for visual representation of relationships between requirements and other project artefacts, which a simple list cannot show.

Benchmarking compares an organisation's processes and performance metrics against a leading competitor's, revealing gaps and improvement opportunities. It directly satisfies the stem's constraint of comparing the sales order process with a competitor rather than analysing internally.

Prototyping helps refine requirements through iterative feedback.

A compliance-focused workshop brings together legal and finance experts who understand the regulatory landscape. This collaborative approach ensures that all relevant regulations are identified and documented early. It also creates a shared understanding and buy-in, which is critical for traceability. By involving these stakeholders from the start, the BA can establish a requirements traceability matrix that links each regulatory requirement to its source, design, and test cases, ensuring compliance throughout the lifecycle.

A facilitated workshop surfaces conflicting views simultaneously, letting the BA challenge inconsistencies and hidden agendas openly. This satisfies the sponsor's demand for a comprehensive, accurate requirement set within tight time and budget, since group elicitation resolves contradictions faster than sequential interviews.

MoSCoW analysis classifies requirements as Must, Should, Could or Won't have, forcing stakeholders to weigh value against implementation complexity. This satisfies the stem's prioritisation constraint by producing a ranked, agreed scope rather than an unranked list.

Brainstorming is a group creativity technique that encourages participants to generate a large volume of ideas without immediate judgement or criticism. It satisfies the workshop's constraint of generating creative ideas by deferring evaluation, allowing diverse contributions before the group filters and prioritises them.

Facilitated workshops bring cross-functional stakeholders together in a structured session to define requirements collaboratively. In this scenario, the BA can guide physicians, nurses, and IT staff to discuss and resolve conflicting opinions, ensuring all perspectives are heard. This technique is specifically designed to build consensus and produce documented requirements, making it ideal for the conflicting stakeholder views described.

Focus groups bring together a small group of stakeholders to discuss specific topics, allowing the BA to explore diverse opinions and build a shared understanding. For a large, diverse group, multiple focus groups can be conducted to represent different departments. They provide richer interaction than surveys and help uncover requirements that might not emerge in individual interviews. This makes focus groups suitable for eliciting requirements from varied stakeholders in the ERP project.

Stakeholder analysis is a key business analysis activity.

Document analysis systematically reviews existing artefacts — project documentation, process flows and system manuals — to elicit requirements and understand the current environment. It satisfies the scenario's constraint by gathering baseline information without directly involving stakeholders, making it the appropriate technique for reviewing existing materials.

Round-robin brainstorming gives every attendee a structured turn to speak, which directly counters a dominant participant. Because the recruiters are invited to contribute in sequence, their process concerns surface before the HR director can steer the conversation back to dashboards. It is a recognized facilitation technique for equalizing participation and produces more complete requirements inputs for the onboarding system.

Delphi circulates anonymous questionnaires across several rounds, feeding back aggregated responses until estimates converge. Anonymity removes seniority and personality pressure that blocks open debate, satisfying the requirement to reach consensus when stakeholder input conflicts during prioritisation.

MoSCoW sorts requirements into Must, Should, Could and Won't, so the team can guarantee the Must-haves ship by the fixed deadline while lower-value items absorb any resource shortfall. This directly satisfies the stem's strict deadline and limited resources by protecting essential scope.

The Power/Interest Grid directly satisfies the initiation-phase need to categorise stakeholders by mapping each one against two axes: authority to influence project outcomes and level of concern in results. This yields four groups — manage closely, keep satisfied, keep informed, monitor — guiding engagement priorities before detailed planning begins.

A prioritisation matrix scores each requirement against weighted business criteria such as revenue impact and compliance, producing an objective ranking that resolves the sales, finance, IT and support conflict and yields the single balanced recommendation the sponsor requested.

If the proposed solution misses the root cause, requirements were derived from an incomplete needs assessment. The analyst should revisit that assessment and adjust requirements so the solution addresses the underlying business problem rather than its symptoms.

Traceability links each requirement to its originating source, so the regulatory compliance origin is documented and auditable. Showing the sponsor that link demonstrates the requirement's mandatory external driver, resolving the alignment concern with evidence rather than opinion.

MoSCoW sorts requirements into Must have, Should have, Could have and Won't have categories, letting the business analyst rank conflicting stakeholder demands by delivery criticality. This directly satisfies the stem's need to identify which requirements are most critical and deliver them first.

Technical feasibility hinges on whether the integration can be built with available resources and expertise. If the proprietary protocol is obscure and no developers have the necessary skills, the project may be delayed or fail. Assessing skill availability is therefore a critical first step in evaluating technical feasibility.

A maintained traceability matrix links each requirement to its business objective and records priority relationships. Missing objective links and conflicting priorities signal that these mappings were never captured or updated, so validation exposed orphaned and contradictory requirements rather than defects in the requirements themselves.

A requirements traceability matrix maps each requirement to its source, linking business needs, stakeholders and downstream deliverables. This directly satisfies the stem's need to trace every requirement back to its origin, and it also supports later impact analysis when requirements change.

A needs assessment compares the current business state against the desired future state, exposing gaps that justify a new software system. This gap analysis defines what the solution must address before requirements or design work begins.

Assessing the security policy's impact and escalating options to the sponsor respects the frozen baseline while recognising that only the sponsor can authorise scope change. The business analyst cannot unilaterally alter scope, so presenting impact analysis enables an informed decision on compliance versus schedule.

Observation captures the actual step-by-step workflow as performed in the real work environment, including undocumented variations and workarounds. This satisfies the stem's constraint of understanding current task execution before design, which interviews or surveys would only approximate through recall.

A context diagram shows the solution as a single process surrounded by external entities such as customers, payment gateways, and regulatory agencies. It defines what is inside the system boundary and what remains external. For a billing system replacement, this clearly communicates included capabilities and excluded interfaces. It is the standard technique for establishing and visualizing scope boundaries.

Solution Evaluation covers assessing a deployed solution's performance and value, so measuring adoption rates, support ticket volumes and response times fits directly. These metrics verify whether the CRM meets business needs post-implementation, the domain's core purpose, rather than eliciting requirements or planning the project itself.

The Power/Interest Grid plots stakeholders on two axes, authority to influence outcomes against concern for the work, sorting them into prioritised quadrants. This lets the analyst target engagement effort where it matters most across a diverse regulatory stakeholder group.

A flow chart maps a process as ordered steps connected by directional arrows, including decision branches, giving the visual sequence the business analyst described. That step-by-step diagrammatic representation is exactly the technique the stem specifies, unlike textual or matrix-based elicitation methods.

High CPU usage could cause slow responses, and network is fine, so server resources are the logical next check.

Engaging key stakeholders early and continuously lets the business analyst capture regulatory requirements, surface concerns and secure buy-in before decisions harden. Ongoing involvement sustains alignment through the project, reducing the likelihood of late resistance or compliance gaps that jeopardise acceptance.

Linking high-risk regulatory requirements to test cases and business objectives first directly satisfies the compliance constraint, since regulators demand demonstrable validation of those specific requirements. This risk-based sequencing also respects the testing team's schedule pressure by concentrating traceability effort where audit exposure is greatest, rather than attempting full matrix completion.

Verifiability requires that satisfaction can be objectively demonstrated. Converting the vague term into measurable acceptance criteria, such as task completion times or error rates, gives testers a concrete standard to evaluate. This preserves the underlying usability intent while making the requirement testable and auditable in the loan origination system's acceptance process.

Cost-benefit analysis quantifies expected costs against anticipated benefits, producing financial metrics such as ROI, NPV or payback period. It directly satisfies the constraint of determining whether the proposed software development project is financially viable before committing organisational resources.

A business case justifies investment by weighing expected benefits against costs, so cost-benefit analysis with financial metrics such as ROI, payback period and NPV provides the quantitative evidence decision-makers need to approve, reject or prioritise the project.

REQ02 remains in Draft, so it cannot progress until stakeholders validate it. Convening a review meeting moves it toward Approved status, resolving the inconsistency with REQ01. Editing status directly or proceeding to design would bypass the approval gate the requirements tool is enforcing.

The requirements traceability matrix links each requirement to its source, design, test cases and deliverables across the lifecycle. It satisfies the need to capture and manage requirements continuously, tracking status and coverage from elicitation through verification.

The RTM maps each requirement backward to its source and forward to design components, deliverables, and test cases. When a new regulation appears, the BA can trace its impact across the matrix to find every affected requirement and associated work product. This supports impact analysis, change control, and targeted regression testing, making it the primary benefit in a regulatory compliance project.

Stakeholder mapping is a technique that visually represents stakeholders based on attributes such as power, interest, influence, or impact. It helps the BA identify who is affected and prioritize engagement strategies. In this scenario, mapping would clarify which departments need more communication or involvement, making it a correct choice for identifying and prioritizing stakeholders.

Solution scope should cover what the current release will deliver, while deferred capabilities belong in a managed backlog where they retain visibility without inflating the baseline. This satisfies the sponsor's concern that future options are not lost and the operations manager's need for a deliverable release. The backlog can be prioritized and scheduled in subsequent releases as value and capacity allow.

Alternatives analysis documents the other options considered and why the recommended approach was selected, demonstrating that the business case rests on comparison rather than assumption. It satisfies the stem because reviewers need assurance that no cheaper or lower-risk route was overlooked.

Agile's iterative, time-boxed increments let the team reprioritise a evolving backlog each sprint, directly satisfying the stem's rapidly changing requirements and need for quick value delivery. Unlike predictive approaches, working software is released frequently, so user feedback shapes subsequent iterations rather than being deferred to a single end-stage acceptance phase.

Alternatives considered is a mandatory business case component because it documents the options evaluated against the recommended solution, including their costs, benefits and rejection rationale. Without it, decision-makers cannot verify that the chosen approach delivers optimal value, so the business case fails the completeness requirement tested in this scenario.

The Delphi Technique gathers anonymous expert responses through iterative questionnaires, then feeds summarised results back for re-rating until consensus emerges. This directly satisfies the stem's constraint of anonymous voting among stakeholders, removing dominance and groupthink effects that open discussion would introduce. Nominal group technique differs by requiring face-to-face voting.

The business case justifies the investment by documenting the problem, options, costs, benefits and risks, and it is the principal output that follows needs assessment. It satisfies the stem by translating identified business needs into a decision-ready justification for proceeding.

Facilitating a structured discussion lets the business analyst surface the conflicting requirements, clarify underlying interests, and guide stakeholders to a mutually agreed resolution. This directly addresses the conflicting information provided during elicitation, ensuring the documented requirements reflect genuine consensus rather than one party's assumption.

Written feedback suits this stakeholder's demonstrated preference for asynchronous, considered input. Surveys or structured forms capture their detailed comments without forcing verbal contribution in meetings, satisfying the engagement need for a channel matched to their communication style.

Surveys gather structured input from many distributed stakeholders efficiently, satisfying the elicitation need to collect broad requirements data. They suit large or geographically dispersed groups where interviews are impractical, and responses can be analysed for common themes and priorities.

An entity-relationship diagram (ERD) is specifically designed to model data entities and their relationships. Entities such as Employee, Department, and Job Position can be represented with attributes and connected via relationships (e.g., an employee belongs to a department, holds a job position). ERDs are the standard tool for data modeling in business analysis, making them ideal for this scenario.

Downward traceability to design, build, and test artifacts enables verification that every requirement is implemented and validated, and it supports impact analysis by revealing exactly which components and test cases a change would touch. In a regulated bank, auditors rely on this chain to demonstrate that each mandated control was built and independently tested before release.

When a KPI fails to improve after implementation, the underlying cause must be diagnosed before any further action. Root cause analysis examines whether the solution, data, process or assumptions are at fault, directing corrective effort rather than guessing at remedies.

The Delphi technique collects anonymous expert responses through multiple rounds until consensus emerges. Because participants never meet face-to-face, dominant personalities cannot sway the group, and time zone differences are less problematic. It is well suited to conflicting opinions because each round allows experts to reconsider their views based on summarized feedback. This makes it a strong choice for the BA's objectives.

Conflicting requirements stem from divergent stakeholder interests, not technical defects, so negotiation is the only route to an agreed outcome. Facilitating a meeting lets the business analyst surface each party's underlying need, then broker a compromise that both accept, preserving requirements traceability and stakeholder buy-in.

Prototyping builds a working model of the solution so stakeholders can interact with it and reveal requirements they cannot articulate abstractly. It elicits and refines requirements through iterative feedback, making it a recognised elicitation technique.

Gap analysis compares the documented current state against the target state to identify the differences that must be addressed. By contrasting as-is invoice processing with the to-be process, the analyst pinpoints missing capabilities and required changes, which is precisely the technique the scenario describes.

Process modeling is a technique used to represent how work will be performed in the future state. By visually mapping the process with cross-functional participants, the BA can capture inputs from operations, IT, and compliance, resolve differences, and build a shared understanding. It directly supports designing the future-state onboarding process collaboratively, making it the best choice here.

Scalability directly addresses the limited-budget constraint: a lightweight framework can be tailored to a small project's scope, avoiding overheads that larger methodologies impose. Selecting a framework whose ceremony and documentation scale down prevents wasted effort, keeping analysis proportionate to the project's size and complexity.

Splitting oversized stories into smaller, specific ones with clear acceptance criteria makes each estimable and completable within a two-week sprint, directly resolving the team's complaint that the current stories are too large and vague to size.

Process modelling maps current workflows as inputs, activities, decision points and outputs, exposing handoffs, delays and redundancies. This directly satisfies the business analyst's need to understand existing CRM workflows and pinpoint improvement areas, unlike elicitation techniques that gather requirements without depicting sequential flow.

A stakeholder map visually categorises affected parties by influence and interest, exposing gaps that ad hoc lists miss. Validating it with subject matter experts confirms coverage of overlooked groups, directly satisfying the requirement to consider all affected parties.

Splitting oversized stories into sprint-sized increments with explicit acceptance criteria directly addresses the two constraints blocking demonstrable functionality: stories too large to finish within a two-week sprint, and undefined completion conditions. Smaller, testable slices let the team deliver working software each sprint, reducing documentation overhead and giving the product owner something to demo.

Stakeholder availability influences technique choice (e.g., workshops vs surveys).