Free DAMA CDMP Fundamentals Practice Questions: Data Warehousing and Business Intelligence
Practice 10 free DAMA CDMP Data Management Fundamentals questions on Data Warehousing and Business Intelligence, with answers, explanations, and the IT Mastery next step.
Try the IT Mastery web app for a richer interactive practice experience with mixed sets, timed mocks, topic drills, explanations, and progress tracking.
Topic snapshot
| Field | Detail |
|---|---|
| Practice target | DAMA CDMP Data Management Fundamentals |
| Topic area | Data Warehousing and Business Intelligence |
| Blueprint weight | 10% |
| Page purpose | Focused sample questions before returning to mixed practice |
How to use this topic drill
Use this page to isolate Data Warehousing and Business Intelligence for DAMA CDMP Data Management Fundamentals. Work through the 10 questions first, then review the explanations and return to mixed practice in IT Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 10% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
Sample questions
These are original IT Mastery practice questions aligned to this topic area. They are not official exam questions, copied live-exam content, or exam dumps. Use them for self-assessment, scope review, and deciding what to drill next.
Question 1
Topic: Data Warehousing and Business Intelligence
A company has two executive dashboards that both use the enterprise data warehouse but report different values for Net Revenue. Finance excludes returns and tax; Sales excludes returns but includes tax. Leadership wants a trusted certified dashboard for enterprise reporting. Which governance action best addresses the issue?
Options:
A. Increase the warehouse refresh frequency
B. Redesign the dashboard visual layout
C. Move both dashboards to a new BI tool
D. Approve a single metric definition and certification workflow
Best answer: D
Explanation: BI governance improves trust by controlling how shared analytical assets are defined, approved, certified, and used. Here the problem is not that the warehouse is unavailable or the dashboard is unattractive; it is that two business groups apply different rules to the same named metric. A single approved Net Revenue definition, assigned ownership, stewardship review, and a certification workflow ensure that enterprise reports use consistent meaning and calculation logic. Technical improvements may help delivery, but they do not resolve conflicting business semantics.
- Refresh frequency addresses data timeliness, not conflicting metric definitions.
- Visual redesign may improve usability, but it does not make the metric trusted.
- New BI tooling can reproduce the same inconsistency if governance over definitions and certification is missing.
Question 2
Topic: Data Warehousing and Business Intelligence
A sales organization reports different monthly revenue totals in finance, sales operations, and executive dashboards. Each team maintains its own spreadsheet extract from operational systems, applies local business rules, and refreshes on different schedules. Which warehouse improvement best addresses the inconsistent metrics?
Options:
A. Store all spreadsheet extracts in a shared file repository
B. Add indexes to the operational source databases
C. Increase extract refresh frequency for each team
D. Create conformed data marts with governed metric definitions
Best answer: D
Explanation: Inconsistent BI metrics often come from unmanaged extracts, local transformation rules, and separate refresh cycles. A warehouse improvement should standardize the analytical flow: source data is integrated, transformed using governed rules, and published through conformed dimensions, facts, and certified metric definitions. This does not just make data easier to access; it makes reports comparable because teams are using the same definitions for revenue, period, customer, product, and other analytical concepts. Faster extracts or shared storage may improve convenience, but they preserve the fragmented logic that caused the disagreement.
- Faster refresh can reduce latency, but it does not align business rules or metric definitions across teams.
- Shared files centralize copies of extracts, but they still leave spreadsheet logic unmanaged.
- Source indexes may improve operational query performance, but they do not create a governed analytical layer.
Question 3
Topic: Data Warehousing and Business Intelligence
A finance division needs monthly margin reporting that executives can trust across regions. Analysts currently email modified spreadsheet extracts, producing conflicting totals and exposing sensitive customer fields. The organization has an approved data warehouse and a data governance council, but business teams still need flexibility to explore margin drivers. Which professional decision best addresses the situation?
Options:
A. Allow each region to maintain its own spreadsheet pack
B. Create another executive dashboard from the emailed spreadsheets
C. Restrict all analysis to IT-produced static reports
D. Publish governed BI datasets with certified metrics and controlled self-service access
Best answer: D
Explanation: Governed BI delivery combines trusted data, approved metric definitions, lineage, access controls, and stewardship with tools that let users analyze within controlled boundaries. In this situation, the data warehouse and governance council provide a foundation for certified datasets, standard margin definitions, and role-based access that prevents unnecessary exposure of sensitive fields. Self-service analysis is still appropriate, but it should use governed semantic layers, certified data products, or approved BI datasets rather than uncontrolled spreadsheet extracts.
The key distinction is not centralized reporting versus user flexibility. The stronger practice is controlled enablement: users can explore margin drivers while the organization manages definitions, quality, security, and report proliferation.
- Regional spreadsheet packs preserve local flexibility but continue duplicate reports, inconsistent totals, and uncontrolled distribution.
- Dashboard from emailed files improves presentation but still relies on ungoverned extracts and conflicting source logic.
- Static IT reports only may improve control but unnecessarily removes governed self-service needed for analysis.
Question 4
Topic: Data Warehousing and Business Intelligence
A retail company is preparing an executive KPI pack from its data warehouse. The CFO and CMO report different counts for “active customer,” although the warehouse load completed successfully and both dashboards trace to the same curated customer table. Marketing includes trial accounts; Finance excludes customers with no purchases in 12 months. The BI governance council wants a reusable control before certifying either dashboard. What is the best professional decision?
Options:
A. Assign a new data owner
B. Approve a governed metric definition
C. Open a data quality remediation issue
D. Document additional lineage details
Best answer: B
Explanation: The primary BI governance gap is metric definition. Both dashboards use the same curated source and the load completed successfully, so the facts do not point first to a lineage or technical quality problem. The conflict is that two business areas apply different inclusion and exclusion rules to the same KPI. A governed metric definition should state the business meaning, calculation logic, population rules, exclusions, accountable approver, and intended use. Once the definition is agreed and published, dashboard certification can confirm that each report implements the approved KPI consistently. Ownership may be needed to approve the definition, but simply assigning a new owner does not resolve the conflicting metric logic.
- New ownership may help with accountability, but the visible gap is unresolved KPI meaning, not an absent responsible party.
- More lineage would show where the data came from, but the dashboards already trace to the same curated table.
- Quality remediation is not the first step because no load failure, defect trend, or incorrect source value is described.
Question 5
Topic: Data Warehousing and Business Intelligence
A finance team reports that the warehouse measure Net Sales is 6% lower than the order-management system and 4% lower than last month’s published report. The CFO needs a defensible explanation before month-end close. A recent warehouse change added returns processing and a revised currency conversion step, and the source system owner says operational order totals have not changed. Which action is the best professional decision?
Options:
A. Change the dashboard total to match the operational system
B. Reload the warehouse from the operational source
C. Reconcile the measure through documented lineage and transformation control points
D. Ask the source system owner to revise order totals
Best answer: C
Explanation: Warehouse measures can legitimately differ from operational totals because the warehouse may apply different business rules, timing cutoffs, currency conversions, returns logic, or aggregation rules. The professional response is to trace the measure from source through staging, transformations, and presentation, then reconcile control totals at each point. In this case, the recent returns and currency changes are likely variance points, while the source owner has not reported a source-total change. The outcome should be a documented cause of the variance, not an unsupported adjustment to make reports match.
- Dashboard adjustment hides the variance and weakens trust because it bypasses lineage, definitions, and reconciliation controls.
- Warehouse reload may repeat the same result if the difference comes from intended transformation logic rather than load failure.
- Source-system revision is not justified because the operational owner reports that source totals have not changed.
Question 6
Topic: Data Warehousing and Business Intelligence
A company has a shared data warehouse and several executive dashboards. Sales and Finance publish different versions of “monthly recurring revenue,” and managers no longer trust the dashboard totals. The CIO wants to improve trust in shared analytical data before expanding self-service BI. What governance action best fits this need?
Options:
A. Limit dashboard access to executives until the totals stabilize
B. Ask each department to reconcile its dashboard totals monthly
C. Replace the dashboard tool with a single enterprise visualization platform
D. Certify shared metrics and datasets with approved definitions, owners, lineage, and quality rules
Best answer: D
Explanation: BI governance improves trust in analytical data by controlling how shared metrics, datasets, reports, and dashboards are defined, approved, certified, and changed. In this case, the trust problem is not mainly a visualization issue; it is conflicting metric meaning and unclear accountability. A governed certification process should define “monthly recurring revenue,” assign business ownership and stewardship, document lineage from source to dashboard, set quality rules, and manage changes. That makes the certified dataset or metric reusable across departments and reduces competing interpretations. Tool standardization can help delivery, but it does not by itself resolve semantic conflicts.
- Tool replacement may standardize presentation, but it does not establish business definitions, ownership, or metric certification.
- Monthly reconciliation treats the symptom repeatedly instead of preventing conflicting published metrics.
- Access restriction reduces visibility but does not improve the trustworthiness of the analytical assets.
Question 7
Topic: Data Warehousing and Business Intelligence
A retail company is trying to restore confidence in the executive Gross Sales dashboard before the next monthly close. Finance says the warehouse total is 4% lower than the CRM report. The team has limited time for remediation but can update metadata and governance decisions now.
| Flow point | Current practice |
|---|---|
| CRM sales report | Near-real-time opportunity updates |
| Warehouse load | ERP invoice snapshot at 8 p.m. daily |
| Transformation | Returns netted before aggregation |
| Catalog lineage | Source and return rule not recorded |
Which action is the BEST professional decision?
Options:
A. Ask Finance to adjust totals manually at close
B. Certify and document the agreed source, cutoff, and return rule
C. Use the CRM report because it is more current
D. Reload the warehouse hourly without changing transformations
Best answer: B
Explanation: Analytical reporting trust depends on knowing which source was used, when the data was captured, and how transformations changed the business meaning of the metric. The discrepancy is not just a refresh problem: CRM opportunities and ERP invoices represent different source selections, the warehouse uses a daily cutoff, and returns are netted before aggregation. A defensible response is to involve the accountable business parties, agree the authoritative definition for Gross Sales, and record the source-to-target lineage, cutoff, and return treatment in governed metadata. That supports consistent reporting now and provides a basis for later technical remediation if needed.
- Current source bias fails because more frequent CRM updates do not make CRM the authoritative source for invoiced sales.
- Refresh frequency only fails because hourly loading would not resolve different sources or the returns transformation.
- Manual adjustment fails because it creates an uncontrolled workaround rather than trusted, traceable analytical data.
Question 8
Topic: Data Warehousing and Business Intelligence
A sales data warehouse shows a sudden break in a five-year revenue trend. Analysts confirm that business volume did not change. The break appeared after an ETL release changed a source mapping and a transformation rule for revenue recognition. Which remediation best protects trust in historical BI reporting?
Options:
A. Perform lineage-driven impact analysis and version the metric change.
B. Smooth the dashboard trend line to reduce visible discontinuity.
C. Revert the source application mapping immediately.
D. Create a new warehouse table for future loads only.
Best answer: A
Explanation: Historical trend breaks in a warehouse are usually a lineage and metric-governance problem when they result from changed mappings or transformations. The remediation should identify which reports, measures, and periods were affected, record the changed rules as versioned metadata, and decide whether to restate history or clearly mark the point where the metric definition changed. This preserves comparability and prevents users from interpreting a technical change as a business trend. Simply changing presentation, reverting a source, or isolating new data does not give users a governed explanation of the historical discontinuity.
- Presentation smoothing hides the symptom but leaves the business definition and lineage problem unresolved.
- Immediate source reversion may disrupt valid current processing and does not assess downstream report impact.
- Future-only storage separates new data physically but does not explain or govern the historical trend break.
Question 9
Topic: Data Warehousing and Business Intelligence
A finance data warehouse feeds a monthly revenue dashboard due for executive review tomorrow. Lineage analysis shows that invalid country values are being introduced in a CRM field, and the same field also feeds customer service exports and a regulatory report. The organization has named data owners and stewards, but country-value quality rules are not yet standardized. What is the best professional decision?
Options:
A. Delay all reporting until the CRM application is redesigned
B. Exclude records with invalid countries from executive reporting
C. Patch only the warehouse transformation for the dashboard
D. Apply a controlled warehouse fix and initiate governed source remediation
Best answer: D
Explanation: Warehouse remediation can protect a time-sensitive BI deliverable, but it should be controlled, documented, and traceable because it does not correct the originating defect. Since the invalid values are created in CRM and reused by multiple downstream consumers, the durable fix belongs at the source and should be managed through data owners and stewards. Enterprise data quality management should define the country-value standard, assign accountability, monitor recurrence, and coordinate remediation across impacted uses. A short-term warehouse rule may be justified for tomorrow’s dashboard, but only as part of a governed response that addresses lineage, ownership, and reuse risk.
- Warehouse-only patch leaves the CRM defect and other downstream uses exposed.
- Full reporting delay overreacts to the immediate dashboard need when a controlled temporary remediation is possible.
- Record exclusion may distort revenue reporting and hides the quality issue instead of managing it through governance.
Question 10
Topic: Data Warehousing and Business Intelligence
A sales organization has three regional dashboards that show different values for “net revenue” because each dashboard applies its own filters and calculation logic. Executives want consistent KPI results while still allowing analysts to build reports in their preferred BI tool. Which BI practice best supports that decision-making need?
Options:
A. Store the dashboards in a shared content folder
B. Refresh the data warehouse more frequently
C. Add more visual filters to each dashboard
D. Define net revenue in a governed semantic layer
Best answer: D
Explanation: BI supports business decision making by turning governed data into consistent, understandable metrics, reports, dashboards, and analyses. In this scenario, the main problem is not tool access or refresh timing; it is inconsistent KPI logic across dashboards. A semantic layer provides a shared business-facing view of data, including definitions, relationships, and measures such as net revenue. When governed properly, it lets different reports and analytical tools reuse the same metric logic, improving trust and comparability for executive decisions.
The key distinction is between making dashboards easier to view and making the underlying metric meaning consistent.
- More dashboard filters may improve exploration, but they can increase inconsistency if each dashboard still calculates net revenue differently.
- Shared content storage helps users find reports, but it does not govern metric definitions or calculation rules.
- More frequent refreshes improve timeliness, but they do not resolve conflicting KPI logic.
Continue in the web app
Use IT Mastery for interactive DAMA CDMP Data Management Fundamentals practice with mixed sets, timed mocks, topic drills, explanations, and progress tracking.
Try DAMA CDMP Data Management Fundamentals on Web
Related focused pages
- Free DAMA CDMP Data Management Fundamentals Full-Length Practice Exam
- Data Management Process
- Big Data
- Data Architecture
- Document and Content Management
- Data Ethics
- Data Governance
- Data Integration and Interoperability
- Master and Reference Data Management
- Data Modelling and Design
- Data Quality
- Data Security
- Data Storage and Operations
- Metadata Management