Free DAMA CDMP Fundamentals Practice Questions: Data Storage and Operations

Topic snapshot

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 Storage and Operations

A claims processing database holds 10 years of closed claims in the same operational tables used for current work. Users report slower searches, and compliance requires closed claims older than 18 months to remain retrievable for audit but not actively updated. Which database operations activity best fits this need?

Options:

• A. Replicate the database to a reporting server

• B. Tune indexes on all claims tables

• C. Archive closed claims under retention rules

• D. Increase database backup frequency

Best answer: C

Explanation: Database operations support the data lifecycle by keeping operational data available, performant, protected, and retained appropriately. In this case, the central issue is that inactive closed claims are still mixed with active operational data. Archiving with retention rules separates less-active records from daily processing while preserving them for audit access and preventing unauthorized updates. This addresses both lifecycle status and operational performance pressure. Backup frequency helps recover from failure, but it does not distinguish active from inactive records. Index tuning may improve some searches, but it does not satisfy the retention and update-control requirement.

• More backups improves recoverability, but it does not reduce active-table volume or enforce audit retention behavior.
• Index tuning may help query performance, but it leaves inactive closed claims in the operational lifecycle.
• Reporting replication supports read access elsewhere, but it does not manage retention, archival status, or update restrictions.

Question 2

Topic: Data Storage and Operations

A hospital scheduling system stores active appointment and patient check-in data. If the primary storage platform fails, current operational data must remain durable and usable by the application within minutes, with minimal data loss. Which data storage and operations action best satisfies this requirement?

Options:

• A. Take periodic backups to offline media

• B. Archive closed records to lower-cost storage

• C. Define retention periods for appointment records

• D. Replicate data to a secondary operational platform

Best answer: D

Explanation: Replication is the storage operations action most directly tied to keeping operational data durable and usable during a platform failure. It maintains a current or near-current copy on another system so the application can continue or be restored quickly with limited data loss. Backups support durability and later restoration, but they are point-in-time copies and may not be immediately usable for live operations. Archival moves data that is no longer active to long-term storage, often optimized for cost or compliance rather than immediate application use. Retention defines how long data must be kept or disposed of; it does not itself create operational continuity.

• Backups protect against loss but usually require a recovery step before the data is usable by the application.
• Archival is for long-term preservation of inactive data, not current transaction continuity.
• Retention periods state how long records are kept; they do not provide a failover copy.

Question 3

Topic: Data Storage and Operations

A production claims database is slowing during daily service operations. It contains nine years of closed claims, but business users normally need only the most recent 18 months online. Policy requires closed claims to be retained for seven years and retrievable for audits. A major redesign is not approved this quarter. Which database operations activity is the best professional decision?

Options:

• A. Permanently delete all claims older than 18 months

• B. Implement managed data archiving with retention controls

• C. Increase the backup frequency for the database

• D. Add more dashboard indexes for claims reporting

Best answer: B

Explanation: Database operations support the data lifecycle by keeping operational data available, performant, recoverable, and retained according to policy. In this situation, the main problem is not only query speed; it is that inactive closed claims are occupying the active production store while still being subject to a seven-year retention requirement. A managed archiving process moves eligible records out of the high-use operational database, applies retention and retrieval rules, and supports audit needs without requiring a full redesign. Backup protects recoverability, and indexing may improve selected queries, but neither addresses lifecycle placement and retention of older records. Deleting records would violate the stated policy.

• More backups improves recoverability, but it does not reduce active database volume or manage retained closed claims.
• Permanent deletion conflicts with the seven-year retention and audit retrieval requirements.
• More indexes may help some reporting access paths, but it does not address inactive data lifecycle management.

Question 4

Topic: Data Storage and Operations

A retailer is launching a new customer analytics application. Several work items have been proposed, but the program manager wants to assign the one that belongs primarily to Data Storage and Operations. Which work item best fits that area?

Options:

• A. Define rules for customer email completeness

• B. Create the logical customer entity model

• C. Approve the enterprise definition of customer

• D. Select storage platforms and define backup/recovery operations

Best answer: D

Explanation: Data Storage and Operations focuses on the platforms and operational processes used to store, retrieve, protect, back up, recover, and maintain data. In this scenario, choosing storage platforms and defining backup/recovery operations is a technology and operational responsibility. The other activities are important data management work, but they belong to different areas: governance sets decision rights and definitions, modelling describes data structures and relationships, and data quality defines and monitors fitness-for-use rules. The key distinction is that storage decisions concern the managed technical environment, not the business meaning, model design, or quality expectations for the data.

• Business definition belongs to data governance because it establishes shared meaning and accountability for customer data.
• Logical entity design belongs to data modelling and design because it represents entities, attributes, and relationships.
• Completeness rules belong to data quality because they define expectations used to assess fitness for use.

Question 5

Topic: Data Storage and Operations

A customer service application stores detailed case records in an operational database. The approved retention schedule says identifiable case details must be removed after 3 years, but BI teams currently query the same tables for 5-year service trend analysis. What is the best action?

Options:

• A. Purge all records older than 3 years immediately

• B. Create a governed archive or analytical dataset before purging

• C. Let BI teams keep unmanaged extracts

• D. Extend operational database retention to 5 years

Best answer: B

Explanation: Database operations and lifecycle support should keep operational data stores aligned with approved retention rules while recognizing valid downstream use. When analytics needs outlive operational retention, the preferred action is not to keep the operational database indefinitely. A governed archive, data warehouse feed, or de-identified analytical dataset can preserve needed trend history under approved controls, retention rules, metadata, and access management. This separates operational processing needs from analytical retention needs and reduces compliance, privacy, and operational performance risk.

Simply extending operational retention ignores the approved schedule. Unmanaged extracts create uncontrolled copies. Immediate deletion may satisfy one rule but can break legitimate analytical requirements if no approved replacement is in place.

• Extending operational retention fails because it overrides the approved retention schedule instead of reconciling operational and analytical needs.
• Unmanaged BI extracts fail because they create uncontrolled copies with unclear ownership, retention, and access controls.
• Immediate purging fails because it protects retention compliance but does not address the approved need for historical analysis.

Question 6

Topic: Data Storage and Operations

A regional insurer is redesigning database operations for a claims system. Claims adjusters need fast retrieval of active claims, regulators require claim records to be retained for 7 years after closure, storage costs are rising, and audit staff must be able to prove that closed claims were not altered after archival. Which professional decision best supports these lifecycle and operational needs?

Options:

• A. Delete closed claims once claim payments are completed

• B. Keep all claims in the active operational tables indefinitely

• C. Define lifecycle rules for active, archived, retained, and deleted claims

• D. Move closed claims to analyst spreadsheets for long-term storage

Best answer: C

Explanation: Database operations support the data lifecycle by ensuring that data can be created, updated, retrieved, archived, retained, and deleted according to business and compliance needs. In this case, active claims should remain optimized for adjuster retrieval, while closed claims should move into controlled archival storage with retention rules, access controls, and evidence of integrity. After the required retention period, deletion or disposal should follow approved policy. This approach also improves operational performance because active tables are not overloaded with inactive history. Simply storing everything forever, deleting too early, or moving records outside controlled database operations fails either performance, retention, or reliability requirements.

• Indefinite active storage may preserve data, but it increases operational burden and does not address archival integrity or lifecycle disposal.
• Early deletion conflicts with the 7-year regulatory retention requirement.
• Spreadsheet storage weakens control, auditability, and reliability for official retained claim records.

Question 7

Topic: Data Storage and Operations

A retailer’s order-entry database is slowing as transaction history grows. Customer service must retrieve recent orders quickly, auditors require retained orders for 7 years, and policy requires defensible deletion after the retention period. Which database operations approach best fits these needs?

Options:

• A. Keep all order data online and expand storage as needed

• B. Move retained orders only into reporting dashboards

• C. Delete older orders manually when performance degrades

• D. Establish lifecycle operations for archiving, retention, tuning, and recovery

Best answer: D

Explanation: Database operations support the full data lifecycle, not just day-to-day storage. In this scenario, the operational design should keep current orders performant, archive older records in a controlled way, enforce retention periods, support auditable retrieval, delete data defensibly when retention expires, and maintain backup and recovery capabilities. This connects lifecycle management with performance and reliability requirements. Simply adding storage may delay the performance problem, while ad hoc deletion creates audit and compliance risk. Reporting systems can support analysis, but they are not a substitute for governed retention, archiving, and disposal controls.

• Online-only storage may preserve access, but it does not address retention-based disposal or long-term performance management.
• Manual deletion creates inconsistent records management and weak auditability when policy requires defensible deletion.
• Reporting dashboards help analytical access, but they do not manage authoritative retention, archiving, deletion, or recovery duties.

Question 8

Topic: Data Storage and Operations

A customer service application stores order documents in a shared file repository. The repository has grown rapidly because teams copy the same documents into project folders instead of linking to a controlled source. Storage costs are rising, and different teams are sometimes using different versions of the same document. Which risk is most directly created by this storage operations issue?

Options:

• A. Incomplete physical data modelling

• B. Uncontrolled duplication and inconsistent records

• C. Insufficient encryption key rotation

• D. Weak database transaction isolation

Best answer: B

Explanation: Data storage operations include managing data assets so they remain available, controlled, and usable throughout their lifecycle. In this case, the issue is not the existence of many documents by itself, but unmanaged copying across folders. That creates duplicate content, higher storage consumption, and conflicting versions used by different teams. The operational risk is loss of control over authoritative records, which can affect service quality, reporting, compliance, and retention decisions.

The key takeaway is that storage growth caused by unmanaged copies is a control and consistency problem, not simply a capacity problem.

• Transaction isolation applies to concurrent database changes, not unmanaged copies in a file repository.
• Key rotation is a security control concern, but the facts do not indicate encryption or access-control weakness.
• Physical modelling concerns database implementation structures, not operational control of duplicate documents.

Question 9

Topic: Data Storage and Operations

A bank is reviewing operational controls for a customer transaction database before renewing its data-sharing agreement. The business needs evidence that the database can be restored after failure, remains available for daily reporting, preserves transaction integrity after nightly loads, and applies approved retention and disposal rules. Which evidence package is the best professional choice?

Options:

• A. Backup/restore test results, uptime monitoring, reconciliation reports, and retention-disposal logs

• B. Data model diagrams, user training records, dashboard screenshots, and project status reports

• C. Access request approvals, encryption settings, role mappings, and security incident tickets

• D. Storage capacity trends, server patch logs, vendor invoices, and network diagrams

Best answer: A

Explanation: Operational evidence should show that controls are actually working, not just that designs or intentions exist. For this database, the review needs proof across four concerns: recoverability, availability, integrity, and lifecycle control. Successful backup jobs plus periodic restore tests support recoverability. Uptime and incident monitoring support availability for reporting. Load reconciliation, control totals, or exception reports support transaction integrity after processing. Retention, archive, and disposal logs show that lifecycle rules are being executed under approved policy. Evidence from architecture, security, or project management may be useful elsewhere, but it does not cover all four operational needs in the scenario.

• Design artifacts describe intended structure but do not prove restore capability, availability, load integrity, or disposal execution.
• Infrastructure records support operational context but miss business data integrity and controlled lifecycle evidence.
• Security evidence is important for access control and protection but does not demonstrate backup recovery, availability, or retention execution.

Question 10

Topic: Data Storage and Operations

A health insurer stores claims data in an operational database used by call-center staff and nightly eligibility feeds. The database is nearing capacity, older closed claims must be retained for 10 years, and recovery time for current claims must stay under 2 hours. Which action is the BEST professional decision?

Options:

• A. Increase disk capacity and keep all claims online

• B. Archive closed claims and update recovery procedures

• C. Delete closed claims after they leave active use

• D. Move nightly feeds to manual file exchange

Best answer: B

Explanation: Data storage and operations responsibilities include ensuring capacity, recoverability, retention, and continuity for operational data services. In this scenario, the organization must relieve capacity pressure without losing legally or operationally required records, and it must maintain a short recovery time for current claims. Archiving closed claims to an appropriate retained storage tier keeps them available for the 10-year retention period while reducing the load on the active database. Updating backup and recovery procedures ensures the active claims environment can still meet the 2-hour recovery requirement. Simply adding storage may postpone the problem but does not address lifecycle management or recovery planning.

• More disk only treats capacity as the only issue and does not manage the retention lifecycle or recovery procedures.
• Deleting closed claims violates the stated 10-year retention need.
• Manual feeds would weaken operational integration and does not address database capacity, archival, or recovery.

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 Warehousing and Business Intelligence
• Metadata Management