Study guide

Internal and External Data Sources

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

Internal and External Data Sources

Key Takeaways Explain This Topic AI

CBDA source identification spans operational systems, warehouses, lakes, marts, vaults, and third-party or public data—chosen for fit to the research question

Structured data fits tables and strict schemas; semi-structured and unstructured sources need extra preparation but can hold critical signal

Internal sources often win on process context and rights clarity; external sources can fill gaps at the cost of trust, latency, licensing, and integration work

Reference data and master data awareness prevent join failures and inconsistent “golden” identifiers across systems

Exam scenarios reward matching source type to use case—not defaulting to the newest platform or to “buy external data” without governance

Last updated: July 2026

Internal and External Data Sources

Quick Answer: After you know what data the research question needs , Domain 2 asks you to identify candidate sources —internal systems and stores plus external or public datasets—and evaluate them for fitness, trust, cost, latency, and rights. Platform names matter less than whether a source can supply the right elements at the right grain for the decision.

Source identification is still planning work. You are building options for acquisition, not yet claiming that every source is clean enough for final analysis (quality depth follows in later Domain 2 sections). On the CBDA exam, strong answers match source type to analytical use case and call out governance implications early.

  • A practical map of source types
  • Operational systems (systems of record / engagement)

These are day-to-day applications: CRM, ERP, billing, claims, EHR modules, LMS, POS, ticketing, HRIS. They generate transactions and states the business runs on.

CBDA use cases: current process truth, event-level history, status flags used in operations.

Watch-outs: schemas optimize transactions, not analytics; definitions may be local; extracts can stress production; historical depth may be limited by archival rules.

Data warehouses

Warehouses store integrated, often structured data optimized for analytical query—commonly dimensional models or governed enterprise tables.

CBDA use cases: cross-functional metrics, historical snapshots, consistent reporting grain for descriptive and diagnostic work.

Watch-outs: latency (batch loads), incomplete subject areas, “official” metrics that still disagree with operational reality if ETL transforms are opaque.

Data marts

Marts are subject- or department-oriented analytical stores (finance mart, marketing mart) derived from warehouse or operational feeds.

CBDA use cases: faster access for a domain team; pre-joined conformed dimensions for common questions.

  • Watch-outs: local marts can diverge; marketing “customer” may not match finance “customer.”
  • Data lakes (and lakehouses)

Lakes hold large volumes of raw or lightly processed data in varied formats; lakehouses add warehouse-like table management on lake storage.

CBDA use cases: exploratory access to multi-format history, machine learning feature raw zones, cheap retention of detailed events.

Watch-outs: “dumping ground” risk without catalog and quality; schema-on-read shifts burden to the analyst; access control and PII sprawl.

Data vaults (awareness level)

Data vault modeling emphasizes hubs, links, and satellites for agile, auditable integration of historical sources.

CBDA use cases: enterprise integration with strong historization and lineage-friendly design.

Watch-outs: business users rarely query vault structures directly; marts or warehouse presentation layers usually sit on top. Exam awareness: vault ≠ automatic business definitions.

Third-party and public data

External commercial feeds (credit, firmographics, weather, mobility, market prices) and public/open data (census, macro indicators, government releases, academic sets).

CBDA use cases: enrichment, benchmarking, market context, features not generated inside the firm.

Watch-outs: licensing, redistribution limits, opaque collection methods, refresh surprises, join-key weakness, bias relative to your population.

Structured vs semi-structured vs unstructured (awareness)

Form Typical examples Analytics implication

Structured Relational tables, CSV with fixed columns, warehouse facts/dims Fastest path to quantitative analysis when definitions hold

Semi-structured JSON/XML events, log objects, NoSQL documents, API payloads Flexible fields; need parsing, evolving schemas, null-heavy attributes

Unstructured Emails, PDFs, call audio, images, free-text notes, chat High insight potential; requires NLP, labeling, or human coding; privacy heavier

CBDA does not require you to be a deep learning engineer. It does require you to recognize that form changes sourcing and preparation cost . Combining structured transactions with unstructured feedback is common; plan time and skills for both. On scenarios, choosing only structured data when the research question is about why customers complain in their own words is a fitness miss.

Internal vs external: trust, cost, latency, rights

Dimension Internal sources External sources

Trust & context Higher process context; SMEs nearby; known quirks Variable; vendor methodology may be black box

  • Cost Mostly sunk platform + internal labor Subscription, per-record, or project fees + legal review
  • Latency Depends on pipelines; can be near-real-time for ops APIs Vendor SLAs; public data often lagged

Rights & privacy Internal policy still applies; employee access rules Contracts, redistribution, geographic restrictions, consent chains

  • Joinability Shared keys may still be messy but stewards exist Fuzzy matching, coverage gaps, ID translation
  • Stability Schema changes with releases Vendor versioning; discontinued products
  • When internal is preferred

The decision hinges on how your process actually runs .

You need lineage and remediation with people you can call.

External purchase cannot clear legal review inside the decision window.

Metrics must reconcile to financial or operational systems of record.

When external is justified

Required attributes do not exist internally (market share, competitor price index, weather at store location).

Internal coverage is structurally incomplete (new market entry with no history).

Benchmarking against industry baselines is part of the research question.

Primary collection would be slower or costlier than a governed purchase.

Exam pattern: Internal incomplete + external complementary → evaluate both, integrate deliberately, govern rights —not “external only because it is trendy,” and not “internal only because external feels scary” when the gap is real.

Reference data and master data (awareness)

Reference data is relatively stable codes and lookups: country codes, product category lists, reason codes, status enumerations, currency codes. Bad reference data breaks filters and group-bys (“CA” meaning California vs Canada; retired cancel codes still appearing).

Master data is the authoritative business entities the enterprise tries to keep consistent: customer, product, supplier, location, chart of accounts. Master data management (MDM) programs create golden records and survivorship rules.

Why CBDA candidates care during sourcing:

Joining CRM to billing fails when customer master duplicates or mismatched keys exist.

Product hierarchy in merchandising disagrees with finance SKU rolls—marts disagree.

Reference lists differ by region; global analysis silently drops rows.

“One customer” research questions assume master resolution you may not have—log it as a gap.

You are not expected to implement MDM in Domain 2, but you must notice when analysis depends on master/reference consistency and plan keys, survivorship assumptions, and limitations accordingly.

Source-type table with CBDA use cases

Source type Best-fit CBDA use cases Typical risks

Operational CRM / billing / claims Event truth for status changes, cancellations, payments, case outcomes Write-optimized schemas; optional fields sparsely filled

ERP / supply chain systems Inventory positions, PO cycle times, cost components Complex modules; limited analyst access; batch windows

Enterprise data warehouse Cross-subject descriptive baselines, governed historical metrics Load lag; transform opacity; incomplete domains

Departmental data mart Fast answers inside one function’s common grain Definition drift vs enterprise; local filters hidden in views

Data lake / object storage Multi-format exploration, detailed clickstream, ML raw zones Catalog gaps; quality unknown; PII sprawl

Data vault (integration layer) Auditable multi-source history for enterprise integration Not end-user friendly; needs presentation layer

BI semantic layer / certified datasets Consistent KPI pull for decision packs May hide grain; limited micro-event detail

APIs (internal microservices) On-demand entities, near-current state Rate limits; pagination traps; unstable contracts

Third-party commercial data Enrichment, risk scores, market prices, firmographics License, ethics, opaque bias, join quality

Public / open government data Macro context, demographics, regulatory datasets Lag, geographic mismatch, aggregation too coarse

Primary collection (survey, interview coding, observation) Attitudes, reasons systems never capture Sampling bias, cost, consent, small N

Spreadsheets & shadow systems Local process truth not yet in platforms Version chaos; single points of failure; weak controls

Scenario patterns

Pattern A — Warehouse first bias: Sponsor says “only use the warehouse.” Inventory shows claims denials detail never landed. Best move: document gap; seek operational claims extract or lake raw zone; do not pretend warehouse completeness.

Pattern B — External shortcut: Team wants to buy a lookalike audience file instead of defining internal conversion events. Best move: confirm whether the research question is about your funnel (internal first) or market universe (external may fit); check rights before purchase.

Pattern C — Unstructured gold: NPS scores are flat but ticket text explodes with a new defect theme. Best move: plan semi/unstructured sourcing (tickets, notes) with privacy review—not only structured score tables.

Pattern D — Master data pain: Two “customer counts” differ by 12%. Best move: pause cross-system claims; involve stewards; define survivorship for this analysis; state limitation if unresolved.

Pattern E — Mart convenience trap: Marketing mart makes charts easy but excludes returns. Best move: validate mart business rules against the research question; supplement from warehouse/ops if returns matter.

Selecting sources: a short decision path

Start from the question-to-data matrix (prior section).

List internal candidates that hold must-have elements.

Rate fit (coverage, grain, window, definition match).

If gaps remain, evaluate external or primary options with rights and cost.

Prefer sources with owners, dictionaries, and access paths inside the decision window.

Record multi-source join keys and master/reference dependencies.

  • Carry forward quality unknowns—do not equate “source identified” with “source trusted.”
  • CBDA exam habits for source types

Prefer fitness to the research question over newest architecture buzzwords.

Prefer internal + external combination when each closes a real gap.

Prefer answers that mention rights, licensing, and privacy for third-party data.

Prefer recognition of structured vs unstructured preparation cost .

Prefer flags for master/reference data issues when joins or golden IDs are assumed.

Reject “analyze all data everywhere” and “never use external data” as absolute rules.