ISC · Information Systems and Data Management · 12 practice questions
Legal Hold vs Retention Schedule: Archives and Backups
Preservation duties override scheduled deletion for relevant records, not automatically for every record or backup. Below: one purge scenario with changed facts showing when to stop deletion, what to preserve, and when backup rotation can continue.
Try one first
Hint
Focus on immediate, defensible actions IT can take to prevent imminent deletion before counsel defines scope.
Answer A. A written preservation request creates a reasonable anticipation of investigation and triggers preservation obligations; retention schedules do not excuse deletion once preservation is requested. Because IT is authorized to take immediate preservation steps pending counsel, suspending the deletion and taking defensible preservation measures while notifying legal and compliance prevents spoliation.
Why not B: Tempting because it follows formal policy requiring counsel to issue holds, but waiting while deletion is imminent risks irreversible loss. The stem explicitly authorizes IT to take immediate preservation steps pending counsel, so delaying is unsafe.
Why not C: Tempting because it relies on established retention practices and backups, but retention schedules do not override preservation duties once an inquiry is reasonably anticipated. Backups may not be immutable, readily restorable for discovery, or in scope, so this approach risks spoliation.
Why not D: Tempting because it attempts to limit retained data and comply narrowly with the request, but investigatory scope often expands and relevant custodians/messages may be identified later. Selective preservation risks missing material and creating spoliation exposure.
Same scenario, one fact changes
Base case
Meridian will purge Contract C and other expired contracts tomorrow after their seven-year retention period. Complete originals, metadata, and related records remain in an indexed archive with immutable hold capability. Recovery backups contain no unique relevant records. IT can suspend deletion selectively and take interim preservation steps pending counsel. No hold, anticipated litigation, or longer binding retention applies. What should IT do?
Answer: Proceed with the scheduled archive purge and normal recovery-backup rotation.
The retention period has expired, and no preservation duty prevents disposal. The archive's location and technical capabilities do not independently require longer retention.
Before you open each one, predict the answer.
Change 1Counsel issues a legal hold covering Contract C and all related records before tomorrow's purge.
Answer: Place Contract C and related archive records in immutable hold status. Document the action. Purge unrelated expired contracts and continue normal backup rotation.
The hold overrides deletion for its defined scope. Complete archive preservation and no unique relevant backup records allow recovery-backup rotation.
Change 2A credible demand letter received today makes litigation over Contract C reasonably anticipated.
Answer: Immediately suspend deletion of Contract C and potentially relevant related records. Notify counsel, implement and document preservation, and continue unrelated disposal and normal backup rotation.
Reasonably anticipated litigation triggers preservation before filing. IT has authority to act immediately; waiting for a formal hold risks irreversible loss.
Change 3A binding regulator instruction requires Contract C and related records to remain retrievable beyond tomorrow.
Answer: Block disposal of Contract C and related records in the controlled archive. Document the retention exception. Purge unrelated expired contracts and continue normal backup rotation.
The binding instruction overrides the ordinary schedule for covered records. The indexed archive provides retention and retrieval; recovery backups do not replace it.
Key points
- Remember: an expired retention period permits deletion only when no preservation duty still covers the records.
- Use the archive's immutable hold capability to protect originals, metadata, and related records without losing searchability.
- Backup rotation can continue here because the archive preserves complete records and backups contain no unique relevant information.
- Document which records were protected, who acted, and when.
How the exam traps you
- Wait for a filed lawsuit or court order before stopping deletion. Act when litigation becomes reasonably anticipated; use authorized interim preservation while notifying counsel.
- Delete archived originals because recovery backups still contain copies. Preserve the searchable records rather than relying on rotating recovery copies.
- Freeze every expired contract because Contract C requires preservation. Protect Contract C and related records; continue scheduled disposal for unrelated records.
Now the same facts as questions
Each question changes one fact from the one before. Watch which change flips the answer.
Question 1
Answer B. The retention period expired, and no preservation duty overrides scheduled disposal.
Why not A: Archive capabilities do not create a preservation duty or require indefinite retention.
Why not C: Backup copies do not independently require preserving the archived contract.
Why not D: No preservation duty requires stopping backup rotation; follow the established disposal schedule.
Question 2
Answer D. Scoped archive preservation satisfies the hold here; backups contain no unique relevant records.
Why not A: A valid hold overrides the expired retention period for covered records.
Why not B: The known scope and complete archive do not require a blanket freeze.
Why not C: Rotating backups are not a substitute for preserving searchable archive records.
Question 3
Answer A. Reasonably anticipated litigation triggers preservation, and IT is authorized to act pending counsel.
Why not B: Preservation can be required before a complaint is filed.
Why not C: Authorized interim preservation prevents loss while counsel formalizes the hold.
Why not D: Recovery backups do not replace preservation of accessible, searchable records.
Question 4
Answer C. The archive preserves required records and retrieval without unnecessarily freezing unrelated disposal.
Why not A: A binding retention instruction overrides scheduled deletion even without litigation.
Why not B: Recovery backups do not substitute for controlled, searchable retention of required records.
Why not D: The instruction covers Contract C and related records, not every expired contract.
Question 2
Hint
Which option describes a documented, preauthorized, narrowly scoped, and auditable emergency procedure rather than an ad hoc or informal bypass of IAM controls?
Answer B. A documented, preauthorized 'break‑glass' emergency override is the proper limiting condition: it allows immediate action for urgent incidents while remaining narrowly scoped, automatically logged, and subject to post‑access review, preserving accountability. The other options describe ad hoc or informal bypasses of IAM controls (credential sharing, ad hoc vendor privilege grants, or broad temporary privilege assignments) that are not permitted under the stated policy.
Why not A: Tempting because managers have operational authority and troubleshooting can feel urgent, but sharing credentials defeats RBAC and nonrepudiation, prevents proper auditing, and creates major security and compliance risks; it is not a documented, auditable exception.
Why not C: Tempting because contracts often authorize vendor work and the task is scheduled, but bypassing IAM approval and provisioning is improper; vendor access should be granted through predefined vendor roles or time‑bound IAM provisions with least privilege and logging, not ad hoc privilege grants.
Why not D: Tempting because project timelines create pressure to expedite work, but mass temporary privilege assignments circumvent least‑privilege controls and auditing; proper temporary access requires documented, minimal‑scope approvals implemented via IAM with enforced expirations.
Question 3
Hint
Ask whether each option preserves original records, linked documents, and change history and whether it provides practical, searchable access for reconstruction and investigations.
Answer B. The requirement is for complete, queryable records that support reconstruction and investigations. The warehouse is analytics‑oriented (ETL transformations, surrogate keys, excluded transactions, missing source documents/change logs) and cannot reliably reproduce original records or context. Backups are recovery‑focused and impractical for routine, searchable access. A purpose‑built archive preserves originals, attachments, change history, and practical retrieval capabilities.
Why not A: This is tempting because the warehouse appears to retain transaction‑level data used for reporting. It fails because warehouse ETL, surrogate keys, omitted voided/rejected records, and the absence of source documents and change logs prevent faithful reconstruction and investigative retrieval.
Why not C: This is tempting because backups preserve the original system image. It fails because backups are designed for disaster recovery, are slow and cumbersome to restore for routine queries, and do not provide convenient, searchable access or indexed context for investigations.
Why not D: This is tempting because exporting detailed extracts and documents seems to preserve necessary records. It fails because ad hoc exports often omit change logs, linked documents, or consistent identifiers and require substantial processing/indexing to be queryable; the facts given do not state that such comprehensive, indexed exports exist.
Question 4
Hint
Ask what kind of fact can override a routine data-purge policy even when summary information is already available.
Answer A. Legal, regulatory, and tax retention requirements override routine data-purging practices. If transaction-level records are required for a specified period (for example, 7 years), deleting them after 30 days would violate those requirements and could impede audits or legal compliance. Therefore such a retention mandate makes the 30-day purge inappropriate.
Why not B: This is tempting because low storage cost reduces the operational burden of keeping data, but storage efficiency does not create a legal or regulatory obligation to retain or to delete records. The question asks which fact would make the purge inappropriate; storage efficiency does not do so.
Why not C: This may seem persuasive because potential future use argues for retention, but a vague possibility without documented business, legal, or regulatory need is not a firm limiting condition. It does not definitively make the 30-day purge inappropriate.
Why not D: Exporting summaries for reporting does not change whether detailed source records must be preserved. The presence of summary copies does not override a legal retention requirement nor does it alone make the 30-day purge inappropriate.
Question 5
Hint
Think about the purpose of archiving in the data lifecycle: it is not the same as deleting data or waiting for a storage emergency.
Answer C. Archiving is the appropriate action once data is no longer required for normal processing but must be kept for retention, compliance, or reference. Because these orders become rarely used after 90 days yet must remain searchable for seven years, the end of active operational use is the proper trigger to archive them into searchable, lower-cost storage.
Why not A: This is tempting because immediate archiving reduces production-system volume, but it is premature: data should remain in the active environment while it is still needed for routine processing and only be archived after active use ends.
Why not B: This confuses archiving with final disposition. The end of the retention period typically triggers review for destruction or other disposition; archiving is commonly done earlier, during the retention period, when data is inactive but must still be retained and searchable.
Why not D: Waiting for storage pressure is a reactive approach. Good data lifecycle management uses defined triggers such as the end of routine business use rather than delaying archiving until a capacity emergency.
Question 6
Hint
Ask which fact overrides a routine retention schedule, rather than which fact only affects storage or convenience.
Answer B. A legal hold (litigation hold) is a formal directive to preserve information that may be relevant to litigation and it overrides routine retention and destruction schedules. Once relevant data is identified, the organization must suspend normal deletion to preserve potential evidence. The fact that the records have already exceeded the routine retention period does not remove the obligation to preserve them under a legal hold.
Why not A: Archive storage indicates a change in storage tier but does not itself create a preservation obligation. Only a legal hold or other legal/regulatory requirement overrides the scheduled deletion.
Why not C: Backup copies can be useful for recovery, but they are not a substitute for an explicit legal hold because backup rotation, retention policies, or restore limitations might still cause loss. Preservation requires suspending normal deletion for the primary and any controlled copies when litigation is involved.
Why not D: Business interest in potential analytical value might affect retention policy planning, but it does not create the legal obligation to suspend deletions; a legal hold or regulatory requirement is the stronger and appropriate reason to stop routine destruction.
Question 7
Hint
Focus on which option is built for long-term retention and selective retrieval, rather than for system recovery or ongoing operational processing.
Answer A. An archive repository is intended for long-term retention, targeted retrieval, and controlled disposition of records that are no longer needed for active processing. An indexed archive supports retrieval within the stated SLA, and immutable retention plus legal-hold features satisfy preservation and suspension-of-deletion requirements without relying on production systems. Backups and replication primarily address recovery and availability, not managed archival retention.
Why not B: This is tempting because backups do preserve data for long periods, but backups are designed for disaster recovery, not efficient selective retrieval or lifecycle management. Restoring backups to satisfy occasional record requests is operationally cumbersome and lacks built-in immutable retention and legal-hold controls.
Why not C: Replication supports availability and load distribution and can facilitate querying, but it does not itself provide formal retention scheduling, immutable retention, or legal-hold functionality. It keeps data in an operational form rather than managing archival lifecycle and disposal.
Why not D: Keeping closed records in production may preserve access but fails to reduce production data volume and does not offer controlled archival retention or tamper-evident preservation. Access restrictions alone are weaker than a separate archived repository with explicit retention and legal-hold capabilities.
Question 8
Hint
Ask which option preserves not just old transactions, but also the old business mappings used when the original report was produced.
Answer D. Reproducing a prior report requires both the historical transaction detail and the historical master/reference data (the mappings and hierarchies) in effect when the report was originally produced. A controlled historical store that preserves date-effective master data and archived detail supports reprocessing, drill-down, and auditability. Backups or replicas address recovery or availability, but do not reliably preserve the reporting context for exact prior-period reproducibility.
Why not A: Tempting because backups are point-in-time copies, but backups are designed for recovery, not controlled historical reporting. Restoring the 'closest backup' may not match the exact reporting date or the mappings in use, and repeated restores are operationally inefficient and error-prone.
Why not B: Keeping issued report outputs preserves what was distributed, but does not permit rerunning the report, performing drill-downs, or validating how results were produced. The requirement is to rerun Year 1 reports in Year 3 and have the rerun agree to the original, which needs retained underlying data and historical mapping context.
Why not C: A replica helps availability but typically mirrors the current state, including in-place updates to master data, so it does not preserve the historical classification context needed to recreate old reports exactly. Replication addresses continuity, not the date-effective archival of reporting context.
Common questions
Does a legal hold override a retention schedule?
Yes. If Contract C is covered, Meridian must suspend its deletion even though the seven-year period has expired. Unrelated expired contracts can still be purged.
Must deletion stop before a lawsuit is filed?
Yes, when litigation is reasonably anticipated. A credible demand letter concerning Contract C can trigger preservation before a complaint or court order.
Can backup rotation continue during a legal hold?
In this scenario, yes: complete relevant records are preserved in the archive, and backups contain no unique relevant records. That does not permit destroying backup information needed for preservation.
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.