150 Cbap v3 Questions Answers
150 Cbap v3 Questions Answers
150 Cbap v3 Questions Answers
150
MIXED
QUESTIONS
&
ANSWERS
MIXED 150 QUESTIONS & ANSWERS
(answers are at end, and not as marked with the questions)
1.
2.
You have been asked to confirm your results after a requirements workshop. Why is
that important?
a. To ensure the project manager
understands the requirements for project
planning.
3.
2
4.
5.
c. Requirements Analysis/Validate
Requirements
d. Requirements Analysis/Verify
Requirements
6.
c. Meta-data definition.
3
7.
b. Requirements versioning.
c. Problem baselining.
d. Problem tracking.
8.
9.
4
10.
11.
5
12.
13.
You are starting to recruit your participants for your focus group.
You are looking for a very diverse group of people. The participants
you are looking for would be categorized as what?
a. Homogeneous.
b. Heterogeneous.
c. Esoteric.
d. Homogenized.
14.
b. Assumptions.
c. Products.
d. Culture.
6
15.
b. Technical constraint.
c. Business constraint.
d. Business assumption.
16.
b. Requirements analysis.
c. Requirements elicitation.
17.
b. Sense of urgency.
c. Sense of confidence.
d. Trustworthiness.
7
18.
b. Observation.
d. Document analysis.
19.
b. Regulator.
c. Sponsor.
d. Tester.
20.
b. Brainstorming.
8
21.
d. Requirements adhere to an
organization template to ensure they
help support strategic direction of the
organization.
22.
9
used.
23.
b. Vision document.
c. Supplementary requirements
specification.
24.
b. RBS.
c. OBS.
d. TBS.
25.
b. Business Analyst.
10
26.
27.
c. Decomposition of Organizational
Processes.
d. Decomposition of Deliverables.
28.
11
29.
b. Value.
c. Necessity.
d. Hierarchy.
30.
A new baseline for requirements and an updated coverage matrix are outputs of what
activities?
a. Maintain requirements plan and Manage
Requirements Traceability.
31.
12
and methodologies and processes.
32.
33.
You have been asked to make a recommendation for an initiative that the
organization is thinking about undertaking. The organization has provided
some initial estimates and high-level costs. Which techniques might you use
in preparing your recommendation?
a. Risk analysis, SWOT analysis,
functional decomposition.
34.
b. Transport requirements.
c. Timeline requirements.
13
d. Training requirements.
35.
36.
You have had several interviews this week for your project. Several problems
have come up. So many have come up that your project manager suggested
that you track them. Why?
a. Used for historical purposes and
project planning by the project
manager.
14
37.
38.
b. Solution approach.
c. Verified requirements.
d. Required capabilities.
39.
b. Research.
d. Formal meetings.
15
40.
What is the purpose of the 'Define Solution Scope' task in the Enterprise
Analysis knowledge area?
a. To make sure the estimates given to
the project manager are accurate.
41.
Some solution components, especially software, will have defects and may
require an investigation of the root cause of problems by which of the
following stakeholders:
a. Domain SME.
b. Implementation SME.
c. Business Analyst.
d. Tester.
42.
b. Context diagram.
c. Fishbone diagram.
16
43.
44.
45.
c. Business architecture.
d. GAP analysis.
17
46.
b. Prototyping.
d. Functional composition.
47.
48.
18
49.
You are walking your stakeholders through a diagram that shows the life
cycle of a class. What type of diagram are you using?
a. Context level data flow diagram.
b. Sequence diagram.
c. State diagram.
50.
51.
b. Business acumen.
d. Business approval.
19
52.
You are preparing for a lessons learned meeting that you will conduct. Which
of the following best describes your lessons learned session?
a. Your session is typically highly
structured.
53.
A set of processes, rules and templates that prescribe how business analysis
is performed is called what?
a. Document analysis.
b. Methodology.
c. Iteration.
d. Release planning.
54.
Which of the following best describes the type of requirement not needed
after a solution is implemented?
a. Non-functional requirements.
b. Functional requirements.
c. Transition requirements.
d. Conversion requirements.
20
55.
c. Problem tracking.
56.
57.
b. Regulatory compliance.
c. Stakeholder agreement.
d. Implementation plan.
21
58.
59.
b. DEA.
c. ERD.
d. EAR.
60.
What is the best definition for the Enterprise Analysis Knowledge Area:
a. Enterprise Analysis is managed as a
stand-alone project except for large
complex organizations where it is
treated as an investigative endeavor.
22
c. Enterprise Analysis spans the analysis
work done after the executive team
of the organization develops strategic
plans and goals and ends after
projects have been initiated.
61.
62.
23
63.
b. Data definition.
c. Data model.
d. Metadata.
64.
65.
The effort to describe how the stakeholder needs are evaluated, structured
and specified for use in the design and implementation of a solution is the
focus of which knowledge area:
a. Solution Assessment and Validation
b. Requirements Elicitation.
24
c. Requirements Analysis.
66.
b. Avoid.
c. Transcend.
d. Accept.
67.
b. Operational Support.
c. Tester.
d. Supplier.
68.
b. Verbally.
c. Face-to-face.
25
69.
d. Business Case.
70.
You want to ensure that the solution will provide business value. Which
technique will be LEAST useful?
a. Metrics and key performance
indicators.
b. Prototyping.
c. Variance analysis.
d. Risk analysis.
71.
26
72.
b. Decision maker.
c. Facilitator.
d. Arbitrator.
73.
74.
b. Risk analysis.
c. SWOT analysis.
27
d. PERT analysis.
75.
What best describes how the acronym RACI is used by the BA?
a. 'Risks Are Continuously Identifiable'
helps the BA during Requirements
Elicitation.
76.
77.
28
the steps an actor takes to
accomplish the goal of a use case.
78.
b. Evolutionary prototype.
c. A mockup.
d. Horizontal prototype.
79.
What is the best definition for the Business Analysis Planning and Monitoring
Knowledge Area?:
a. The BA must decide how to gather
requirements from the CIO and merge
this information with other
Knowledge Areas.
29
d. Business Analysis Planning and
Monitoring applies to the Business
Framework of an organization and the
activities associated with developing
a consensus for the optimal
investment opportunities.
80.
81.
Before estimating how long a requirements activity will take, what else must
be done?
a. Define deliverables.
82.
30
c. By a third-party vendor.
83.
b. A documented representation of a
condition or capability.
84.
b. Specify requirements.
85.
You are trying to gather quantitative data in your survey. What should you
do?
a. Ask closed-ended questions.
31
c. Ask both open-ended and closed-
ended questions.
86.
87.
b. Process model.
c. State diagrams.
d. Features.
88.
b. Testers.
32
d. Sponsors.
89.
Which of the following statements best describes the Solution Assessment &
Validation knowledge area?
a. The business analyst plays a key role
in the eliciting of requirements and
stakeholder concerns.
90.
91.
33
Benchmark studies are most appropriate for which BA Task:
a. Selecting the optimal approach to
business analysis.
92.
You have just completed your organizational assessment for the solution.
What is the potential next best step to perform?
a. Determine operational support.
93.
b. Requirements analysis.
c. Requirements performance
management.
94.
b. Hardware specifications.
c. System utilization.
34
d. Budget restrictions.
95.
b. Cohesive.
c. Complete.
d. Cover.
96.
97.
35
One of the following elements is NOT a part of the standard nomenclature for
a DFD (Data Flow Diagram):
a. Process.
b. Data store.
c. External entity.
d. Join.
98.
b. Sponsor.
c. Resource manager.
d. Domain SME.
99.
100.
Who is responsible for making sure that the process is followed during a
structured walkthrough?
36
a. Facilitator.
b. Moderator.
c. Author.
d. Sponsor.
101.
All of the following factors are considerations when selecting techniques for
Requirements Elicitation EXCEPT:
a. Availability and physical distance
separating the stakeholders.
102.
103.
37
a. Decision making.
b. Creative thinking.
c. Problem solving.
d. Systems thinking.
104.
105.
106.
38
A requirements package is defined as:
a. Collection of related objects in UML
diagram (use cases or classes),
grouped together for communication
to stakeholders.
107.
108.
39
c. Understand if a methodology or
business model can work.
109.
b. Context diagram.
110.
a. Glossary.
c. Model.
111.
The Work Breakdown Structure (WBS) is a useful tool for the BA in what task
or activity within the IIBA Knowledge Areas:
40
a. Plan business analysis activities.
112.
113.
41
114.
b. Be testable.
c. Have an author.
115.
116.
b. Relationship management
d. Stakeholder management.
117.
42
a. Draw a Context diagram.
b. Prepare a Storyboard.
118.
119.
Acceptance and evaluation criteria more than any other type of requirement
must be expressed in a testable form. For that reason, this technique would
be beneficial to which approach?
a. Waterfall.
b. Iterative.
c. Agile.
d. RUP.
120.
43
What type of analysis is used to ensure the underlying reason for a defect has
been identified?
a. Problem tracking.
b. Defect tracking.
d. BA performance metrics.
121.
b. Requirements analysis.
c. Requirements elicitation.
122.
What is the key purpose of the Maintain Requirements for Re-Use task?
a. To build a database of requirements
that will ensure requirements are not
missed in development.
44
123.
124.
Which of the following groups of factors will best help analyze solution
replacement or elimination:
a. Opportunity cost, sunk cost,
necessity.
125.
b. Recommendation on feasibility of
solution.
45
126.
126.
127.
b. Questionnaire.
d. Use Cases
128.
46
a. SMEs and other business recipients of
a solution.
b. Business Analyst.
c. Project Sponsor.
d. Project Team.
129.
b. Stakeholder analysis.
c. Functional requirements.
130.
You are running a requirements workshop. What task or activity are you
performing?
a. Documenting elicitation results.
b. Elicitation planning.
131.
47
b. Comparing against quality standards.
d. Repairing defects.
132.
133.
b. Configuration/change management.
d. Requirements verification.
48
134.
b. Elicited.
c. Documented.
d. Communicated.
135.
136.
c. Iteratively.
49
d. According to the BA communication
plan.
137.
b. Storyboarding.
c. Document Analysis.
d. Brainstorming.
138.
139.
Mary has collected several notes, diagrams and other documents through the
course of her project. This is known as what?
a. Documents.
c. Work product.
50
140.
Which of the following will help you determine the properties, behaviors and
characteristics of a system and the people that interact with it?
a. Learning.
b. Problem solving.
c. Systems thinking.
d. POLDAT.
141.
b. A determination.
c. A result.
d. A deliverable.
142.
143.
51
What is the best candidate for requirements re-use?
a. Current state.
b. Future state.
d. Enterprise Architecture.
144.
The BA would most likely invite which of the following project stakeholders
to a formal review of business processes and Use Case descriptions:
a. IT Architect, Sponsor, Business Area
Manager, Business Area Worker.
145.
b. Dependability, operability,
performance efficiency, security.
52
scalability.
146.
147.
148.
149.
53
Process Models are typically used to:
a. Document the scope of the problem
domain.
150.
54
ANSWERS
1. a BABOK 5.1.4.
2. c BABOK 3.4.1.
3. a This is the only answer that addresses what the BA does during EA, so it is the
best answer. BABOK 5.1.2.
4. d BABOK 7.4.1.
7. d Problem Tracking in the BABOK does have some ambiguity, since one of the
elements is Problem Management. Problem tracking is the technique in the BABOK,
though, is more specific, and is described similarly to what the question is asking:
'Allows the business analyst to manage any issues identified with requirements by
stakeholders and ensure that those issues are resolved.' BABOK 4.1.5., 9.20.2.
9. d BABOK 3.1.7.
11. a Executives typically like a summary, backed up by details. BABOK 5.5.4 and
5.5.6.
12. a No such thing, although a utility theory of risk explains the different risk
tolerances. BABOK 9.24.3.
15. b Something that deals with architecture suggests a technical constraint. BABOK
6.4.4.
17. d This supports 'demonstrating to the stakeholders that they deserve their
confidence.' BABOK 8.2.3.
19. c Description: 'Often want summaries and high-level requirements.' BABOK 4.4.6.
20. c Heterogeneous Focus Groups include individuals with diverse backgrounds and
perspectives. BABOK 9.11.3.
55
21. c Traceability is bi-directional. Trace back to the business/project objectives, and
forward into the development/testing. BABOK 4.2.2.
22. d Constraints limit choices, and these are all technical constraints. BABOK 6.4.4.3
and 7.1.2.
25. b The BABOK lists the business analyst as the only stakeholder for the task of
documenting elicitation results. BABOK 3.3.6
31. d OPAs are referred to throughout the BABOK as inputs to several tasks in several
knowledge areas. BABOK 2.4.3.
32. d These are all the techniques. Facilitating cross-functional sessions refers to the
technique of using requirements workshops. BABOK 3.1.5, 3.2.5., 3.3.5, and 3.4.5.
33. b These are used in define business case, which is what you'll be doing here.
BABOK 5.5.5.
40. b This is done to enable stakeholders to understand how the capabilities will
address the business need. BABOK 5.4.2
41. b Implementation SMEs are in the best position to diagnose solution component
problems. BABOK 7.5.4 and 7.5.6.
43. a For example, they are used for running parallel systems and are no longer
relevant once the solution is fully implemented. BABOK 7.4.2.
56
44. a From the BABOK 2.6.2.
48. b The purpose of the task addresses the needs described. BABOK 2.4.2.
50. a Not specifically stated, but implied. There is no set sequence for preparing the
requirements package, and this aligns with the concept of iteration implied in the
knowledge area graphic in the introduction. BABOK 4.4.4.
51. a Components could also include processes, people who operate/maintain the
solution, software applications, and organization structure. BABOK 7.2.4.1.
53. b Even though the BABOK stresses the term 'approach', it also lists 'methodology'
in the Glossary. BABOK Glossary page 228.
54. c This refers to the transition from current to future state and represents temporary
requirements. BABOK 1.3.3.1.
55. a This step would be performed after identifying defective solution outputs. BABOK
7.5.4.1.
57. d An implementation plan provides details on how the solution will be implemented.
If you are prioritizing requirements, you haven't agreed to a solution yet. If you have no
solution, you can't implement it. BABOK 6.1.4.
61. c May need to custom-design the interview based on desired outcome. BABOK
9.14.3.
62. a The key elements are tracing requirements, capturing requirements attributes,
and metrics. BABOK 3.2.4.
57
a solution that will meet the needs of the sponsoring organization and stakeholders.'
BABOK 1.4.
68. d Decisions on signoff are part of stakeholder authority levels in the BA plan. It is
not the role of the business analyst or project manager to decide how signoff will occur.
BABOK 2.2.4.4.
69. d The information needed for a go/no go decision is what the business case
represents. BABOK 5.5.7.
70. c This is used to look at actual vs. planned and is not useful for ensuring business
value. BABOK 6.6.5.
71. a They test only expected inputs and outputs. Even though testing is not a BA task,
BAs are expected to know about it. BABOK Glossary, page 223.
74. c The key here is to look for synonyms. Strengths = favorable. Weakness =
unfavorable. BABOK 7.3.5.
77. c Use Case models contain the graphical diagram and use case narratives
(BABOK: descriptions) contain text. BABOK 9.26.3.
82. b Constraints could also force certain requirements to be prioritized above others.
BABOK 7.2.4.
87. c State diagrams are useful for modeling functional requirements for complex
entities/objects, and not useful for scope modeling. BABOK 9.27.3 and 9.29.1.
58
88. c BABOK 2.3.6.
91. b Benchmarking is listed as one of the six techniques for defining the business
need. BABOK 5.1.5.
94. d Time and money are typical business constraints. BABOK 6.4.4
96. b BABOK Figure 2-1 (2.1, 2.2, 2.3, 2.4, 2.5, 2.6)
97. d Join is a part of an Activity Diagram. For Activity Diagrams the BABOK mentions
Flow merges which is also called a join. The reference to flow of work splits is also
called a fork. BABOK 9.21.2, Figure 9-9.
100. b This is the term used in the BABOK 9.30.3 and Figure 9-15.
104. a A simple story is an integral part of the User Story technique. BABOK 9.33.1.
107. c The BABOK mentions that assumptions and constraints are documented along
with associated attributes. BABOK 6.4.2.
108. d The solution approach represents the most feasible solution to meet a business
need. BABOK 5.3.1.
109. b A context diagram is a top-level data flow diagram. Data Flow Diagrams are
used as part of a structured analysis approach. They are used to get an understanding
of the range of data within the domain. BABOK 9.6.4; 9.27.3.
59
110. c A definition of a model. BABOK 6.3.4
117. a A Context Diagram shows the data in and out of a system. BABOK Glossary;
9.27, Figure 9-12 and 5.4.5.
120. c Use for finding underlying causes to any problems, including solution defects.
BABOK 7.5.5 and 9.25.
123. d The description of the root cause analysis technique mentions this as the critical
element. BABOK 9.25.2.
124. d All are listed as factors for solution replacement. Obsolescence is an example
of the 'Necessity' factor. BABOK 7.6.4.3.
126. d. Conflict can be recorded as an issue on the issue log. BABOK 4.1.4.2.
127. c This is part of document analysis, not stakeholder analysis. BABOK 9.9.2
128. d BABOK 7.1.3: 'Assumptions may lead to certain solutions being favored, and
constraints may limit available solution options.'
131. b Part of the definition of verification. Think 'quality' when facing questions about
verifying requirements. BABOK 6.5.2
60
132. a BABOK 6.5.4.
133. b The Requirements Management Plan describes how changes are controlled,
and is used in the task 'Manage Requirements Traceability.' BABOK 2.5.4.5, 4.2.4.3
135. c The S and W of SWOT are concerned with Strengths and Weaknesses. In
Enterprise Analysis, it is a technique that can be used in preparing a Business Case or
in conducting an Initial Risk Assessment. BABOK 5.2.5, 5.3.5, 5.5.5 and 9.32.
141. a Solution and product are synonymous. BABOK Glossary page 229
143. a Requirements are candidates for re-use only for the current state. BABOK
4.3.3.
144. c All roles listed here would be interested in business process descriptions, which
can include detailed processes and use cases. While the BABOK mentions 'any
stakeholder' might be invited, sponsors and executives may not be the best choice for
detailed requirements analysis. The other answers include the sponsor, who would be
least interested in detailed requirements analysis. BABOK: 6.3.6.
148. c These are all valid strategies for responding to positive risks. BABOK 9.24.3.3.
149. c Process models do typically document the 'as is' and 'to be' business workflow.
BABOK 9.21.2.
61