Courseiva

CCNA Business Analysis Frameworks Questions

22 of 172 questions · Page 3/3 · Business Analysis Frameworks · Answers revealed

151
MCQeasy

A business analyst is working on a project to implement a new inventory management system. The project charter has been approved, and the project manager has asked the analyst to begin requirements elicitation. The analyst notices that the business case did not include a clear problem statement or measurable objectives. Several stakeholders are uncertain about the project's purpose and expected outcomes. The project sponsor is eager to move forward. As the business analyst, what should you do first?

A.Create a requirements management plan to document how requirements will be handled.
B.Proceed with requirements elicitation and clarify objectives later during prioritization.
C.Conduct a stakeholder analysis to identify who needs to be involved in defining objectives.
D.Work with the sponsor and key stakeholders to refine the business case with a clear problem statement and measurable objectives.
AnswerD

A solid business case provides direction and success criteria for all subsequent activities.

Why this answer

The business case provides the foundational justification for the project, including the problem statement and measurable objectives. Without these, requirements elicitation lacks clear direction, leading to scope creep and misaligned outcomes. The business analyst must first refine the business case with the sponsor and key stakeholders to ensure a shared understanding of the project's purpose and success criteria before proceeding with requirements activities.

Exam trap

The trap here is that candidates often jump to stakeholder analysis (Option C) as a first step, but the CAPM exam tests the sequence of business analysis planning: the business case must be validated before any requirements activities begin.

How to eliminate wrong answers

Option A is wrong because creating a requirements management plan is a process that follows after the business case is clarified; it does not address the missing problem statement and objectives. Option B is wrong because proceeding with requirements elicitation without clear objectives risks gathering irrelevant or conflicting requirements, wasting effort and increasing rework. Option C is wrong because stakeholder analysis identifies who to involve but does not directly resolve the missing problem statement and measurable objectives; the business case must be refined first to guide stakeholder engagement.

152
Multi-Selecthard

Which THREE techniques are commonly used for requirements elicitation?

Select 3 answers
A.Surveys
B.SWOT analysis
C.Brainstorming
D.Interviews
E.Gantt charts
AnswersA, C, D

Surveys can gather requirements from a large number of stakeholders.

Why this answer

Surveys, brainstorming, and interviews are all commonly used requirements elicitation techniques. Surveys efficiently gather input from a large number of stakeholders, brainstorming facilitates creative idea generation in a group setting, and interviews allow for in-depth exploration of individual stakeholder needs. SWOT analysis and Gantt charts are not elicitation techniques; they are used for strategic analysis and project scheduling, respectively.

Exam trap

PMI often tests the distinction between requirements elicitation techniques and project management tools, so candidates mistakenly select SWOT analysis or Gantt charts because they are familiar terms, even though they are not used for eliciting requirements.

153
Multi-Selecteasy

A BA is identifying stakeholders. Which TWO techniques are commonly used for stakeholder analysis?

Select 2 answers
A.Mind mapping
B.Work breakdown structure
C.Requirements traceability matrix
D.Power/interest grid
E.Influence/impact grid
AnswersD, E

Classifies stakeholders by power and interest.

Why this answer

Stakeholder analysis involves identifying and classifying stakeholders based on their influence, interest, power, and impact. The power/interest grid (Option D) and influence/impact grid (Option E) are two commonly used techniques for this classification. Option A (mind mapping) is a brainstorming technique, not specific to stakeholder analysis.

Option B (work breakdown structure) is for scope decomposition. Option C (requirements traceability matrix) is for tracking requirements, not stakeholders.

154
MCQhard

After solution implementation, the business analyst discovers that a key performance indicator (KPI) has not improved as expected. What is the most appropriate next step?

A.Conduct a root cause analysis to identify why the solution is underperforming.
B.Request additional budget for a new solution.
C.Immediately escalate to the project sponsor.
D.Document the discrepancy in the lessons learned.
AnswerA

Root cause analysis guides corrective actions.

Why this answer

Conducting root cause analysis helps identify why the solution is underperforming. Option B is wrong because requesting additional budget without analysis is premature. Option C is wrong because escalation without analysis is premature.

Option D is wrong because documenting in lessons learned without action is inadequate.

155
Multi-Selecteasy

Which THREE elements should be included in a needs assessment? (Choose three.)

Select 3 answers
A.Business goals and objectives
B.User interface mockups
C.Problem or opportunity statement
D.Current state analysis
E.Proposed system architecture
AnswersA, C, D

Needs must align with goals.

Why this answer

Correct are A (Business goals and objectives), C (Problem or opportunity statement), and D (Current state analysis). B and E are solution-oriented artifacts, not part of a needs assessment.

156
MCQmedium

A business analyst is tasked with verifying that the solution meets the defined requirements. Which activity is part of the verification process?

A.Peer review
B.Testing
C.Quality assurance
D.Validation
AnswerB

Testing directly verifies that the solution meets requirements.

Why this answer

Testing is a key verification activity that checks if the solution conforms to specified requirements.

157
MCQmedium

A project manager is leading a business analysis effort to define the requirements for a new inventory management system. The stakeholders have conflicting needs regarding real-time data updates versus batch processing. Which business analysis technique should the PM use to facilitate a decision?

A.Develop a process flow diagram to map the current inventory process.
B.Create a Gantt chart to schedule requirement gathering activities.
C.Use a decision tree to analyze the impact of each approach on project cost and timeline.
D.Conduct a requirements validation workshop to review the requirements.
AnswerC

Decision trees evaluate consequences of different decisions, helping stakeholders choose.

Why this answer

A decision tree is a structured business analysis technique that evaluates the trade-offs between conflicting stakeholder requirements—in this case, real-time data updates versus batch processing—by quantifying the impact of each approach on project cost and timeline. This enables the project manager to facilitate an objective, data-driven decision rather than relying on subjective preferences.

Exam trap

The trap here is that candidates confuse requirement elicitation or documentation techniques (like process flow diagrams or validation workshops) with analytical decision-making tools, assuming any stakeholder conflict is resolved by gathering more requirements rather than by quantitatively comparing the impacts of each option.

How to eliminate wrong answers

Option A is wrong because developing a process flow diagram maps the current inventory process, which documents existing workflows but does not analyze the cost or schedule implications of the two conflicting technical approaches. Option B is wrong because a Gantt chart is a project scheduling tool used to plan and track requirement gathering activities, not a technique for evaluating trade-offs between real-time and batch processing. Option D is wrong because a requirements validation workshop reviews and confirms that requirements are complete and correct, but it does not provide a quantitative analysis of cost and timeline impacts needed to resolve the conflict between real-time updates and batch processing.

158
MCQhard

A business analyst is evaluating whether a proposed solution aligns with the organization's strategic goals. Which business analysis technique should be used?

A.MoSCoW analysis
B.Gap analysis
C.Feasibility study
D.SWOT analysis
AnswerD

SWOT analysis helps evaluate strategic alignment by examining internal and external factors.

Why this answer

SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) is the correct technique because it directly evaluates how a proposed solution aligns with the organization's strategic goals by examining internal capabilities and external market factors. This technique helps the business analyst determine whether the solution leverages organizational strengths and opportunities while mitigating weaknesses and threats, ensuring strategic fit.

Exam trap

The trap here is that candidates often confuse SWOT analysis with gap analysis, assuming both assess alignment, but gap analysis focuses on performance discrepancies rather than strategic fit with organizational goals.

How to eliminate wrong answers

Option A is wrong because MoSCoW analysis (Must have, Should have, Could have, Won't have) is a prioritization technique used to categorize requirements, not to assess alignment with strategic goals. Option B is wrong because gap analysis identifies the difference between the current state and desired future state, but it does not directly evaluate strategic alignment with organizational goals. Option C is wrong because a feasibility study assesses whether a solution is technically, operationally, and economically viable, but it does not specifically measure alignment with strategic objectives.

159
MCQmedium

A business analyst discovers that two requirements conflict with each other. What is the best strategy to resolve this conflict?

A.Ask the project sponsor to choose which requirement to keep
B.Facilitate a meeting with the key stakeholders to negotiate a resolution
C.Document both requirements and let the development team decide
D.Include both requirements and add a third requirement to reconcile them
AnswerB

Collaborative negotiation is the best approach to resolve conflicts.

Why this answer

Facilitating a meeting with stakeholders allows for negotiation and collaboration to resolve the conflict. Option A is incorrect because asking the sponsor to choose may not address the underlying concerns and could bypass stakeholder input. Option C is incorrect because leaving the decision to the development team may lead to a technical decision that doesn't consider business needs.

Option D is incorrect because including both conflicting requirements without resolution could create inconsistencies, and adding a third requirement doesn't reconcile the original conflict.

160
MCQhard

Refer to the exhibit. The business analyst is analyzing system requirements for a payment gateway. Based on this error log, which non-functional requirement is most likely to be updated?

A.Usability requirement for user-friendly error messages
B.Performance requirement to increase timeout threshold
C.Availability requirement for 99.99% uptime
D.Security requirement to encrypt transactions
AnswerB

Correct: Timeout is a performance attribute.

Why this answer

The error describes a transaction timeout, which relates to system performance. Therefore, the performance requirement for timeout threshold should be reviewed and potentially increased.

161
MCQeasy

A project manager is defining the business analysis approach for a new software development project. The stakeholders are located in different countries and have varying levels of technical expertise. Which business analysis framework is most suitable for ensuring effective communication and collaboration?

A.Agile
B.PRINCE2
C.Lean
D.Waterfall
AnswerA

Agile promotes continuous collaboration and adaptability.

Why this answer

Agile emphasizes iterative communication and collaboration, making it ideal for distributed teams with diverse expertise.

162
Multi-Selecteasy

Which TWO of the following are commonly used requirements elicitation techniques?

Select 2 answers
A.Monte Carlo Simulation
B.Prototyping
C.Parametric Estimating
D.Brainstorming
E.Variance Analysis
AnswersB, D

Prototyping allows stakeholders to interact with a model to refine requirements.

Why this answer

Brainstorming and Prototyping are direct elicitation techniques. Variance Analysis, Monte Carlo Simulation, and Parametric Estimating are from other knowledge areas (monitoring, risk, cost).

163
MCQeasy

Refer to the exhibit. A business analyst has documented the current and target states for invoice processing. What business analysis technique is being used?

A.Feasibility study
B.SWOT analysis
C.Gap analysis
D.Root cause analysis
AnswerC

Gap analysis compares current and desired states to identify differences.

Why this answer

The business analyst is comparing the current state and target state of invoice processing to identify the differences or gaps that need to be addressed. This is the core definition of gap analysis, which is a technique used to determine the steps required to move from the current state to the desired future state. The exhibit explicitly shows a 'Current State' and 'Target State' for invoice processing, making gap analysis the correct technique.

Exam trap

The trap here is that candidates may confuse gap analysis with root cause analysis because both involve analyzing problems, but gap analysis focuses on the difference between current and target states, while root cause analysis digs into the origin of a single problem.

How to eliminate wrong answers

Option A is wrong because a feasibility study assesses whether a project or solution is viable in terms of cost, time, and resources, not by comparing current and target states. Option B is wrong because SWOT analysis evaluates internal Strengths and Weaknesses and external Opportunities and Threats, not a direct comparison of current and target process states. Option D is wrong because root cause analysis is used to identify the underlying cause of a problem or defect, not to document the difference between current and target states.

164
MCQeasy

Refer to the exhibit. Based on the server health check, which requirement is most likely to be triggered?

A.Add more memory
B.Replace the server
C.Increase CPU capacity
D.Expand disk space on /var/log
AnswerD

Correct: Disk usage at 92% with critical error.

Why this answer

The error message indicates a critical disk space issue on /var/log, so expanding disk space is the most likely requirement. CPU and memory are within normal ranges, and replacing the server is premature.

165
MCQeasy

A business analyst is selecting a business analysis framework for a small project with limited budget. Which framework characteristic is most important to consider?

A.Scalability to fit the project size and complexity
B.Alignment with industry standards
C.Comprehensiveness to cover all possible scenarios
D.Integration with existing project management tools
AnswerA

Scalability allows the framework to be adapted without waste.

Why this answer

For a small project with a limited budget, the most important characteristic of a business analysis framework is scalability, because it allows the framework to be tailored to the project's size and complexity without incurring unnecessary overhead or costs. A framework that is too rigid or comprehensive would waste resources on activities that do not add value for a small project, while a scalable approach ensures that only essential analysis tasks are performed. This directly aligns with the principle of 'just enough' business analysis, which is critical when budget constraints are tight.

Exam trap

The trap here is that candidates often choose 'comprehensiveness' (Option C) because they assume a framework must cover all scenarios to be effective, but the CAPM exam tests the understanding that frameworks must be tailored to project constraints, and for a small budget, scalability is the key enabler of cost efficiency.

How to eliminate wrong answers

Option B is wrong because alignment with industry standards, while beneficial for consistency and interoperability, is not the most critical factor when budget is limited; a small project can still succeed without strict adherence to standards if the framework is scalable. Option C is wrong because comprehensiveness to cover all possible scenarios would introduce excessive documentation and analysis activities, driving up costs and time, which is counterproductive for a small project with a limited budget. Option D is wrong because integration with existing project management tools is a convenience feature, not a primary driver; a scalable framework can be adapted to work with minimal tooling, and forcing integration could add unnecessary expense.

166
MCQeasy

A business analyst is working on a project to develop a mobile banking application. During the requirements analysis phase, the BA creates a set of user stories and acceptance criteria. The BA then conducts a peer review with the development team. The team points out that the stories are too large and vague to estimate. The BA needs to refine the requirements to make them actionable. The project is using an agile methodology with two-week sprints. What should the BA do?

A.Split the large user stories into smaller, more specific stories with acceptance criteria.
B.Add more detail to the existing user stories and acceptance criteria.
C.Create a prototype to clarify requirements and then rewrite stories.
D.Ask the development team to re-estimate the stories as they are.
AnswerA

Splitting stories makes them estimable and sprint-ready.

Why this answer

In agile methodologies, user stories must be small enough to fit within a single sprint and provide clear, testable acceptance criteria for estimation and development. Splitting large, vague stories into smaller, specific stories with acceptance criteria directly addresses the team's inability to estimate, enabling accurate sprint planning and incremental delivery. This aligns with the INVEST principle (Independent, Negotiable, Valuable, Estimable, Small, Testable) for effective user stories.

Exam trap

PMI often tests the misconception that adding more detail or creating a prototype is sufficient to make stories actionable, but the core agile requirement is that stories must be small enough to be estimable and completed within a single sprint.

How to eliminate wrong answers

Option B is wrong because simply adding more detail to existing large stories does not reduce their size; they remain too large for a two-week sprint and still cannot be reliably estimated. Option C is wrong because creating a prototype is a discovery technique that may clarify requirements but does not inherently produce actionable, estimable user stories; it adds an extra step and delays refinement. Option D is wrong because asking the team to re-estimate stories that are known to be too large and vague will yield unreliable estimates, violating the core agile principle that stories must be estimable to be planned.

167
MCQhard

Before approving a major IT system upgrade, the steering committee wants to understand whether the proposed solution is technically feasible and aligns with the organization's strategic goals. The business analyst should recommend conducting which type of analysis?

A.Feasibility study
B.Business case development
C.Return on investment (ROI) analysis
D.SWOT analysis
AnswerA

Feasibility study evaluates viability before significant investment.

Why this answer

A feasibility study assesses technical, economic, and operational viability before committing to a project. A business case is built after feasibility; ROI analysis is part of the business case; SWOT analysis is for strategic positioning.

168
MCQmedium

In a project to implement a new customer relationship management (CRM) system, the business analyst needs to understand the current workflows and identify areas for improvement. Which technique should be used?

A.Document analysis
B.Process modeling
C.Benchmarking
D.Root cause analysis
AnswerB

Process modeling captures current workflows and identifies improvement opportunities.

Why this answer

Process modeling is the correct technique because it visually maps out the current workflows, showing the sequence of activities, decision points, and handoffs in the CRM system. This allows the business analyst to identify inefficiencies, bottlenecks, and areas for improvement in the existing processes before designing the new system.

Exam trap

The trap here is that candidates often confuse 'document analysis' (reviewing existing materials) with 'process modeling' (creating a visual representation of workflows), leading them to pick A when the question specifically asks for a technique to understand and improve workflows.

How to eliminate wrong answers

Option A is wrong because document analysis involves reviewing existing documentation (e.g., user manuals, process documents) to gather information, but it does not actively model or visualize workflows to identify improvement areas. Option C is wrong because benchmarking compares performance metrics against industry standards or competitors, which is useful for setting targets but not for understanding current internal workflows. Option D is wrong because root cause analysis is used to identify the underlying causes of a specific problem or defect, not to map and analyze entire workflows for improvement.

169
Multi-Selecteasy

Which TWO of the following are considered business analysis planning activities?

Select 2 answers
A.Conducting interviews to gather requirements
B.Developing wireframes for the user interface
C.Defining project success criteria
D.Conducting stakeholder analysis
E.Selecting elicitation techniques
AnswersD, E

Stakeholder analysis is a key planning activity.

Why this answer

Business analysis planning activities involve identifying stakeholders and determining how to elicit requirements. Conducting stakeholder analysis (D) is a planning activity to understand who will be impacted and their involvement. Selecting elicitation techniques (E) is also planning as it defines how requirements will be gathered.

Option A (conducting interviews) is part of elicitation execution, not planning. Option B (developing wireframes) is solution design. Option C (defining project success criteria) is typically part of project management or scope definition, not specifically business analysis planning.

170
MCQeasy

A business analyst is using a business analysis framework to identify stakeholders. Which technique is most effective for ensuring all affected parties are considered?

A.Brainstorming with the project team
B.Conducting one-on-one interviews with known stakeholders
C.Creating a stakeholder map and validating with experts
D.Distributing a questionnaire to the organization
AnswerC

A stakeholder map systematically identifies and categorizes stakeholders.

Why this answer

Stakeholder mapping, when validated with experts, systematically identifies all affected parties by visually representing relationships, influence, and impact. This technique leverages expert judgment to cross-check the map against organizational knowledge, ensuring no stakeholder group is overlooked. It is more comprehensive than ad-hoc methods because it follows a structured framework (e.g., PMI's stakeholder identification process) and incorporates validation to fill gaps.

Exam trap

The trap here is that candidates confuse 'brainstorming' (Option A) as a comprehensive technique, but the CAPM exam requires a structured, validated approach (stakeholder mapping with expert validation) to ensure all affected parties are considered, not just those immediately visible.

How to eliminate wrong answers

Option A is wrong because brainstorming with the project team is unstructured and relies on the team's limited perspective, often missing stakeholders outside their immediate awareness (e.g., regulatory bodies or downstream users). Option B is wrong because one-on-one interviews with known stakeholders only capture their personal views, creating a snowball effect that may still miss indirect or marginalized stakeholders not in the interviewee's network. Option D is wrong because distributing a questionnaire to the organization is passive and relies on self-identification, which can lead to low response rates and overlook stakeholders who do not see themselves as affected (e.g., future users or external auditors).

171
MCQmedium

A business analyst is working on a project to implement a new human resources software. The project is using an Agile framework with two-week sprints. After three sprints, the product owner is frustrated because the team has not delivered any working functionality that can be demoed. The business analyst realizes that the user stories lack acceptance criteria and are too large to complete in a sprint. The team is also spending too much time on documentation. As the business analyst, what should you do to improve the situation?

A.Replace the product owner with a more experienced one who understands Agile.
B.Reduce documentation requirements to free up more development time.
C.Work with the product owner to break down large stories into smaller ones with clear acceptance criteria.
D.Increase the sprint duration to four weeks to allow more time for completion.
AnswerC

Smaller stories with acceptance criteria are easier to estimate and demonstrate.

Why this answer

The core issue is that user stories are too large and lack acceptance criteria, which prevents the team from delivering working functionality within the sprint. By working with the product owner to break down large stories into smaller ones with clear acceptance criteria, the team gains clarity on what to build and can complete work within a sprint. Option A is incorrect because replacing the product owner does not address the root cause of poorly defined stories.

Option B is incorrect because reducing documentation does not fix the lack of acceptance criteria or story sizing. Option D is incorrect because increasing sprint duration does not solve the underlying problem of story quality and may reduce feedback frequency.

172
Multi-Selecthard

Which THREE factors should a business analyst consider when selecting an elicitation technique for a project?

Select 3 answers
A.Availability of stakeholders
B.Project manager's preference
C.Type of information needed
D.Cost of the technique
E.Level of detail required
AnswersA, C, E

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

Why this answer

A is correct because stakeholder availability directly impacts the feasibility of scheduling and conducting elicitation activities such as interviews, workshops, or focus groups. If key stakeholders are unavailable, the chosen technique may be impractical or yield incomplete information, making this a primary logistical consideration in technique selection.

Exam trap

The trap here is that candidates often confuse 'project manager's preference' or 'cost' as valid selection criteria, but the CAPM exam specifically tests the BABOK's three primary factors: stakeholder availability, type of information needed, and level of detail required.

← PreviousPage 3 of 3 · 172 questions total

Ready to test yourself?

Try a timed practice session using only Business Analysis Frameworks questions.