In the context of ECS, what are the primary use cases for implementing strict data compliance and retention policies?

Question

Options

• ALong-term archival for historical analysis
• BRegulatory compliance with industry standards
• CTemporary data storage for transient processing
• DProtection against data breaches and unauthorized access

• A
  92% (36)
• C
  5% (2)
• D
  3% (1)

Explanation

Implementing strict data compliance and retention policies in ECS (Elastic Cloud Storage) is fundamentally about keeping data for the right duration and meeting legal/regulatory obligations - both of which align with options A and B. Long-term archival (A) ensures data remains accessible and intact for historical audits, litigation holds, and business intelligence, while regulatory compliance (B) addresses mandates like HIPAA, SEC 17a-4, FINRA, and GDPR that require specific retention durations and immutability guarantees (e.g., WORM - Write Once, Read Many).

C is wrong because temporary/transient storage is the opposite of what compliance and retention policies enforce - those policies exist precisely to prevent data from being prematurely deleted or altered. D is wrong because breach protection and access control are security concerns handled by IAM policies, encryption, and firewalls, not by data retention policies themselves - though they may coexist in a broader data governance strategy.

Memory tip: Think of compliance + retention as a legal contract with time - you're promising regulators that data will survive (archival) and conform (regulatory standards). If an answer describes short-lived or security-focused data handling, it's outside that promise.

No community discussion yet for this question.