Study guide
Planning Data Sourcing Activities
IIBA Certification in Business Data Analytics CBDA
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About the CBDA Exam Format, Fees, Eligibility & Scheduling How to Use This Guide & Study Strategy
2 Domain 1: Frame the Business Situation
Business Problems and Opportunities Current State Analysis for Analytics Future State, Gaps, KPIs and Metrics
3 Domain 1: Scope, Assumptions & Analytics Approach
Scope, Assumptions, Constraints, Dependencies Planning the Analytics Approach Organizational Analytics Culture and Capability
4 Domain 1: Research Questions & Technique Selection
Formulating Analytics Research Questions Analytics Categories and Technique Selection
5 Domain 2: Plan Sourcing & Identify Sources
Planning Data Sourcing Activities Internal and External Data Sources Data Frequency, Flow, and Acquisition
6 Domain 2: Quality, Preparation & Relationships
Data Quality Dimensions Preparation, Cleaning, and Sampling Outliers, Relationships, Linkages, and Integrity
7 Domain 3: Analysis Foundations & Descriptive Work
Scope, Data, Decision Models and Architecture Descriptive Statistics and Exploratory Data Analysis Diagnostic Analysis: Correlation vs Causation
8 Domain 3: Predictive Models & Validation
Predictive Models Overview Regression, Logistic Regression, and Classification Trees Interpreting Model Output and Adjusting Approach Validating Results Against the Business Question
9 Domain 4: Interpret Results & Recommend
Interpreting Analytics Results Deriving Insights from Analysis Recommendations and Refined Problem Statements
10 Domain 4: Storytelling & Visualization
Data Storytelling and Business Narrative Visualization Principles Chart Selection and Common Visualization Traps
11 Domain 4: Package & Stakeholder Communication
Packaging the Analytics Deliverable Stakeholder Communication Needs
12 Domain 5: Influence Decisions & Ethics
Assessing Whether Results Meet the Business Need Evidence-Based Decision Support Assessing Solutions and Recommending Action Ethics, Bias, Privacy, and Responsible Reporting
13 Domain 5: Implementation & Change
Implementation Planning from Analytics Results Organizational Readiness and Change Management Influencing Stakeholders and Managing Resistance
14 Domain 6: Strategy, Evaluation & Governance
Organization-Level Analytics Strategy and Maturity Evaluating Analytics Solutions and Outcomes Data Governance, Security, and Privacy
15 Domain 6: MDM, Curation & Performance
Master Data, Metadata, and Data Curation Performance Improvement, Standards, and Reuse
Planning Data Sourcing Activities
Key Takeaways Explain This Topic AI
Competency 2.1 asks what data is needed to answer the research question before collecting everything available
Map each research question to required data elements, grain, time window, and population—then inventory what exists vs what is missing
Business analysts contribute expertise on business meaning, process context, and decision fit—not only on SQL or pipelines
If expected data is unreliable or unavailable, re-evaluate the sourcing approach (or refine the question)—do not abandon the research question as the first move
A living data inventory and gap list turns vague source hope into a manageable Domain 2 plan (about 15% of the CBDA exam)
Last updated: July 2026
Planning Data Sourcing Activities
Quick Answer: Domain 2 ( Source Data , about 15% of the CBDA exam) begins with planning what data you need to answer approved research questions—not with downloading every table you can reach. Competency 2.1 focuses on identifying required data elements, assessing availability, documenting gaps, and adjusting the sourcing plan when expected data is incomplete or unreliable.
Domain 1 left you with framed business situations, scope, assumptions, and research questions. Domain 2 turns those questions into a sourcing plan : which fields, at what grain, for which population and time window, from which candidate systems, under which access and quality constraints. Teams that skip this planning either drown in irrelevant extracts or discover too late that the question cannot be answered with current sources.
Competency 2.1: What data is needed?
Plan data sourcing means answering, for each research question:
What entities and attributes must exist (customers, orders, tickets, claims, sensors, employees)?
At what grain must each row represent reality (order line, daily store, monthly cohort, claim event)?
Over what time window must history cover the decision (last 90 days, last fiscal year, post-policy-change only)?
For which population (segment, region, product family, channel)?
With what freshness (as-of yesterday batch, weekly snapshot, near-real-time)?
Under what rights and privacy rules (PII, PHI, commercial third-party licenses)?
Only after those answers are clear do you shop systems, vendors, surveys, or manual collection. On exam stems, “pull all CRM data” without this map is almost always a weak next step.
Required vs nice-to-have
Separate must-have fields that make the question answerable from enrichment fields that improve insight but are not blocking:
Priority Example for voluntary churn research If missing
Must-have Customer ID, subscription status, churn/cancel flag and date, tenure, product plan Question not answerable as written
- Important Support ticket counts, NPS, payment failures Diagnostic depth limited; still possible with caveats
- Nice-to-have Third-party credit scores, social sentiment Enrichment deferred; do not block baseline analysis
CBDA planning rewards honest minimum viable data for the decision, then phased enrichment—not a “data lake first, question later” posture.
Map research questions → data elements, grain, time window
A practical technique is a question-to-data matrix . One row per research question (or sub-question); columns for elements, grain, window, population, candidate sources, and status.
Example: mid-market SaaS retention
Research question: Which mid-tenure online subscribers show elevated voluntary churn that is actionable with the current offer catalog?
Need Specification
Elements subscriber_id, plan_code, tenure_months, voluntary_churn_flag, churn_date, offer_id history, support_contacts_90d, payment_fail_count
- Grain One row per subscriber-month (or subscriber as-of analysis date with monthly activity rollups)
- Time window 12 months of history ending last complete month
- Population U.S. online B2C subscribers with tenure 4–18 months
- Exclusions Forced cancellations, fraud closures, B2B contracts
- Freshness Monthly decision cycle → month-end warehouse snapshot is acceptable
Notice the map does not yet name “use Snowflake table X.” It names business data needs . Source selection comes next, using inventory and fitness checks.
Grain mistakes that break analysis later
Too coarse: Monthly revenue by region cannot answer SKU-level assortment questions.
Too fine without keys: Clickstream events without stable customer keys cannot support subscriber-level churn drivers.
Mixed grain joins: Order headers joined carelessly to order lines inflate revenue and create false correlations.
Wrong event time: Using “load date” instead of “business event date” misplaces pre/post policy windows.
Document grain in the sourcing plan so engineers and SMEs validate the same unit of analysis the research question assumes.
Time window discipline
Time windows must match the decision and the process reality :
Seasonal businesses need comparable seasons, not an arbitrary last-30-days slice.
Policy changes create natural breakpoints; mixing pre/post regimes without flags confounds diagnostics.
Very long windows increase coverage but may include obsolete product definitions.
Very short windows may miss rare but costly events.
On CBDA scenarios, if a stakeholder wants “all history forever,” the BA often negotiates a fit-for-purpose window tied to decision relevance and definition stability.
BA expertise: required vs available
The business analyst’s contribution in Domain 2 is not limited to writing tickets for IT. CBDA expects BAs to:
Translate research language into business data language (“voluntary churn” → specific cancel reason codes and exclusions).
Challenge “we have that data” claims by asking where it lives, who owns it, how complete it is, and whether definitions match.
Surface process knowledge that systems miss (manual workarounds, regional spreadsheets, shadow CRM fields).
Protect decision fit: if available data answers a different question, say so and re-scope rather than force a narrative.
Coordinate owners and stewards for access, dictionary confirmation, and quality expectations.
Keep ethics and privacy in the plan so acquisition does not outrun consent and policy.
Required vs available assessment pattern
List required elements from the research question.
For each element, record candidate source , owner , known definition , and confidence (confirmed / assumed / unknown).
Mark status: available & fit , available but risky , partial , unavailable .
For risky/partial/unavailable items, define actions : profile sample, interview steward, seek alternative source, collect primary data, or refine the question.
Update assumptions and dependencies from Domain 1 with evidence from this assessment.
This is where Domain 1 assumptions become Domain 2 work: “warehouse has two years of clean churn flags” is no longer a hope—it is a checklist item.
When expected data is unreliable: re-evaluate sourcing (exam theme)
A recurring IIBA-style theme: you planned on a source, then profiling or SME review shows the data is incomplete, inconsistently defined, late, or legally restricted. What is the next step?
Weak reaction Stronger CBDA reaction
Abandon the research question immediately Re-evaluate the sourcing approach first: alternate internal source, external purchase, primary collection, proxy metric, or adjusted grain/window
Quietly use bad data and hope Document quality risk, quantify impact, and refuse unsupported claims
Expand scope to “analyze everything else” Stay tied to the decision; change sources or refine question deliberately
Blame IT and stop Engage owners with a gap list and time-boxed remediation or fallback plan
Re-evaluate sourcing can include:
Switching from CRM cancel flags to billing termination events if CRM is sparsely maintained.
Using store-level sales when item-level POS is delayed—but only if the research question can be restated at store grain.
Commissioning a short survey when attitudinal drivers are essential and systems only hold transactions.
Purchasing a third-party firmographic feed after rights review when internal firmographics are empty.
Narrowing population to regions with reliable data and stating external validity limits.
Only after feasible sourcing paths are exhausted—or when remaining paths cannot meet decision timing—do you renegotiate the research question with stakeholders. Abandoning the question as the first response is usually wrong on exam items; so is pretending the original question is still fully answerable.
Mini-scenario
Plan: Use CRM “reason for leave” to diagnose voluntary churn drivers.
Finding: 55% of churned accounts have blank or “other” reasons; agents say the field is optional.
Poor next step: Cancel the churn study.
Better next steps: (1) Profile billing and product-usage signals as alternative diagnostic inputs; (2) sample call notes if allowed; (3) propose a time-boxed improvement to reason-code capture for future cycles; (4) restate near-term question toward behavioral drivers that systems do capture. That is re-evaluating sourcing and, if needed, refining—not abandoning—the analytical intent.
- Data inventory and gap list
- Data inventory (what we might use)
A data inventory for an analytics effort is a working catalog of candidate datasets relevant to the research questions. Minimum useful fields:
- Dataset / system name
- Business owner and technical contact
- Entities covered and primary keys
- Known grain and refresh cadence
- Access path (warehouse table, API, extract, manual file)
- Sensitivity classification (public, internal, confidential, restricted)
- Known quality issues or dictionary links
- Fit rating for each research question (high / medium / low / unknown)
You do not need a perfect enterprise catalog on day one. You need enough inventory that the team stops relying on hallway knowledge.
Gap list (what we still lack)
A gap list converts inventory into action:
Gap Impact on question Options Owner Due
No reliable voluntary vs involuntary churn flag Cannot isolate voluntary churn drivers Derive from cancel reason + collection status; SME rule set BA + billing steward Week 1
Offer history only for last 4 months Limited offer-effectiveness claims Restrict offer analysis to 4 months; diagnose churn without offer ROI BA + marketing ops Week 1
No consent flag for email engagement Cannot use campaign clicks for EU cohort Exclude EU from engagement features or use consented subset Privacy + marketing Week 2
Gaps should be visible to sponsors . They are not project failure—they are the sourcing plan’s risk register.
Planning activities checklist (Domain 2 start)
Restate approved research questions and success criteria.
Build the question-to-data matrix (elements, grain, window, population).
Draft inventory of candidate internal/external sources.
Confirm definitions with SMEs for must-have fields.
Assess availability, access path, rights, and preliminary quality.
Produce gap list with options and owners.
Choose primary sourcing approach and fallbacks.
Update assumptions, constraints, and dependencies.
Get light approval on the sourcing plan before large extracts or purchases.
Only then schedule acquisition, profiling, and preparation (covered deeper in later Domain 2 chapters).
Linking plan-sourcing to later work
Source types and acquisition: Inventory items become concrete lakes, warehouses, APIs, or vendor feeds (next sections).
Quality and preparation: Gap severity drives cleaning, sampling, and integrity work.
Analysis: Grain and window choices constrain which techniques are honest.
Interpretation and influence: Limitations documented in the gap list become transparency in the story—not surprises in the decision meeting.
CBDA exam habits for planning data sourcing
Prefer options that derive data needs from the research question .
Prefer inventory + gap analysis over blind full-enterprise extracts.
Prefer re-evaluate sourcing / refine approach when data is unreliable—not instant abandonment of the question.
Prefer BA actions that validate definitions and owners early.
Reject both extremes: tool-first collection with no plan, and analysis paralysis that never inventories real sources.