ISC · Information Systems and Data Management · 6 practice questions
What Governs Data Retention Periods?
Applicable legal, regulatory, and contractual requirements govern retention and deletion before storage cost or convenience. Below: compare responses to an invoice retention decision and see why archiving can reduce cost without shortening retention.
Try one first
Hint
Which factor can impose nonnegotiable obligations (including both required retention and required deletion) rather than being a discretionary trade-off?
Answer B. Binding legal, regulatory, and contractual obligations can both require retention (e.g., statutory tax-record rules) and require deletion (e.g., privacy statutes or contractual deletion rights), so they must govern retention policy first. When no such obligations exist for a dataset, retention decisions should rely on documented business need, analytics value, and a risk/cost assessment.
Why not A: This distractor is tempting because analytics often drives practical data decisions, but it is wrong: it treats legal rules mainly as prohibitions and ignores affirmative legal or contractual retention mandates (for example, required tax or audit record retention). Legal and contractual obligations are not limited to prohibiting retention and thus cannot be subordinated this way.
Why not C: This is attractive to cost-conscious managers, but it fails because operational or cost considerations cannot justify violating binding legal or contractual requirements that mandate retention or deletion. Operational factors are important but secondary to nonnegotiable legal obligations.
Why not D: Industry benchmarks provide useful guidance and consistency, which makes this answer tempting, but they are only advisory. They do not supersede binding legal, regulatory, or contractual requirements, which must come first.
What should you do?
The situation
North Co. is setting retention rules for customer invoices. Operations wants deletion after one year to reduce storage costs. Internal audit wants five years for analysis. Legal confirms that applicable tax rules and customer contracts require seven years from creation. The invoices are rarely accessed after one year and can remain retrievable in an archive. Which response best addresses the decision?
Archive inactive invoices and retain them through the required seven-year period.
Best This meets the binding minimum while addressing storage cost. The archive must keep the invoices retrievable.
Keep the invoices retrievable in production for the required seven years.
Acceptable This satisfies retention, but it does not use the available archive to address storage cost.
Delete invoices after one year to reduce storage costs.
Wrong Cost savings cannot override the seven-year requirement.
Retain invoices for five years, matching internal audit's analytical need.
Wrong A business preference cannot shorten a binding legal or contractual minimum.
Archive invoices after one year, then delete them immediately.
Wrong Moving invoices to an archive does not satisfy the remaining retention period.
Key points
- Remember: Low usage can change where North keeps invoices, not how long it must retain them.
- Internal audit's five-year preference cannot shorten North's binding seven-year minimum.
- North's invoices must remain retrievable for seven years, whether kept in production or an accessible archive.
How the exam traps you
- Choosing the deletion date based on storage savings. Meet the seven-year requirement first; reduce cost through compliant archiving.
- Treating internal audit's preferred period as the governing requirement. Five years is insufficient when binding requirements demand seven.
- Treating a move to an archive as permission to destroy records. Archiving continues retention; it does not end the obligation.
Question 2
Hint
Focus on the difference between archiving data and being allowed to dispose of it.
Answer C. Records should be destroyed only after the approved retention period has been satisfied and there are no legal, regulatory, audit, or business holds requiring continued retention. Archiving is a retention method, not a destruction trigger, and preserves records for the remainder of their retention term. Operational factors such as backup schedules or storage pressure do not override the retention policy.
Why not A: Tempting because candidates sometimes equate archiving with deletion; however, moving data to an archive is still an act of retention. Archived records remain subject to the retention schedule until the retention period expires and no hold applies.
Why not B: Appeals to operational cost or storage-management thinking, but storage constraints do not authorize early destruction. Legal and policy retention obligations take precedence over storage pressure.
Why not D: Sounds cautious because backups preserve copies, but backup timing is not the authorized trigger for disposal. If the retention period has expired and no hold exists, records may be destroyed per policy without awaiting a backup cycle.
Question 3
Hint
Focus on the step that should come before automated deletion rules are built. Think about what determines how long different records should be kept.
Answer A. Retention and deletion policies should be driven by the nature of the records and the legal, regulatory, and business obligations that apply to each category. Classifying records and mapping requirements first provides a defensible governance foundation so automated rules enforce the correct retention periods and reduce the risk of premature deletion or unnecessary retention.
Why not B: This is tempting because uniformity simplifies administration, but a single retention period ignores differing legal and business requirements across record types. That approach risks noncompliance for records that require longer retention and unnecessary storage for others.
Why not C: Backups support recovery but do not replace a properly defined retention policy; relying on backups to correct premature deletions is reactive and can be legally and operationally risky. The correct preventive step is to define retention rules based on classification before automating deletions.
Why not D: Departments may understand their records, but decentralized deletion schedules without a common classification and governance framework create inconsistency and compliance gaps. Centralized automation should be based on a mapped, governed classification to ensure consistent enforcement.
Question 4
Hint
Classify each dataset as compliance (long-term archive), operational (must remain live), or short-term incident-response; then apply the company's rule that 30-day DR backups do not satisfy long-term regulatory archival requirements.
Answer A. Financial transaction records have a 7-year regulatory retention and must be accessible for audit, placing them in the WORM-enabled long-term archive is required because 30-day DR backups are insufficient. Customer master data is operational and must remain live with replication and backups while enforcing encryption-at-rest and strict access controls to protect PII and payment-card tokens. Debug logs are short-term for incident response and should be held in a log-management system for 90 days; backups are not a substitute for appropriate log retention or compliance archives.
Why not B: Tempting because it avoids changing infrastructure by extending the existing backup process. It fails because the stem limits backups to 30 days for DR and they cannot satisfy a 7-year regulatory archive; relying solely on transport protections leaves stored PII and payment tokens insufficiently protected, and backups are a poor mechanism for timely log access and forensic investigations.
Why not C: Tempting because archiving everything looks compliant and reduces primary storage costs. It fails because customer master data is required live for daily operations, archiving it would disrupt business processes; retaining debug logs indefinitely contradicts the stated 90-day purpose and data-minimization; and long-term archive is intended for regulatory retention, not routinely for operational data.
Why not D: Tempting because it prioritizes availability with a single-system approach and minimal change. It fails because the stem explicitly states backups are for 30-day DR and cannot meet the 7-year archival requirement, and treating most PII less restrictively risks noncompliance and inadequate protection.
Question 5
Hint
Focus on what must be satisfied before data can be destroyed, not on what makes deletion convenient.
Answer D. Data retention and disposal decisions should be driven first by retention requirements, including legal, regulatory, and business needs. If law or internal policy requires that records be retained, they must be kept (for example, moved to an archive) even when they are old or rarely accessed. Cost and convenience are secondary and cannot justify destroying records that must be retained.
Why not A: This is tempting because candidates may look for a simple age-based rule. In practice, age alone does not determine deletion; required retention periods depend on the type of record and applicable legal, regulatory, and business rules.
Why not B: This is tempting because storage cost is often the reason management wants to purge data. However, storage usage is a secondary operational concern and cannot justify deleting records that must still be retained under applicable legal, regulatory, or business requirements.
Why not C: This is tempting because low-usage data often belongs in an archive rather than a production system. But access frequency affects storage tiering or whether to archive, not whether the records may legally be destroyed when retention obligations still apply.
Question 6
Hint
Ask what would justify treating these data sets differently even if using one uniform policy would be easier.
Answer D. Data management policies should be driven primarily by the nature of the data and the legal or regulatory requirements that apply. Sensitive or regulated records (for example, payment card data or payroll) typically require stricter retention, access, and disposal controls than anonymized or low-risk operational data.
Why not A: Format affects tooling and storage choices, which makes this tempting, but structured vs unstructured alone does not determine retention periods, access restrictions, or disposal standards; those depend on sensitivity and applicable requirements.
Why not B: This is tempting because storage costs are a practical concern, but storage usage does not determine appropriate retention, access, or disposal rules; sensitive or regulated data may need stricter handling even if it occupies little space.
Why not C: This seems plausible since departments often act as data owners, but the creating department does not override the data's sensitivity or legal obligations when setting controls, retention, and disposal requirements.
Common questions
What primarily governs data retention periods?
Applicable legal, regulatory, and contractual requirements govern first. For North's invoices, they impose a seven-year minimum that cost savings and shorter business preferences cannot override.
Can archived invoices satisfy a retention requirement?
Yes, under North's facts, an accessible archive can satisfy the requirement. The invoices do not need to remain in production for all seven years.
Must every company retain invoices for seven years?
This scenario establishes seven years for North's invoices, not a universal rule. Determine the requirements that apply to the specific records before setting their retention period.
Watch it solved
A full CPA ISC task-based simulation on Data management, worked step by step.
Data Quality Defects & ETL Reconciliation | CPA ISC Simulation (TBS) on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Data management
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.